<div dir="ltr"><div>Scott,</div><div><br></div><div>I acknowledge and empathize with the pain -- I've operated OpenStack forks downstream at previous jobs and have had to push changes to swap from the branch to the EOL-tag. With that being said, I still wouldn't be in favor of that kind of change in policy, because the downsides -- such as it not being clear to contributors what branches were open for contribution -- are pretty high.</div><div><br></div><div>We have an announcement list[1]. I don't think it's a bad idea to start publishing posts there when a branch changes support status. I'm curious what other contributors would think of this.</div><div><br></div><div>Thanks,</div><div>Jay Faulkner</div><div>Ironic PTL</div><div>TC Vice-Chair<br></div><div><br></div><div>1: <a href="https://lists.openstack.org/pipermail/openstack-announce/">https://lists.openstack.org/pipermail/openstack-announce/</a> <br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 12, 2023 at 6:32 AM Scott Little <<a href="mailto:scott.little@windriver.com">scott.little@windriver.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>Thanks for your response Jay<br>
</p>
<p>Yes the <branch>-eol tag is somewhat useful, but it doesn't
appear to be created until the branch is removed. There is no way
for a downstream consumer to to prepare for the forthcoming branch
deletion. There is no way to avoid a period of breakage. <br>
</p>
<p>I'd like to suggest the branches be 'frozen', as in accepting no
further updates, and tagged with <branch>-eol, but otherwise
allowed to continue to exist for several months if not a year.
That would allow downstream projects a reasonable period to switch
from branch to tag and avoid a period of breakage.<br>
</p>
<p>Second point. Is there a separate mailing list to announce major
events such as EOL of a branch? It's hard to pick such
announcements out of a general mailing list. <br>
</p>
<p>Scott<br>
</p>
<p><br>
</p>
<p><br>
</p>
<div>On 2023-05-11 18:39, Jay Faulkner
wrote:<br>
</div>
<blockquote type="cite">
<strong>
</strong>
<div style="border:1pt solid rgb(156,101,0);padding:2pt;background:rgb(252,252,3)"><strong><u></u><span style="font-size:11pt;color:rgb(0,0,0)">CAUTION: This email
comes from a non Wind River email account!</span><u></u></strong><br>
<u></u><span style="font-size:10pt;color:rgb(0,0,0)">Do not click links or open
attachments unless you recognize the sender and know the
content is safe.</span><br>
<u></u></div>
<div>
<div dir="ltr">
<div>Hey Scott,</div>
<div><br>
</div>
<div>Good news! It's all still there, just not as branches.
When a branch is moved from "Extended Maintenance" (EM) to
End of Life (EOL), we remove the branch but retain the git
refs on a tag.[1] (e.g.
<a href="https://urldefense.com/v3/__https://opendev.org/openstack/ironic/src/tag/stein-eol__;!!AjveYdw8EvQ!apBHo-KzBygqt5lBcWQglBwJIGOdfH3sz3CcLWJ28X_9PFacGxLhRQnyyxD8ARoFb-md29v17QlQmDvFpQ$" target="_blank">
https://opendev.org/openstack/ironic/src/tag/stein-eol</a>
is the tag representing Ironic stable/stein at the point of
EOL).<br>
</div>
<div><br>
</div>
<div>Look for the `train-eol` tag on the projects you're
struggling with, and that should be the git ref you're
looking for. Hopefully your tooling is happy getting any git
ref and not just a branch ref.</div>
<div><br>
</div>
<div>
<div>1: <a href="https://urldefense.com/v3/__https://docs.openstack.org/project-team-guide/stable-branches.html*end-of-life__;Iw!!AjveYdw8EvQ!apBHo-KzBygqt5lBcWQglBwJIGOdfH3sz3CcLWJ28X_9PFacGxLhRQnyyxD8ARoFb-md29v17QlQZtReEw$" target="_blank">
https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-life</a></div>
</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Jay Faulkner</div>
<div>Ironic PTL</div>
<div>TC Vice-Chair</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, May 11, 2023 at
3:20 PM Scott Little <<a href="mailto:scott.little@windriver.com" target="_blank">scott.little@windriver.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hello OpenStack community<br>
<br>
I'm one of the members of the StarlingX community. We've
had a lot of <br>
stability issues with our ability to compile both our
development branch <br>
and supported release branches these last few weeks. It all
traces back <br>
to the Train EOL. We weren't monitoring openstack mailing
lists, and <br>
missed the EOL announcement. We are actively moving off of
Train, but <br>
aren't yet ready.<br>
<br>
What's really causing us grief is that some sub-projects,
e.g.heat and <br>
nova, have started deleting elements of Train, e.g. git
branches.<br>
<br>
Now please don't take this wrong. Ending support for an old
branch is a <br>
totally normal thing, and we accept that. If StarlingX
customers need <br>
support in that area, we'll provide it. However I would plea
to you to <br>
NOT delete the elements of Train that allow other projects
to compile <br>
old openstack releases, e.g. your gits branches.<br>
<br>
Sincerely<br>
<br>
Scott Little on behalf of StarlingX<br>
<br>
<br>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote></div>