<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 18, 2022 at 5:40 PM Jiri Podivin <<a href="mailto:jpodivin@redhat.com">jpodivin@redhat.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 dir="ltr"><div>I suppose the corresponding rdo distgit branches will follow suit?</div><div>Once again most of the open reviews[6] are backports.</div><div><br></div><div>[6]<a href="https://review.rdoproject.org/r/q/branch:ussuri-rdo+status:open" target="_blank">https://review.rdoproject.org/r/q/branch:ussuri-rdo+status:open</a></div></div><br></blockquote><div><br></div><div>well those won't be removed as part of <a href="https://review.opendev.org/c/openstack/releases/+/834049">https://review.opendev.org/c/openstack/releases/+/834049</a> - that will only remove the source code branches. </div><div>However indeed the rdo team will likely want to remove the corresponding distgit for each of the tripleo repos being eol for ussuri after we move forward.</div><div><br></div><div>At this point I think we'll probably hold on this until ptg which is just under 2 weeks away but I haven't heard any pushback against this proposal so far,</div><div><br></div><div>marios</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 18, 2022 at 4:35 PM Marios Andreou <<a href="mailto:marios@redhat.com" target="_blank">marios@redhat.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 dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 17, 2022 at 9:20 AM Jiri Podivin <<a href="mailto:jpodivin@redhat.com" target="_blank">jpodivin@redhat.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 dir="ltr"><div>Hi,</div><div>As far as Tripleo-Validations repo[5] is concerned I don't believe we should see any issues.</div><div>For the most part we are treating the stable/ussuri branch as a necessary, but not very meaningful, step when backporting changes to stable/train.</div><div><br></div><div>[5]<a href="https://review.opendev.org/admin/repos/openstack/tripleo-validations" target="_blank">https://review.opendev.org/admin/repos/openstack/tripleo-validations</a></div></div><br></blockquote><div><br></div><div>thanks for confirming Jirka</div><div><br></div><div>so assuming we go ahead with this we will at some point need to close all open reviews against stable ussuri - there aren't too many as we would expect (just things being backported - validations has 3 currently). For convenience, links for all the repos:</div><div><br></div><div><br></div><div><a href="https://review.opendev.org/q/project:openstack%252Fos-apply-config+status:open+branch:stable/ussuri" target="_blank">https://review.opendev.org/q/project:openstack%252Fos-apply-config+status:open+branch:stable/ussuri</a><br><a href="https://review.opendev.org/q/project:openstack%252Fos-collect-config+status:open+branch:stable/ussuri" target="_blank">https://review.opendev.org/q/project:openstack%252Fos-collect-config+status:open+branch:stable/ussuri</a><br><a href="https://review.opendev.org/q/project:openstack%252Fos-net-config+status:open+branch:stable/ussuri" target="_blank">https://review.opendev.org/q/project:openstack%252Fos-net-config+status:open+branch:stable/ussuri</a><br><a href="https://review.opendev.org/q/project:openstack%252Fos-refresh-config+status:open+branch:stable/ussuri" target="_blank">https://review.opendev.org/q/project:openstack%252Fos-refresh-config+status:open+branch:stable/ussuri</a><br><a href="https://review.opendev.org/q/project:openstack%252Fpaunch+status:open+branch:stable/ussuri" target="_blank">https://review.opendev.org/q/project:openstack%252Fpaunch+status:open+branch:stable/ussuri</a><br><a href="https://review.opendev.org/q/project:openstack%252Fpuppet-tripleo+status:open+branch:stable/ussuri" target="_blank">https://review.opendev.org/q/project:openstack%252Fpuppet-tripleo+status:open+branch:stable/ussuri</a><br><a href="https://review.opendev.org/q/project:openstack%252Fpython-tripleoclient+status:open+branch:stable/ussuri" target="_blank">https://review.opendev.org/q/project:openstack%252Fpython-tripleoclient+status:open+branch:stable/ussuri</a><br><a href="https://review.opendev.org/q/project:openstack%252Ftripleo-ansible+status:open+branch:stable/ussuri" target="_blank">https://review.opendev.org/q/project:openstack%252Ftripleo-ansible+status:open+branch:stable/ussuri</a><br><a href="https://review.opendev.org/q/project:openstack%252Ftripleo-common+status:open+branch:stable/ussuri" target="_blank">https://review.opendev.org/q/project:openstack%252Ftripleo-common+status:open+branch:stable/ussuri</a><br><a href="https://review.opendev.org/q/project:openstack%252Ftripleo-heat-templates+status:open+branch:stable/ussuri" target="_blank">https://review.opendev.org/q/project:openstack%252Ftripleo-heat-templates+status:open+branch:stable/ussuri</a><br><a href="https://review.opendev.org/q/project:openstack%252Ftripleo-image-elements+status:open+branch:stable/ussuri" target="_blank">https://review.opendev.org/q/project:openstack%252Ftripleo-image-elements+status:open+branch:stable/ussuri</a><br><a href="https://review.opendev.org/q/project:openstack%252Ftripleo-ipsec+status:open+branch:stable/ussuri" target="_blank">https://review.opendev.org/q/project:openstack%252Ftripleo-ipsec+status:open+branch:stable/ussuri</a><br><a href="https://review.opendev.org/q/project:openstack%252Ftripleo-puppet-elements+status:open+branch:stable/ussuri" target="_blank">https://review.opendev.org/q/project:openstack%252Ftripleo-puppet-elements+status:open+branch:stable/ussuri</a><br><a href="https://review.opendev.org/q/project:openstack%252Ftripleo-validations+status:open+branch:stable/ussuri" target="_blank">https://review.opendev.org/q/project:openstack%252Ftripleo-validations+status:open+branch:stable/ussuri</a><br></div><div><br></div><div><br></div><div>I'll bring this up again in #tripleo next week and see if there are any objections, otherwise we can call it and start getting folks to close out those open reviews and stop posting new ones,</div><div><br></div><div>thanks, marios</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 16, 2022 at 5:45 PM Marios Andreou <<a href="mailto:marios@redhat.com" target="_blank">marios@redhat.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 dir="ltr">Hello TripleO o/<br><br>The tripleo-ci team proposes that we move the stable/ussuri branch for all tripleo repos [1] to End of Life [2].<br><br>The branch was moved to extended maintenance with [3] so we can already no longer make any new releases for ussuri/tripleo repos. <br><br>Are there any objections or concerns about this? If so please speak up here or directly on the patch. I think that any patches posted to ussuri nowadays are mainly about cherrypicking back to train, rather than merging something to ussuri specifically.<br><br>I have posted the proposal to move to EOL at [4] and have WF-1 to wait for this discussion.<br><br>If there are no objections then once we move to EOL the tripleo-ci team will remove all Ussuri related CI, check/gate/promotions.<br><br>regards, marios<br><br>[1] <a href="https://releases.openstack.org/teams/tripleo.html#ussuri" target="_blank">https://releases.openstack.org/teams/tripleo.html#ussuri</a><br>[2] <a href="https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases" target="_blank">https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases</a><br>[3] <a href="https://review.opendev.org/c/openstack/releases/+/817623" target="_blank">https://review.opendev.org/c/openstack/releases/+/817623</a><br>[4] <a href="https://review.opendev.org/c/openstack/releases/+/834049" target="_blank">https://review.opendev.org/c/openstack/releases/+/834049</a><br></div>
</blockquote></div>
</blockquote></div></div>
</blockquote></div>
</blockquote></div></div>