| cardoe | Is 2024.2 not intended to go unmaintained? https://releases.openstack.org/ | 01:37 |
|---|---|---|
| fungi | cardoe: good question. https://governance.openstack.org/tc/resolutions/20220210-release-cadence-adjustment.html#details point #5 would indicate that the interim not-slurp between the two most recent slurp releases should get normal maintenance, and then the second bullet at https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html#unmaintained-branches just means | 02:41 |
| fungi | that when 2024.1 transitions to unmaintained 2024.2 goes eol | 02:41 |
| fungi | "Only SLURP releases are eligible for having an Unmaintained branch." | 02:42 |
| cardoe | Oh I guess that makes sense. For some reason I derped. 2023.2 did the same. | 02:48 |
| *** bauzas_ is now known as bauzas | 08:39 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!