+1 We haven't seen any interest to backport fixes to these two old branches. We've spent some amount of effort to keep CI for the stable/train branch but stable/stein and stable/rocky lack anyone interested in maintenance and CI jobs in these branches have been broken for a while. So it'd make sense to EOL these two branches. On Wed, Nov 30, 2022 at 8:25 PM Brendan Shephard <bshephar at redhat.com> wrote: > Hi, > > We were discussing some of the older branches we have and thought it was > about time we start moving some of them to EOL. > > Initially, I would like to move Rocky and Stein to EOL and have done so > here: > review.opendev.org > <https://review.opendev.org/c/openstack/releases/+/866135> > [image: favicon.ico] > <https://review.opendev.org/c/openstack/releases/+/866135> > <https://review.opendev.org/c/openstack/releases/+/866135> > > > We would also like to move Train to EOL as well, pending a few changes > being merged. I wanted to reach out and ensure there is no objections here > to any of these branches being EOL’d. Feel free to voice any concerns, > otherwise I will move forward with that next week. > > Cheers, > > Brendan Shephard > Senior Software Engineer > Red Hat Australia > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20221207/285fb011/attachment-0001.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: favicon.ico Type: application/octet-stream Size: 5430 bytes Desc: not available URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20221207/285fb011/attachment-0001.obj>