<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://opendev.org/openstack/ironic/src/tag/stein-eol">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://docs.openstack.org/project-team-guide/stable-branches.html#end-of-life">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">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>