<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof ContentPasted0">
Hi,
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0">this thread was bit of forgotten, sorry for that. A bit more than two</div>
<div class="ContentPasted0">weeks ago we had a discussion on #openstack-release about this [1].</div>
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0">So, to summerize, there are the issues:</div>
<div class="ContentPasted0">- stable/rocky's gate is mostly broken</div>
<div class="ContentPasted0">- more than one third of the repositories have transitioned their</div>
<div class="ContentPasted0"> stable/rocky branch to EOL (including multiple core component)</div>
<div class="ContentPasted0">- old, unmaintained CI jobs, testing environments, hinders refactoring</div>
<div class="ContentPasted0"> of Zuul jobs and other configurations</div>
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0">On the other hand, as Thomas mentioned, there is the need for some</div>
<div class="ContentPasted0">to be able to cooperate (as an example: recent security issue [2],</div>
<div class="ContentPasted0">mentioned in previous mail or in our IRC discussion) on a common place,</div>
<div class="ContentPasted0">namely in gerrit. This was originally the intention with Extended</div>
<div class="ContentPasted0">Maintenance. We just haven't thought about eternity :)</div>
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0">It seems that teams feel that if a branch is 'open' and in 'Extended</div>
<div class="ContentPasted0">Maintenance' then it still means it is 'fully supported', thus cannot</div>
<div class="ContentPasted0">let the gate failing AND don't want to merge patches without gate</div>
<div class="ContentPasted0">tests, that's one reason why teams rather EOL their branches.</div>
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0">We might need to think more about what is the best way forward.</div>
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0">[1] https://meetings.opendev.org/irclogs/%23openstack-release/%23openstack-release.2023-03-08.log.html#t2023-03-08T13:54:34</div>
<div class="ContentPasted0">[2] https://security.openstack.org/ossa/OSSA-2023-002.html</div>
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0">Előd</div>
<div class="ContentPasted0">irc: elodilles</div>
<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Thomas Goirand <zigo@debian.org><br>
<b>Sent:</b> Tuesday, February 14, 2023 7:31 PM<br>
<b>To:</b> Elõd Illés <elod.illes@est.tech><br>
<b>Cc:</b> openstack-discuss@lists.openstack.org <openstack-discuss@lists.openstack.org><br>
<b>Subject:</b> Re: [all][stable][ptl] Propose to EOL Rocky series</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">On 2/10/23 18:26, Elõd Illés wrote:<br>
> Hi,<br>
> <br>
> thanks for all the feedbacks from teams so far!<br>
> <br>
> @Zigo: Extended Maintenance process was created just for the same <br>
> situation: to give space to interested parties to cooperate and keep <br>
> things maintained even when stable releases are over their 'supported' <br>
> lifetime. So it's good to see that there is interest in it! <br>
> Unfortunately, with very old branches we've reached the state where <br>
> gates can't be maintained and without a functional gate it's not safe to <br>
> merge patches (yes, even security fixes) and they are just using <br>
> resources (CI & maintainers' time). When gate is broken in such extent, <br>
> then i think the community have to accept that it is not possible to <br>
> merge patches confidently and needs to EOL that release.<br>
<br>
That's where I don't agree. There are ways, outside of the OpenStack <br>
gate, to test things, in such ways that merging patches there can be a <br>
thing.<br>
<br>
> Another aspect is that code cannot be cleaned up until those old <br>
> branches are still present (CI jobs, project configurations, etc) which <br>
> gives pain for developers.<br>
<br>
Just disable gating completely then.<br>
<br>
> So, however some vendors would appreciate probably to keep things open <br>
> forever, for the community this is not beneficial and doable I think. <br>
<br>
I don't agree. We need a place to share patches between distros. The <br>
official Git feels like the natural place to do so, even without any <br>
type of gating.<br>
<br>
BTW, my Nova patches for CVE-2022-47951 in Rocky, Stein & Train are <br>
currently wrong and need another approach. I was thinking about simply <br>
disabling .vmdk altogether (rather than having a complicated code to <br>
check for the VMDK subtype). I wonder what other distros did. Where do I <br>
disucss this?<br>
<br>
Cheers,<br>
<br>
Thomas Goirand (zigo)<br>
<br>
</div>
</span></font></div>
</body>
</html>