[stable][EM] Extended Maintenance - Queens
Hi, As it was agreed during PTG, the planned date of Extended Maintenance transition of Queens is around two weeks after Train release (a less busy period) [1]. Now that Train is released, it is a good opportunity for teams to go through the list of open and unreleased changes in Queens [2] and schedule a final release for Queens if needed. Feel free to use / edit / modify the lists (I've generated the lists for repositories which have 'follows-policy' tag). I hope this helps. [1] https://releases.openstack.org/ [2] https://etherpad.openstack.org/p/queens-final-release-before-em Thanks, Előd
On Wed, Oct 16, 2019 at 05:44:31PM +0000, Elõd Illés wrote:
Hi,
As it was agreed during PTG, the planned date of Extended Maintenance transition of Queens is around two weeks after Train release (a less busy period) [1]. Now that Train is released, it is a good opportunity for teams to go through the list of open and unreleased changes in Queens [2] and schedule a final release for Queens if needed. Feel free to use / edit / modify the lists (I've generated the lists for repositories which have 'follows-policy' tag). I hope this helps.
[1] https://releases.openstack.org/ [2] https://etherpad.openstack.org/p/queens-final-release-before-em
Thanks,
Előd
Trying to amplify this. The date for Queens to transition to Extended Maintenance is next week. Late in the week we will be proposing a patch to tag all deliverables with a "queens-em" tag. After this point, no additional releases will be allowed. I took a quick look through our stable/queens deliverables, and there are several that look to have a sizable amount of patches landed that have not been released. Elod was super nice by including all of that for easy checking in [2] above. As part of Extended Maintenance, bugfixes can (and should) be cherry-picked to stable/queens. But once we enter Extended Maintenance, there won't be any official releases and it will be up to downstream consumers to pick up these fixes locally as they need them. So consider this a last call for stable/queens releases. Thanks! Sean
On Thu, Oct 17, 2019 at 1:37 PM Sean McGinnis <sean.mcginnis@gmx.com> wrote:
On Wed, Oct 16, 2019 at 05:44:31PM +0000, Elõd Illés wrote:
Hi,
As it was agreed during PTG, the planned date of Extended Maintenance transition of Queens is around two weeks after Train release (a less busy period) [1]. Now that Train is released, it is a good opportunity for teams to go through the list of open and unreleased changes in Queens [2] and schedule a final release for Queens if needed. Feel free to use / edit / modify the lists (I've generated the lists for repositories which have 'follows-policy' tag). I hope this helps.
[1] https://releases.openstack.org/ [2] https://etherpad.openstack.org/p/queens-final-release-before-em
Thanks,
Előd
Trying to amplify this.
The date for Queens to transition to Extended Maintenance is next week. Late in the week we will be proposing a patch to tag all deliverables with a "queens-em" tag. After this point, no additional releases will be allowed.
I took a quick look through our stable/queens deliverables, and there are several that look to have a sizable amount of patches landed that have not been released. Elod was super nice by including all of that for easy checking in [2] above.
As part of Extended Maintenance, bugfixes can (and should) be cherry-picked to stable/queens. But once we enter Extended Maintenance, there won't be any official releases and it will be up to downstream consumers to pick up these fixes locally as they need them.
So consider this a last call for stable/queens releases.
Thanks! Sean
Thank you Elod and Sean. In Manila, we went through the exercise of seeing if we missed out any bug fixes for stable/queens and addressed most of them. However, there's one additional fix [1] due that would be nice to get in. We hope to get that in in the next couple of days and propose a final release with that commit hash. Hope that's okay.. Thanks, Goutham [1] https://launchpad.net/bugs/1845135
On Thu, 2019-10-17 at 15:31 -0500, Sean McGinnis wrote:
On Wed, Oct 16, 2019 at 05:44:31PM +0000, Elõd Illés wrote:
Hi,
As it was agreed during PTG, the planned date of Extended Maintenance transition of Queens is around two weeks after Train release (a less busy period) [1]. Now that Train is released, it is a good opportunity for teams to go through the list of open and unreleased changes in Queens [2] and schedule a final release for Queens if needed. Feel free to use / edit / modify the lists (I've generated the lists for repositories which have 'follows-policy' tag). I hope this helps.
[1] https://releases.openstack.org/ [2] https://etherpad.openstack.org/p/queens-final-release-before-em
Thanks,
Előd
Trying to amplify this.
The date for Queens to transition to Extended Maintenance is next week. Late in the week we will be proposing a patch to tag all deliverables with a "queens-em" tag. After this point, no additional releases will be allowed.
I took a quick look through our stable/queens deliverables, and there are several that look to have a sizable amount of patches landed that have not been released. Elod was super nice by including all of that for easy checking in [2] above.
As part of Extended Maintenance, bugfixes can (and should) be cherry-picked to stable/queens. But once we enter Extended Maintenance, there won't be any official releases and it will be up to downstream consumers to pick up these fixes locally as they need them.
So consider this a last call for stable/queens releases.
Here's the patch [1] to do last kuryr-kubernetes release for Queens. It's not a big deal, most people build their own containers, but I guess it doesn't hurt. [1] https://review.opendev.org/#/c/690109/
Thanks! Sean
On 10/17/2019 3:31 PM, Sean McGinnis wrote:
The date for Queens to transition to Extended Maintenance is next week. Late in the week we will be proposing a patch to tag all deliverables with a "queens-em" tag. After this point, no additional releases will be allowed.
I took a quick look through our stable/queens deliverables, and there are several that look to have a sizable amount of patches landed that have not been released. Elod was super nice by including all of that for easy checking in [2] above.
As part of Extended Maintenance, bugfixes can (and should) be cherry-picked to stable/queens. But once we enter Extended Maintenance, there won't be any official releases and it will be up to downstream consumers to pick up these fixes locally as they need them.
So consider this a last call for stable/queens releases.
Nova is still working through a non-trivial backlog of backports, the main slowness being some of the stuff yet to land in queens still has to make it through stein and rocky first. I've been bugging stable cores in nova the last week or so but it's slow going. So just FYI that I'm not sure nova will be ready for the queens-em tag this week but I'm trying to get us close. -- Thanks, Matt
On 22-10-19 17:05:41, Matt Riedemann wrote:
On 10/17/2019 3:31 PM, Sean McGinnis wrote:
The date for Queens to transition to Extended Maintenance is next week. Late in the week we will be proposing a patch to tag all deliverables with a "queens-em" tag. After this point, no additional releases will be allowed.
I took a quick look through our stable/queens deliverables, and there are several that look to have a sizable amount of patches landed that have not been released. Elod was super nice by including all of that for easy checking in [2] above.
As part of Extended Maintenance, bugfixes can (and should) be cherry-picked to stable/queens. But once we enter Extended Maintenance, there won't be any official releases and it will be up to downstream consumers to pick up these fixes locally as they need them.
So consider this a last call for stable/queens releases.
Nova is still working through a non-trivial backlog of backports, the main slowness being some of the stuff yet to land in queens still has to make it through stein and rocky first. I've been bugging stable cores in nova the last week or so but it's slow going. So just FYI that I'm not sure nova will be ready for the queens-em tag this week but I'm trying to get us close.
I've finally found time to try and push things through this morning. FWIW I've also updated some dashboards I've been using for active and em stable branch review below, hopefully others find these useful: Add EM dashboard for Nova https://review.opendev.org/#/c/690536/ Nova Stable Maintenance Review Inbox http://shorturl.at/cj156 Nova Extended Maintenance Review Inbox http://shorturl.at/moDFH -- Lee Yarwood A5D1 9385 88CB 7E5F BE64 6618 BCA6 6E33 F672 2D76
One final last call for stable/queens. Tomorrow I will be proposing patches to mark all deliverables as Extended Maintenance by adding a queens-em tag. After this point, there will be no more official releases for any queens deliverables. I took another quick look at unreleased commits today, and there are a few projects that still have some things that might be good to release. As mentioned though, downstream consumers can always pick these up as needed once we are past the point of doing official community releases. Some things do not need to be released. Things like CI job changes, internal documentation, and testing fixes are all good, but not something that needs to be delivered in a "release" of that project. Bug fixes, translations, requirements updates, etc., though are useful things. Thanks, Sean
The date for Queens to transition to Extended Maintenance is next week. Late in the week we will be proposing a patch to tag all deliverables with a "queens-em" tag. After this point, no additional releases will be allowed.
I took a quick look through our stable/queens deliverables, and there are several that look to have a sizable amount of patches landed that have not been released. Elod was super nice by including all of that for easy checking in [2] above.
As part of Extended Maintenance, bugfixes can (and should) be cherry-picked to stable/queens. But once we enter Extended Maintenance, there won't be any official releases and it will be up to downstream consumers to pick up these fixes locally as they need them.
So consider this a last call for stable/queens releases.
Thanks! Sean
On Thu, Oct 24, 2019 at 12:12:38PM -0500, Sean McGinnis wrote:
One final last call for stable/queens. Tomorrow I will be proposing patches to mark all deliverables as Extended Maintenance by adding a queens-em tag. After this point, there will be no more official releases for any queens deliverables.
Patches have now been proposed: https://review.opendev.org/#/q/status:open+project:openstack/releases+branch... If PTLs and/or release liaisons can leave +1, that can help us know which ones we can approve right away to start to clear the queue. Otherwise, for ones with no ack, we will wait until next week and take the silence as implicit approval. We do have a few teams that needed a little more time to wrap up some final things to leave the last release in a good state. We can hold off on a few a little bit longer if they are important. Otherwise, just another reminder, downstream consumers will be able to pick up committed changes during the Extended Maintenance period. They just won't be included in an official community release. Big thanks to Elod for helping get the ball rolling on this and getting reviewers added to the patches! Thanks! Sean
participants (6)
-
Elõd Illés
-
Goutham Pacha Ravi
-
Lee Yarwood
-
Matt Riedemann
-
Michał Dulko
-
Sean McGinnis