[all][stable][ptl] Propose to EOL Rocky series

Thomas Goirand thomas at goirand.fr
Sat Jan 28 13:25:38 UTC 2023


Hi,

I understand the gate is broken, however, Rocky is in Debian LTS, and I would like to keep the possibility to merge patches, even with the gate tests disabled. CVE-2022-47951 is an example why this is important...

Thomas Goirand (zigo)

On Jan 28, 2023 11:54, Radosław Piliszek <radoslaw.piliszek at gmail.com> wrote:
>
> Masakari is happy to EOL Rocky too. 
>
> Radek 
> -yoctozepto 
>
> On Fri, 27 Jan 2023 at 20:59, Jay Faulkner <jay at gr-oss.io> wrote: 
> > 
> > Thanks for doing all this cleanup work Elod. Ironic is OK with retirements of these shared resources up to Train. 
> > 
> > - 
> > Jay Faulkner 
> > 
> > On Fri, Jan 27, 2023 at 10:12 AM Elõd Illés <elod.illes at est.tech> wrote: 
> >> 
> >> Hi, 
> >> 
> >> Similarly like the Queens branch EOL proposal [1] I would like to propose 
> >> to transition every project's stable/rocky to End of Life: 
> >> 
> >> - gates are mostly broken 
> >> - minimal number of activity can be seen on this branch 
> >> - some core projects already transitioned their stable/rocky to EOL 
> >>   recently (like ironic, neutron, nova) 
> >> - gate job definitions are still using the old, legacy zuul syntax 
> >> - gate jobs are based on Ubuntu Xenial, which is also beyond its public 
> >>   maintenance window date and hard to maintain 
> >> 
> >> Based on the above, if there won't be any project who wants to keep open 
> >> their stable/rocky, then I'll start the process of EOL'ing Rocky stable 
> >> series as a whole. If anyone has any objection then please respond to 
> >> this mail. 
> >> 
> >> Thanks, 
> >> 
> >> Előd Illés 
> >> irc: elodilles @ #openstack-stable / #openstack-release 
> >> 
> >> [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-October/031030.html 
> >> 
>


More information about the openstack-discuss mailing list