[ptl][release][stable][EM] Extended Maintenance - Rocky
Hi,
In less than one month Rocky is planned to enter into Extended Maintenance phase [1] (estimated date: 2020-02-24).
I have generated the list of *open* and *unreleased* changes in *stable/rocky* for the follows-policy tagged repositories [2]. These lists could help the teams, who are planning to do a final release on Rocky before moving stable/rocky branches to Extended Maintenance. Feel free to edit them!
* At the transition date the Release Team will tag the latest (Rocky) releases of repositories with *rocky-em* tag. * After the transition stable/rocky will be still open for bugfixes, but there won't be any official releases.
NOTE: teams, please focus on wrapping up your libraries first if there is any concern about changes, in order to avoid any broken releases!
Thanks,
Előd
[1] https://releases.openstack.org/ [2] https://etherpad.openstack.org/p/rocky-final-release-before-em
Hi Teams, PTLs, Stable Branch Liaisons,
This is a reminder that Rocky Extended Maintenance transition is near.
Please try to schedule a release if it's necessary, for the coming days. (The estimated transition day was today, but it seems a couple of teams are about to initiate a release.)
Thanks,
Előd
On 2020. 01. 27. 17:34, Elõd Illés wrote:
Hi,
In less than one month Rocky is planned to enter into Extended Maintenance phase [1] (estimated date: 2020-02-24).
I have generated the list of *open* and *unreleased* changes in *stable/rocky* for the follows-policy tagged repositories [2]. These lists could help the teams, who are planning to do a final release on Rocky before moving stable/rocky branches to Extended Maintenance. Feel free to edit them!
- At the transition date the Release Team will tag the latest (Rocky)
releases of repositories with *rocky-em* tag.
- After the transition stable/rocky will be still open for bugfixes, but
there won't be any official releases.
NOTE: teams, please focus on wrapping up your libraries first if there is any concern about changes, in order to avoid any broken releases!
Thanks,
Előd
[1] https://releases.openstack.org/ [2] https://etherpad.openstack.org/p/rocky-final-release-before-em
Hi,
In Neutron we still have some patches to merge to stable/rocky branch before we will cut last release and go to EM. Will it be ok if we will do it before end of this week?
On 24 Feb 2020, at 15:44, Elõd Illés elod.illes@est.tech wrote:
Hi Teams, PTLs, Stable Branch Liaisons,
This is a reminder that Rocky Extended Maintenance transition is near.
Please try to schedule a release if it's necessary, for the coming days. (The estimated transition day was today, but it seems a couple of teams are about to initiate a release.)
Thanks,
Előd
On 2020. 01. 27. 17:34, Elõd Illés wrote:
Hi,
In less than one month Rocky is planned to enter into Extended Maintenance phase [1] (estimated date: 2020-02-24).
I have generated the list of *open* and *unreleased* changes in *stable/rocky* for the follows-policy tagged repositories [2]. These lists could help the teams, who are planning to do a final release on Rocky before moving stable/rocky branches to Extended Maintenance. Feel free to edit them!
- At the transition date the Release Team will tag the latest (Rocky)
releases of repositories with *rocky-em* tag.
- After the transition stable/rocky will be still open for bugfixes, but
there won't be any official releases.
NOTE: teams, please focus on wrapping up your libraries first if there is any concern about changes, in order to avoid any broken releases!
Thanks,
Előd
[1] https://releases.openstack.org/ [2] https://etherpad.openstack.org/p/rocky-final-release-before-em
— Slawek Kaplonski Senior software engineer Red Hat
On 2/24/20 2:56 PM, Slawek Kaplonski wrote:
Hi,
In Neutron we still have some patches to merge to stable/rocky branch before we will cut last release and go to EM. Will it be ok if we will do it before end of this week?
That should be fine. As long as these are something in the works and just waiting for them to make it through the review and gating process, we should be able to wait a few days so they are included in a final release.
Sean
On Mon, 24 Feb 2020 at 22:02, Sean McGinnis sean.mcginnis@gmx.com wrote:
On 2/24/20 2:56 PM, Slawek Kaplonski wrote:
Hi,
In Neutron we still have some patches to merge to stable/rocky branch
before we will cut last release and go to EM. Will it be ok if we will do it before end of this week?
That should be fine. As long as these are something in the works and just waiting for them to make it through the review and gating process, we should be able to wait a few days so they are included in a final release.
Indeed, we are down to 2 backports [0], both ready to get in, just waiting for a gate fix [2]
Sean
[0] https://review.opendev.org/705400 and https://review.opendev.org/705199 [1] https://bugs.launchpad.net/neutron/+bug/1864471
Hi,
On 25 Feb 2020, at 15:01, Bernard Cafarelli bcafarel@redhat.com wrote:
On Mon, 24 Feb 2020 at 22:02, Sean McGinnis sean.mcginnis@gmx.com wrote: On 2/24/20 2:56 PM, Slawek Kaplonski wrote:
Hi,
In Neutron we still have some patches to merge to stable/rocky branch before we will cut last release and go to EM. Will it be ok if we will do it before end of this week?
That should be fine. As long as these are something in the works and just waiting for them to make it through the review and gating process, we should be able to wait a few days so they are included in a final release. Indeed, we are down to 2 backports [0], both ready to get in, just waiting for a gate fix [2]
So our final release for some Rocky deliverables is at [1] and after that we can go to EM with [2]. Thx Bernard, Amotoki and the rest of the neutron stable team for help with that :)
Sean
[0] https://review.opendev.org/705400 and https://review.opendev.org/705199 [1] https://bugs.launchpad.net/neutron/+bug/1864471
-- Bernard Cafarelli
[1] https://review.opendev.org/#/c/710080/ [2] https://review.opendev.org/#/c/709901/
— Slawek Kaplonski Senior software engineer Red Hat
participants (4)
-
Bernard Cafarelli
-
Elõd Illés
-
Sean McGinnis
-
Slawek Kaplonski