<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">
<span style="font-family: "Courier New", monospace;">Hi,</span>
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;">Similarly like the Queens branch EOL proposal [1] I would like to propose</span></div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;">to transition every project's stable/rocky to End of Life:</span></div>
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;">- gates are mostly broken</span></div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;">- minimal number of activity can be seen on this branch
</span></div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;">- some core projects already transitioned their stable/rocky to EOL</span></div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;"> recently (like ironic, neutron, nova)</span></div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;">- gate job definitions are still using the old, legacy zuul syntax</span></div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;">- gate jobs are based on Ubuntu Xenial, which is also beyond its public</span></div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;"> maintenance window date and hard to maintain</span></div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;">
</span></div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;">Based on the above, if there won't be any project who wants to keep open</span></div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;">their stable/rocky, then I'll start the process of EOL'ing Rocky stable</span></div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;">series as a whole. If anyone has any objection then please respond to</span></div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;">this mail.</span></div>
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;">Thanks,</span></div>
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;">Előd Illés</span></div>
<div class="ContentPasted0"><span style="font-family: "Courier New", monospace;">irc: elodilles @ #openstack-stable / #openstack-release</span></div>
<div><br class="ContentPasted0">
</div>
<span style="font-family: "Courier New", monospace;">[1] </span><a href="https://lists.openstack.org/pipermail/openstack-discuss/2022-October/031030.html" id="LPNoLPOWALinkPreview"><span style="font-family: "Courier New", monospace;">https://lists.openstack.org/pipermail/openstack-discuss/2022-October/031030.html</span></a><br>
<div class="_Entity _EType_OWALinkPreview _EId_OWALinkPreview _EReadonly_1"></div>
<br>
</div>
</body>
</html>