Re: [openstack-dev] Are we ready to put stable/ocata into extended maintenance mode?
On Tue, Sep 18, 2018 at 1:30 PM Alex Schultz <aschultz@redhat.com> wrote:
On Tue, Sep 18, 2018 at 1:27 PM, Matt Riedemann <mriedemos@gmail.com> wrote:
The release page says Ocata is planned to go into extended maintenance mode on Aug 27 [1]. There really isn't much to this except it means we don't do releases for Ocata anymore [2]. 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 [3]. 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, [3] doesn't mention it, but the resolution said we'd tag the branch [4] 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)?
I believe TripleO would like to EOL instead of EM for Ocata as indicated by the thead http://lists.openstack.org/pipermail/openstack-dev/2018-September/134671.htm...
Bringing this backup to see what we need to do to get the stable/ocata branches ended for the TripleO projects. I'm bringing this up because we have https://review.openstack.org/#/c/647009/ which is for the upcoming rename but CI is broken and we have no interest in continue to keep the stable/ocata branches alive (or fix ci for them). Thanks, -Alex
Thanks, -Alex
[1] https://releases.openstack.org/ [2] https://docs.openstack.org/project-team-guide/stable-branches.html#maintenan... [3] https://docs.openstack.org/project-team-guide/stable-branches.html#extended-... [4] https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.h...
--
Thanks,
Matt
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Wed, Mar 27, 2019 at 11:52 PM Alex Schultz <aschultz@redhat.com> wrote:
On Tue, Sep 18, 2018 at 1:30 PM Alex Schultz <aschultz@redhat.com> wrote:
On Tue, Sep 18, 2018 at 1:27 PM, Matt Riedemann <mriedemos@gmail.com> wrote:
The release page says Ocata is planned to go into extended maintenance mode on Aug 27 [1]. There really isn't much to this except it means we don't do releases for Ocata anymore [2]. 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 [3]. 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, [3] doesn't mention it, but the resolution said we'd tag the branch [4] 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)?
I believe TripleO would like to EOL instead of EM for Ocata as indicated by the thead http://lists.openstack.org/pipermail/openstack-dev/2018-September/134671.htm...
Bringing this backup to see what we need to do to get the stable/ocata branches ended for the TripleO projects. I'm bringing this up because we have https://review.openstack.org/#/c/647009/ which is for the upcoming rename but CI is broken and we have no interest in continue to keep the stable/ocata branches alive (or fix ci for them).
So we had a discussion yesterday in TripleO meeting regarding EOL of Ocata and Pike Branches for TripleO projects, and there was no clarity regarding the process of making the branches EOL(is just pushing a change to openstack/releases(deliverables/ocata/<project>.yaml) creating ocata-eol tag enough or something else is also needed), can someone from Release team point us in the right direction.
Thanks, -Alex
Thanks, -Alex
[1] https://releases.openstack.org/ [2] https://docs.openstack.org/project-team-guide/stable-branches.html#maintenan... [3] https://docs.openstack.org/project-team-guide/stable-branches.html#extended-... [4] https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.h...
--
Thanks,
Matt
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Thanks and Regards Yatin Karel
Bringing this backup to see what we need to do to get the stable/ocata branches ended for the TripleO projects. I'm bringing this up because we have https://review.openstack.org/#/c/647009/ which is for the upcoming rename but CI is broken and we have no interest in continue to keep the stable/ocata branches alive (or fix ci for them).
So we had a discussion yesterday in TripleO meeting regarding EOL of Ocata and Pike Branches for TripleO projects, and there was no clarity regarding the process of making the branches EOL(is just pushing a change to openstack/releases(deliverables/ocata/<project>.yaml) creating ocata-eol tag enough or something else is also needed), can someone from Release team point us in the right direction.
Thanks, -Alex
It would appear we have additional information we should add to somewhere like: https://docs.openstack.org/project-team-guide/stable-branches.html or https://releases.openstack.org/#references I believe it really is just a matter of requesting the new tag in the openstack/releases repo. There is a good example of this when Tony did it for TripleO's stable/newton branch: https://review.opendev.org/#/c/583856/ I think I recall there were some additional steps Tony took at the time, but I think everything is now covered by the automated process. Tony, please correct me if I am wrong. Not sure if it applies, but you may want to see if there are any Zuul jobs that need to be cleaned up or anything of that sort. We do say branches will be in unmaintained in the Extended Maintenance phase for six months before going End of Life. Looking at Ocata, that happened April 5 of this year. Six months would put it at the beginning of October. But I think if the team knows they will not be accepting any more patches to these branches, then it is better to get it clearly marked as EOL so proper expectations are set. Sean
On Thu, Aug 15, 2019 at 12:54 AM Sean McGinnis <sean.mcginnis@gmx.com> wrote:
Bringing this backup to see what we need to do to get the stable/ocata branches ended for the TripleO projects. I'm bringing this up because we have https://review.openstack.org/#/c/647009/ which is for the upcoming rename but CI is broken and we have no interest in continue to keep the stable/ocata branches alive (or fix ci for them).
So we had a discussion yesterday in TripleO meeting regarding EOL of Ocata and Pike Branches for TripleO projects, and there was no clarity regarding the process of making the branches EOL(is just pushing a change to openstack/releases(deliverables/ocata/<project>.yaml) creating ocata-eol tag enough or something else is also needed), can someone from Release team point us in the right direction.
Thanks, -Alex
It would appear we have additional information we should add to somewhere like:
https://docs.openstack.org/project-team-guide/stable-branches.html
or
https://releases.openstack.org/#references
I believe it really is just a matter of requesting the new tag in the openstack/releases repo. There is a good example of this when Tony did it for TripleO's stable/newton branch:
Thanks Sean, so ocata-eol[1] and pike-eol[2] patches were proposed for TripleO and they are merged, both ocata-eol and pike-eol tags got created after the patches merged. But still stable/ocata and stable/pike branches exist. Can someone from Release Team get them cleared so there is no option left to get cherry-pick proposed to these EOL branches. If any step from TripleO maintainers is needed please guide. [1] https://review.opendev.org/#/c/677478/ [2] https://review.opendev.org/#/c/678154/
I think I recall there were some additional steps Tony took at the time, but I think everything is now covered by the automated process. Tony, please correct me if I am wrong.
Not sure if it applies, but you may want to see if there are any Zuul jobs that need to be cleaned up or anything of that sort.
We do say branches will be in unmaintained in the Extended Maintenance phase for six months before going End of Life. Looking at Ocata, that happened April 5 of this year. Six months would put it at the beginning of October. But I think if the team knows they will not be accepting any more patches to these branches, then it is better to get it clearly marked as EOL so proper expectations are set.
Sean
Thanks and Regards Yatin Karel
Thanks Sean, so ocata-eol[1] and pike-eol[2] patches were proposed for TripleO and they are merged, both ocata-eol and pike-eol tags got created after the patches merged. But still stable/ocata and stable/pike branches exist. Can someone from Release Team get them cleared so there is no option left to get cherry-pick proposed to these EOL branches. If any step from TripleO maintainers is needed please guide.
[1] https://review.opendev.org/#/c/677478/ [2] https://review.opendev.org/#/c/678154/
The release automation can only create branches, not remove them. That is something the infra team would need to do. I can't recall how this was handled in the past. Maybe someone from infra can shed some light on how EOL'ing stable branches should be handled for the no longer needed stable/* branches. Sean
On 2019-09-03 14:03:37 -0500 (-0500), Sean McGinnis wrote: [...]
The release automation can only create branches, not remove them. That is something the infra team would need to do.
I can't recall how this was handled in the past. Maybe someone from infra can shed some light on how EOL'ing stable branches should be handled for the no longer needed stable/* branches.
We've done it different ways. Sometimes it's been someone from the OpenDev/Infra sysadmins who volunteers to just delete the list of branches requested, but more recently for large batches related to EOL work we've temporarily elevated permissions for a member of the Stable Branch (now Extended Maintenance SIG?) or Release teams. -- Jeremy Stanley
On Wed, Sep 4, 2019 at 12:57 AM Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2019-09-03 14:03:37 -0500 (-0500), Sean McGinnis wrote: [...]
The release automation can only create branches, not remove them. That is something the infra team would need to do.
I can't recall how this was handled in the past. Maybe someone from infra can shed some light on how EOL'ing stable branches should be handled for the no longer needed stable/* branches.
We've done it different ways. Sometimes it's been someone from the OpenDev/Infra sysadmins who volunteers to just delete the list of branches requested, but more recently for large batches related to EOL work we've temporarily elevated permissions for a member of the Stable Branch (now Extended Maintenance SIG?) or Release teams. --
Thanks Jeremy, Sean for all the information. Can someone from Release or Infra Team can do the needful of removing stable/ocata and stable/pike branch for TripleO projects being EOLed for pike/ocata in https://review.opendev.org/#/c/677478/ and https://review.opendev.org/#/c/678154/.
Jeremy Stanley
Thanks and Regards Yatin Karel
On 2019-09-09 12:53:26 +0530 (+0530), Yatin Karel wrote: [...]
Can someone from Release or Infra Team can do the needful of removing stable/ocata and stable/pike branch for TripleO projects being EOLed for pike/ocata in https://review.opendev.org/#/c/677478/ and https://review.opendev.org/#/c/678154/.
I've attempted to extract the lists of projects from the changes you linked. I believe you're asking to have the stable/ocata branch deleted from these projects: openstack/instack-undercloud openstack/instack openstack/os-apply-config openstack/os-cloud-config openstack/os-collect-config openstack/os-net-config openstack/os-refresh-config openstack/puppet-tripleo openstack/python-tripleoclient openstack/tripleo-common openstack/tripleo-heat-templates openstack/tripleo-image-elements openstack/tripleo-puppet-elements openstack/tripleo-ui openstack/tripleo-validations And the stable/pike branch deleted from these projects: openstack/instack-undercloud openstack/instack openstack/os-apply-config openstack/os-collect-config openstack/os-net-config openstack/os-refresh-config openstack/paunch openstack/puppet-tripleo openstack/python-tripleoclient openstack/tripleo-common openstack/tripleo-heat-templates openstack/tripleo-image-elements openstack/tripleo-puppet-elements openstack/tripleo-ui openstack/tripleo-validations Can you confirm? Also, have you checked for and abandoned all open changes on the affected branches? -- Jeremy Stanley
Hi, On Thu, Sep 12, 2019 at 12:30 AM Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2019-09-09 12:53:26 +0530 (+0530), Yatin Karel wrote: [...]
Can someone from Release or Infra Team can do the needful of removing stable/ocata and stable/pike branch for TripleO projects being EOLed for pike/ocata in https://review.opendev.org/#/c/677478/ and https://review.opendev.org/#/c/678154/.
I've attempted to extract the lists of projects from the changes you linked. I believe you're asking to have the stable/ocata branch deleted from these projects:
openstack/instack-undercloud openstack/instack openstack/os-apply-config openstack/os-cloud-config openstack/os-collect-config openstack/os-net-config openstack/os-refresh-config openstack/puppet-tripleo openstack/python-tripleoclient openstack/tripleo-common openstack/tripleo-heat-templates openstack/tripleo-image-elements openstack/tripleo-puppet-elements openstack/tripleo-ui openstack/tripleo-validations
And the stable/pike branch deleted from these projects:
openstack/instack-undercloud openstack/instack openstack/os-apply-config openstack/os-collect-config openstack/os-net-config openstack/os-refresh-config openstack/paunch openstack/puppet-tripleo openstack/python-tripleoclient openstack/tripleo-common openstack/tripleo-heat-templates openstack/tripleo-image-elements openstack/tripleo-puppet-elements openstack/tripleo-ui openstack/tripleo-validations
Can you confirm? Also, have you checked for and abandoned all open changes on the affected branches?
I totally missed this mail, in today's Tripleo meeting it was raised so get back to this again. @Jeremy yes the list is correct. These branches were EOLed long ago is it still necessary to abandon all open reviews? Anyway, I will get those cleaned.
-- Jeremy Stanley
Thanks and Regards Yatin Karel
On 2021-03-02 19:58:19 +0530 (+0530), Yatin Karel wrote: [...]
is it still necessary to abandon all open reviews? [...]
Gerrit will not allow deletion of a branch if there are any changes still open for it. -- Jeremy Stanley
On Tue, Mar 2, 2021 at 5:06 PM Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2021-03-02 19:58:19 +0530 (+0530), Yatin Karel wrote: [...]
is it still necessary to abandon all open reviews? [...]
thanks ykarel for bringing this up in today's tripleo irc meeting - I completely missed this thread
Gerrit will not allow deletion of a branch if there are any changes still open for it.
thank you and ack Jeremy - I just abandoned a couple of changes I had there (eg https://review.opendev.org/c/openstack/instack-undercloud/+/777368) to remove deprecated things from zuul layouts, but instead removing the branch is a better solution no more zuul layout to worry about ;) - one of those is currently waiting in the gate ( https://review.opendev.org/c/openstack/os-apply-config/+/777533) so i didn't hit abandon ... if it fails for whatever reason then I can abandon that one too. marios
-- Jeremy Stanley
Hi, On Tue, Mar 2, 2021 at 8:40 PM Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2021-03-02 19:58:19 +0530 (+0530), Yatin Karel wrote: [...]
is it still necessary to abandon all open reviews? [...]
Gerrit will not allow deletion of a branch if there are any changes still open for it. --
Ok wasn't aware of it, Thanks for sharing. We have cleaned up all open reviews, please proceed with branch deletion.
Jeremy Stanley
Thanks and Regards Yatin Karel
participants (5)
-
Alex Schultz
-
Jeremy Stanley
-
Marios Andreou
-
Sean McGinnis
-
Yatin Karel