Recently, based on the 'Unmaintained replaces Extended Maintenance'

resolution [1], old branches (Xena, Wallaby, and Victoria), originally

in Extended Maintenance, moved to Unmaintained, together with Yoga

branch that transitioned directly from maintained to Unmaintained as a

first such branch.

From now on, there is the possibility for folks who are interested in

further maintaining these old branches (in the so called 'Unmaintained'

state :)). For that, maintainers need to sign up to be a member of

openstack-unmaintained-core group (or the project specific group, if

such exists). There is no requirement to be part of that group, but we

would like to ask 'unmaintainers' to follow the stable policy [2], if

possible, for unmaintained/* branches as well (*if the given project

follows it on maintained branches). To signal your interest, please

write a mail to this mailing list, or ping openstack-unmaintained-core

group members (for example me :)) on IRC.

As a first important thing, i would like to call attention to the

following part of the resolution:

'The CI for all branches must be in good standing at the time of opt-in.

At a minimum this needs to contain all integrated jobs, unit tests,

pep8, and functional testing. However, as this is a best-effort CI and

to preserve resources, Unmaintained branches will include periodic jobs

of no higher than monthly frequency.' [1]

However, while many gates look healthy [3] (i.e. patches have merged),

there are still a significant number of failing CI gates [4]. So, to

these projects and their unmaintained/.* branches, to be eligible to

kept open for further maintenance and be able to opt-in in the next

cycle for maintenance, these gates have to be fixed as soon as possible.

Otherwise project branches need to be deleted and transitioned to End of

Life. As an example for a simple gate fix, many project/branch need to

drop their failing 'lower-constraints' job (or fix them).

Also a good starter is to fix zuul config errors [5] if there exists any.

Final note from me: as the above quote shows, the concept of good

standing CI is quite minimal. Any further CI jobs (devstack based

tempest jobs) add value to these branches for those who consume them.

So any such work is really appreciated.

If you have any question, feel free to ask, either here, on the mailing

list, or ping me or the TC on IRC.

Thanks for reading this,

Előd Illés

irc: elodilles

@ #openstack-release #openstack-stable #openstack-unmaintained

[1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html

[2] https://docs.openstack.org/project-team-guide/stable-branches.html

[3] https://review.opendev.org/q/branch:%5Eunmaintained/.*+label:Verified%252B2+is:merged

[4] https://review.opendev.org/q/branch:%5Eunmaintained/.*+label:Verified-1,225

[5] https://zuul.opendev.org/t/openstack/config-errors?branch=unmaintained%2Fyoga