On 2023-05-11 16:27:56 -0400 (-0400), Scott Little wrote: [...]
I would plea to you to NOT delete the elements of Train that allow other projects to compile old openstack releases, e.g. your gits branches.
For future reference, it's unsafe to assume branches stick around forever. Projects may EOL and delete them as soon as 18 months from the coordinated release (when normal maintenance for those branches ends). Tags, on the other hand, are kept indefinitely. If you need to know the most recent stable point release tag for a given coordinated release series, you can find them listed on the releases site: As an example, https://releases.openstack.org/train/index.html lists them for Train. While many projects practice an "extended maintenance" to allow interested members of the community to continue backporting fixes on stable branches after that point, those branches are intended as a point of coordination for downstream maintainers who want to collaborate upstream on developing and reviewing backports for older releases. Branches under extended maintenance don't receive point releases and aren't intended to be consumed directly for deployment, but are rather meant as a source for cherry-picking relevant fixes. Not all projects practice extended maintenance and may EOL and delete their branches at any point after normal maintenance ends, but even those who do extend maintenance as long as possible are eventually sunset in a similar fashion. Mandatory sunset is currently about 5 years from the initial coordinated release for that series, but we probably need to shorten it given challenges with testing 10 different branches across projects and lack of actual extended maintenance interest from downstream consumers and redistributors (they're interested in things being maintained of course, but not doing the work to make it happen). -- Jeremy Stanley