[PTL][release][stable] Pike transitioning to Extended Maintenance phase
Hey everyone, Thought I should get this out there to make sure folks are aware. We are actually overdue for Pike to have entered extended maintenance. According to the stable policy, that should happen 18 months after the release [0]. That means we should have made the switch in February, if my math is right. We will need to work through the details to actually put that in effect, but for now I wanted to remind teams that we do not do releases after a stable branch enters this phase. So this is a call for action for any teams that have been backporting fixes that time is short to get a final release out while you can. The release dates for each cycle can be found on the releases site [1]. Thanks! Sean [0] https://docs.openstack.org/project-team-guide/stable-branches.html#maintenan... [1] https://releases.openstack.org/
On 4/4/2019 3:15 PM, Sean McGinnis wrote:
We are actually overdue for Pike to have entered extended maintenance. According to the stable policy, that should happen 18 months after the release [0]. That means we should have made the switch in February, if my math is right.
We will need to work through the details to actually put that in effect, but for now I wanted to remind teams that we do not do releases after a stable branch enters this phase. So this is a call for action for any teams that have been backporting fixes that time is short to get a final release out while you can.
For nova at least we have some stable/pike backports that are held up on getting fixes merged on newer branches even up through stable/stein so I've been waiting on stable/stein to open up after the GA (next week?) before making another review push. -- Thanks, Matt
On Fri, Apr 05, 2019 at 05:15:36PM -0500, Matt Riedemann wrote:
On 4/4/2019 3:15 PM, Sean McGinnis wrote:
We are actually overdue for Pike to have entered extended maintenance. According to the stable policy, that should happen 18 months after the release [0]. That means we should have made the switch in February, if my math is right.
We will need to work through the details to actually put that in effect, but for now I wanted to remind teams that we do not do releases after a stable branch enters this phase. So this is a call for action for any teams that have been backporting fixes that time is short to get a final release out while you can.
For nova at least we have some stable/pike backports that are held up on getting fixes merged on newer branches even up through stable/stein so I've been waiting on stable/stein to open up after the GA (next week?) before making another review push.
Backports can happen already to stable/stein. We just would not be able to do a stable release off of there until next week - April 11 to be precise.
On 4/6/2019 4:10 AM, Sean McGinnis wrote:
Backports can happen already to stable/stein. We just would not be able to do a stable release off of there until next week - April 11 to be precise.
Yeah and we've been doing backports but holding them until the stein GA - is it safe to assume we're past any last minute RC issues for stein and can start merging stable/stein backports to go into the first stable/stein release? -- Thanks, Matt
On Sat, Apr 06, 2019 at 02:52:52PM -0500, Matt Riedemann wrote:
On 4/6/2019 4:10 AM, Sean McGinnis wrote:
Backports can happen already to stable/stein. We just would not be able to do a stable release off of there until next week - April 11 to be precise.
Yeah and we've been doing backports but holding them until the stein GA - is it safe to assume we're past any last minute RC issues for stein and can start merging stable/stein backports to go into the first stable/stein release?
That is a good point, and one I almost followed up to my orginal comment about. You are correct, the main reason teams may want to hold of on backporting anything at this point would be on the off chance that there is a very critical bug found before the final release. Only backporting that critical fix makes it a lot easier than needing to pick up a bunch of not quite so critical changes. The final RC deadline was last Thursday, but we did end up with a couple projects that found bugs important enough to make an exception. Final release happens this Wednesday. I would say it's probably safe now to backport, but I suppose until that final release is complete, there is some risk that something could still happen. So lesson for the future for all of us - it probably is better to be conservative like Nova has been and not actually start backporting fixes to the current stable branch until it really has been released and entered that full stable branch state. Great point! Sean
On Thu, 4 Apr 2019 at 22:17, Sean McGinnis <sean.mcginnis@gmx.com> wrote:
Hey everyone,
Thought I should get this out there to make sure folks are aware.
We are actually overdue for Pike to have entered extended maintenance. According to the stable policy, that should happen 18 months after the release [0]. That means we should have made the switch in February, if my math is right.
We will need to work through the details to actually put that in effect, but for now I wanted to remind teams that we do not do releases after a stable branch enters this phase. So this is a call for action for any teams that have been backporting fixes that time is short to get a final release out while you can.
For neutron, we have quite a few fixes queued in for a final release (and a few in gates right now), I will check with team next week to get that release out. -- Bernard Cafarelli
On Thu, Apr 04, 2019 at 03:15:57PM -0500, Sean McGinnis wrote:
Hey everyone,
Thought I should get this out there to make sure folks are aware.
We are actually overdue for Pike to have entered extended maintenance. According to the stable policy, that should happen 18 months after the release [0]. That means we should have made the switch in February, if my math is right.
We will need to work through the details to actually put that in effect, but for now I wanted to remind teams that we do not do releases after a stable branch enters this phase. So this is a call for action for any teams that have been backporting fixes that time is short to get a final release out while you can.
The release dates for each cycle can be found on the releases site [1].
Thanks Sean! How about this to catch us up: 1. This week I'll propose one change per team[1] to create a release from the current HEAD for stable/pike and tag that as pike-em 2. Just like with other procedural releases teams are free to +/-1 / suggest fixes. 3. We merge any that have PTL/Liaison +1 as we get the approvals 4. Any that aren't explicitly -1'd by April 22nd get merged that week 5. Others get discussed at the Summit/PTG. 6. We release the remainders during the week of May 6th 7. May 13th we formally transition pike to EM Yours Tony. [1] This will be a generally helpful tool to write anyway.
According to the stable policy, that should happen 18 months after the release [0]. That means we should have made the switch in February, if my math is right.
We will need to work through the details to actually put that in effect, but for now I wanted to remind teams that we do not do releases after a stable branch enters this phase. So this is a call for action for any teams that have been backporting fixes that time is short to get a final release out while you can.
The release dates for each cycle can be found on the releases site [1].
Thanks Sean!
How about this to catch us up:
1. This week I'll propose one change per team[1] to create a release from the current HEAD for stable/pike and tag that as pike-em 2. Just like with other procedural releases teams are free to +/-1 / suggest fixes. 3. We merge any that have PTL/Liaison +1 as we get the approvals 4. Any that aren't explicitly -1'd by April 22nd get merged that week 5. Others get discussed at the Summit/PTG. 6. We release the remainders during the week of May 6th 7. May 13th we formally transition pike to EM
Yours Tony.
That sounds like a good plan to me, thanks Tony! This should give teams some time after the stein work settles down to do any final backports they think are important before that final release and transition to EM. I wonder if we should just make that the general policy that we will wait a few weeks after the current series final release so there is a window where teams don't need to be worrying both about current work and stable backport work. At least once things get back to aligning on six month windows. Sean
participants (4)
-
Bernard Cafarelli
-
Matt Riedemann
-
Sean McGinnis
-
Tony Breeds