---- On Mon, 22 Apr 2024 09:45:42 -0700 Stephen Finucane wrote ---
o/
I've noticed that a variety of SDK-related projects have had 'Update .gitreview for unmaintained/wallaby' patches proposed against them, e.g [1]. I'm not sure this makes much sense. Both SDK and OSC are designed to work against any version of OpenStack so there's hardly a reason to keep stable branches around, let alone the unmaintained branches. I took a look through the Project Team Guide docs [2] but while I can find info on opting-in to keep older unmaintained branches around, I can't find any info on opting-out of their creation altogether.
I think this can be done by -1 from unmaintained liaison or PTL when the unmaintained branch cut is proposed. All these pre-SLURP model branches are going to be unmaintained but once we Antelope comes to the stage of moving from a supported branch then it will be easy as only the SLURP branches are supposed to be moved to unmaintained which is default but can be opt-out by -1 the release change. I can propose this to document if it help.
That brings me to my question: does such a thing exist, and if not, can it? How can we ensure we go straight from stable to EOL for these projects?
As a separate point, we may wish to explore removing stable branches entirely for these projects. Open to input on whether this is even possible, or if their removal would have serious issues for folks.
Agree with you, I do not find any reason why we need a stable branch for something whose current/master version is supposed to work against all supported OpenStack releases. I am in favour of removing the stable branch and that way we will be able to keep backward compatibility in a better and easier way. We can release a tag at every release or when the release moves to unmaintained so that that tag can be used for unmaintained branches testing if the current/master version does not work. Same model, we are doing for Tempest. -gmann
Cheers, Stephen
[1] https://review.opendev.org/c/openstack/openstacksdk/+/911660 [2] https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintai...