<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>Yes, what Hervé wrote is a good approach. (Actually, the same
issue was already discussed in another mail thread [1]). I also
talked about this with Lajos Katona and he is planning to prepare
the EOL process and the release patches as far as I know.</p>
<p>Thanks,<br>
</p>
<p>Előd</p>
<p>[1]
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/pipermail/openstack-discuss/2021-June/thread.html#23347">http://lists.openstack.org/pipermail/openstack-discuss/2021-June/thread.html#23347</a></p>
<p><br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 2021. 07. 01. 14:59, Herve Beraud
wrote:<br>
</div>
<blockquote type="cite" cite="mid:CAFDq9gUN5OCMjH6_5MqEMXZsZ8JjPF7dK97p1eBQmNddh12Csw@mail.gmail.com">
<div dir="ltr">
<div>Hello,</div>
<div><br>
</div>
<div>I think that you are more or less in the same situation as
with `puppet-openstack-integration`.</div>
<div><br>
</div>
<div>Please have a look to this patch <a href="https://review.opendev.org/c/openstack/releases/+/798282" moz-do-not-send="true">https://review.opendev.org/c/openstack/releases/+/798282</a></div>
<div><br>
</div>
<div>I think that we could do something similar and then remove
the stale branches.</div>
<div><br>
</div>
<div>Let me know what you think about this.<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Le jeu. 1 juil. 2021 à 14:45,
Akihiro Motoki <<a href="mailto:amotoki@gmail.com" moz-do-not-send="true">amotoki@gmail.com</a>> a écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
I have a question about how to mark stable branches as EOL
when such branches<br>
were not part of official releases at the moment of
corresponding<br>
releases but the<br>
repositories which contain them became official after the
release.<br>
<br>
One example happens in a repository under the neutron team.<br>
networking-odl is now part of the neutron governance but as of
Ocata<br>
release it was not official.<br>
Ocata branches under the neutron stadium were marked as EOL
recently,<br>
but networking-odl<br>
was not marked as EOL as it was not an official repository as
of Ocata.<br>
<br>
The openstack/releases repository handles official branches
under a<br>
specific release,<br>
but all branches in official repositories are under control of
the<br>
openstack/releases repo.<br>
<br>
I wonder how we can mark stable/ocata branch of networking-odl
repo as<br>
EOL and delete stable/ocata branch.<br>
What is the recommended way to mark such branches described
above as EOL?<br>
<br>
Thanks in advance,<br>
Akihiro Motoki (irc: amotoki)<br>
<br>
</blockquote>
</div>
<br clear="all">
<br>
-- <br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>Hervé Beraud</div>
<div>Senior Software Engineer at Red Hat</div>
<div>irc: hberaud</div>
<div><a href="https://github.com/4383/" target="_blank" moz-do-not-send="true">https://github.com/4383/</a></div>
<div><a href="https://twitter.com/4383hberaud" target="_blank" moz-do-not-send="true">https://twitter.com/4383hberaud</a><br>
</div>
<div>-----BEGIN PGP SIGNATURE-----<br>
<br>
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+<br>
Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+<br>
RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP<br>
F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G<br>
5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g<br>
glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw<br>
m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ<br>
hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0<br>
qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y<br>
F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3<br>
B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O<br>
v6rDpkeNksZ9fFSyoY2o<br>
=ECSj<br>
-----END PGP SIGNATURE-----<br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</body>
</html>