[Openstack-operators] [openstack-dev] [stable][all] Keeping Juno "alive" for longer.

Gareth academicgareth at gmail.com
Mon Nov 9 16:49:55 UTC 2015

Thanks Jeremy,

I hope it come earlier personally. Our company is designing next could
product release, based on Juno. Now I have powerful talking points ;)

On Tue, Nov 10, 2015 at 12:43 AM, Jeremy Stanley <fungi at yuggoth.org> wrote:
> On 2015-11-10 00:18:34 +0800 (+0800), Gareth wrote:
>> BTW, what's the EOL date of Juno?
> "2014.2.4 (eol) early November, 2015."
> <URL: https://wiki.openstack.org/wiki/StableBranchRelease#Planned_stable.2Fjuno_releases_.2812_months.29 >
> This was decided at the stable branch management session for the
> Liberty Design Summit in Vancouver, BC back in May of this year.
> So basically any time after 2014.2.4 is tagged on all the
> release-managed stable-branch deliverables for Juno, the final state
> of the corresponding stable/juno branches will be tagged as juno-eol
> and then the stable/juno branches themselves deleted, per our usual
> EOL process. After which time the Project Infrastructure team will
> delete stable/juno CI jobs and dismantle any Juno-specific support
> infrastructure (for example, CentOS 6.x workers which were kept to
> support contemporary Python 2.6 compatibility testing).
> --
> Jeremy Stanley
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


Cloud Computing, OpenStack, Distributed Storage, Fitness, Basketball
OpenStack contributor, kun_huang at freenode
My promise: if you find any spelling or grammar mistakes in my email
from Mar 1 2013, notify me
and I'll donate $1 or ¥1 to an open organization you specify.

More information about the OpenStack-operators mailing list