[PTL][release][stable] 2023.1 Antelope transition to Unmaintained
Hi teams, As 2024.2 Dalmatian was released last week and we are in a less busy period, now is the good time to call your attention to the following: At the end of October 2023.1 Antelope is planned to transition to Unmaintained phase [1] (planned date: 2024-10-30). I have generated the list of the current *open* and *unreleased* changes in stable/2023.1 for every repositories [2] (where there are such patches). These lists could help the teams who are planning to do a *final* release on Antelope before moving stable/2023.1 branches to unmaintained/2023.1. Feel free to edit and extend these lists to track your team's progress! Note that the last hash on stable/2023.1 branch will be tagged ('<series>-eom' tag) and transition patches will be generated soon. After the tagging and cutting unmaintained/2023.1 branch, the new unmaintained branch will be open to for bug fixes, but there won't be official releases for 2023.1 Antelope anymore. (You can get some information about the Unmaintained state on stable policy page [3]). *NOTE*: teams, please focus on wrapping up your libraries first if there is any concern about the changes, in order to avoid broken (final!!) releases! [1] https://releases.openstack.org/ [2] https://etherpad.opendev.org/p/2023.1-antelope-final-release-before-eom [3] https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintai... Thanks, Előd Illés irc: elodilles @ #openstack-release
---- On Wed, 09 Oct 2024 09:56:36 -0700 Elõd Illés wrote ---
Hi teams,
As 2024.2 Dalmatian was released last week and we are in a less busy period, now is the good time to call your attention to the following:
At the end of October 2023.1 Antelope is planned to transition to Unmaintained phase [1] (planned date: 2024-10-30).
I have generated the list of the current *open* and *unreleased* changes in stable/2023.1 for every repositories [2] (where there are such patches). These lists could help the teams who are planning to do a *final* release on Antelope before moving stable/2023.1 branches to unmaintained/2023.1. Feel free to edit and extend these lists to track your team's progress!
Note that the last hash on stable/2023.1 branch will be tagged ('-eom' tag) and transition patches will be generated soon. After the tagging and cutting unmaintained/2023.1 branch, the new unmaintained branch will be open to for bug fixes, but there won't be official releases for 2023.1 Antelope anymore. (You can get some information about the Unmaintained state on stable policy page [3]).
*NOTE*: teams, please focus on wrapping up your libraries first if there is any concern about the changes, in order to avoid broken (final!!) releases!
As we run the focal job on stable/2023.1, those are broken due to Python 3.8 drop[1]. To fix that, we need to pin the Tempest on stable/2023.1 testing, which means we need to end support of stable/2023.1 on Tempest master[2]. We usually do that when the branch is moved to an unmaintained state, but this time (due to Python 3.8 drop) we need to do it a little early. Hope it will not impact any test coverage (This will only happen when stable/2023.1 backports add tests on Tempest master). [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.... [2] https://review.opendev.org/q/topic:%222023-1-last%22 -gmann
[1] https://releases.openstack.org/ [2] https://etherpad.opendev.org/p/2023.1-antelope-final-release-before-eom [3] https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintai...
Thanks,
Előd Illés irc: elodilles @ #openstack-release
participants (2)
-
Elõd Illés
-
Ghanshyam Mann