[openstack-dev] Are we ready to put stable/ocata into extended maintenance mode?
elod.illes at ericsson.com
Thu Sep 20 17:08:30 UTC 2018
About 1.: I think it is a good idea to cut a final release (especially
as some vendor/operator would be glad even if there would be some
release in Extended Maintenance, too, what most probably won't
happen...) -- saying that without knowing how much of a burden would it
be for projects to do this final release...
After that it sounds reasonably to tag the branches EM (as it is written
in the mentioned resolution).
Do you have any plan about how to coordinate the 'final releases' and do
Thanks for raising these questions!
On 2018-09-18 21:27, Matt Riedemann wrote:
> The release page says Ocata is planned to go into extended maintenance
> mode on Aug 27 . There really isn't much to this except it means we
> don't do releases for Ocata anymore . There is a caveat that
> project teams that do not wish to maintain stable/ocata after this
> point can immediately end of life the branch for their project . We
> can still run CI using tags, e.g. if keystone goes ocata-eol, devstack
> on stable/ocata can still continue to install from stable/ocata for
> nova and the ocata-eol tag for keystone. Having said that, if there is
> no undue burden on the project team keeping the lights on for
> stable/ocata, I would recommend not tagging the stable/ocata branch
> end of life at this point.
> So, questions that need answering are:
> 1. Should we cut a final release for projects with stable/ocata
> branches before going into extended maintenance mode? I tend to think
> "yes" to flush the queue of backports. In fact,  doesn't mention
> it, but the resolution said we'd tag the branch  to indicate it has
> entered the EM phase.
> 2. Are there any projects that would want to skip EM and go directly
> to EOL (yes this feels like a Monopoly question)?
>  https://releases.openstack.org/
More information about the OpenStack-dev