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

Jeremy Stanley fungi at yuggoth.org
Mon Nov 9 16:43:22 UTC 2015

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: Digital signature
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20151109/989fe158/attachment.pgp>

More information about the OpenStack-operators mailing list