[stable][unmaintained] Move old Unmaintained branches to EOL
Dear OpenStack Community, A bit more than two years ago the Unmaintained state was formalized [1] to signal towards the community that branches beyond the official maintained phase are not officially supported by the project teams themselves, rather by volunteers with interests to keep these branches open for co-operation and bug fix backports. This requires CI maintenance time to time, as CI jobs, infrastructure, packaging and build tools might also change under these legacy unmaintained branches. My employer, Ericsson, chose to support this process for further co- operation on these legacy branches and we stepped up as maintainer for unmaintained branches back till unmaintained/victoria as a starter, as long as it is feasible. Unfortunately, in the past months the point is reached where multiple gate jobs got broken, CI infrastructure elements (old ubuntu versions, old python versions) went to End of Life, too, and keeping meaningful testing [2] functional, is harder and harder on the oldest unmaintained/* branches [3]. Given these circumstances, I'm officially initiating to move old unmaintained branches to End of Life, starting with Victoria, and up till Yoga. I'll prepare the transition patches next week. Thanks to all, who helped with these old branches for this long. Sincerely, Előd Illés irc: elodilles @ #openstack-release / #openstack-stable / #openstack-unmaintained [1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branch... [2] there were arguments about making it possible to merge patches without tempest or even without any tests, but that is something that we should avoid in my opinion as we cannot be sure that we don't introduce regressions if there were no proper testing and no one would want to consume untested code. [3] ubuntu-bionic node type is removed, py36 based jobs disappeared, tempest jobs started to fail with some test cases and with that, grenade jobs as well, etc.
Hi Elod, Thanks for all the work you do on keeping the unmaintained release CI running! I did have one question below. On 12/5/25 3:20 PM, Elõd Illés wrote:
Dear OpenStack Community,
A bit more than two years ago the Unmaintained state was formalized [1] to signal towards the community that branches beyond the official maintained phase are not officially supported by the project teams themselves, rather by volunteers with interests to keep these branches open for co-operation and bug fix backports. This requires CI maintenance time to time, as CI jobs, infrastructure, packaging and build tools might also change under these legacy unmaintained branches.
My employer, Ericsson, chose to support this process for further co- operation on these legacy branches and we stepped up as maintainer for unmaintained branches back till unmaintained/victoria as a starter, as long as it is feasible. Unfortunately, in the past months the point is reached where multiple gate jobs got broken, CI infrastructure elements (old ubuntu versions, old python versions) went to End of Life, too, and keeping meaningful testing [2] functional, is harder and harder on the oldest unmaintained/* branches [3].
Given these circumstances, I'm officially initiating to move old unmaintained branches to End of Life, starting with Victoria, and up till Yoga. I'll prepare the transition patches next week. Thanks to all, who helped with these old branches for this long.
I'm fine with moving the older branches to EOL, but I had one question just regarding Yoga, since it is an LTS release for us. Is there an option of somehow keeping CI for some core set of projects alive? Not sure what that would even look like but I figured it didn't hurt to ask. And you can tell me I'm crazy for even asking :) Thanks, -Brian
Sincerely,
Előd Illés irc: elodilles @ #openstack-release / #openstack-stable / #openstack-unmaintained
[1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branch... [2] there were arguments about making it possible to merge patches without tempest or even without any tests, but that is something that we should avoid in my opinion as we cannot be sure that we don't introduce regressions if there were no proper testing and no one would want to consume untested code. [3] ubuntu-bionic node type is removed, py36 based jobs disappeared, tempest jobs started to fail with some test cases and with that, grenade jobs as well, etc.
Hi Brian, Thanks for your mail and for you being a maintainer on unmaintained branches, too :) I included Yoga because it is the latest release that still has python 3.6 as minimum version as supported runtime [1] and that is one of the reason of the EOL'ing that Ubuntu Bionic and with that py36 based tests were gone. Otherwise, I heard from others as well that they use Yoga. I'm not against keeping Yoga, moreover, I volunteer to help with reviews and CI fixes if others are interested (and if that is feasible). Though probably that would need at first to add somehow back the py36 job(s) (based on newer ubuntu nodeset). Also note, that Yoga is already open for a reduced set of projects [2], the rest were moved to EOL before. I've also created the first EOL patch, for Victoria [3], and will propose on top of it the Wallaby and Xena EOL patches for now. [1] https://governance.openstack.org/tc/reference/runtimes/yoga.html [2] https://paste.opendev.org/show/bXkAKOnJ9K8CKc4VcGR7/ [3] https://review.opendev.org/c/openstack/releases/+/970624 Thanks, Előd Illés irc: elodilles @ #openstack-release / #openstack-stable / #openstack-unmaintained
Hi Elod, On 12/11/25 8:54 AM, Elõd Illés wrote:
Hi Brian,
Thanks for your mail and for you being a maintainer on unmaintained branches, too :) I included Yoga because it is the latest release that still has python 3.6 as minimum version as supported runtime [1] and that is one of the reason of the EOL'ing that Ubuntu Bionic and with that py36 based tests were gone. Otherwise, I heard from others as well that they use Yoga.
I'm not against keeping Yoga, moreover, I volunteer to help with reviews and CI fixes if others are interested (and if that is feasible). Though probably that would need at first to add somehow back the py36 job(s) (based on newer ubuntu nodeset). Also note, that Yoga is already open for a reduced set of projects [2], the rest were moved to EOL before.
Yes, maybe we can just move to a focal nodeset for py36? I do realize it's not the reference runtime but this is the unmaintained branch. I think you are proposing that here? https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/958668 Thanks, -Brian
I've also created the first EOL patch, for Victoria [3], and will propose on top of it the Wallaby and Xena EOL patches for now.
[1] https://governance.openstack.org/tc/reference/runtimes/yoga.html [2] https://paste.opendev.org/show/bXkAKOnJ9K8CKc4VcGR7/ [3] https://review.opendev.org/c/openstack/releases/+/970624
Thanks, Előd Illés irc: elodilles @ #openstack-release / #openstack-stable / #openstack-unmaintained
participants (2)
-
Brian Haley
-
Elõd Illés