Open Stack

I suppose the corresponding rdo distgit branches will follow suit?
Once again most of the open reviews[6] are backports.

[6]https://review.rdoproject.org/r/q/branch:ussuri-rdo+status:open

On Fri, Mar 18, 2022 at 4:35 PM Marios Andreou <marios at redhat.com> wrote:

>
>
> On Thu, Mar 17, 2022 at 9:20 AM Jiri Podivin <jpodivin at redhat.com> wrote:
>
>> Hi,
>> As far as Tripleo-Validations repo[5] is concerned I don't believe we
>> should see any issues.
>> 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.
>>
>> [5]https://review.opendev.org/admin/repos/openstack/tripleo-validations
>>
>>
> thanks for confirming Jirka
>
> 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:
>
>
>
> https://review.opendev.org/q/project:openstack%252Fos-apply-config+status:open+branch:stable/ussuri
>
> https://review.opendev.org/q/project:openstack%252Fos-collect-config+status:open+branch:stable/ussuri
>
> https://review.opendev.org/q/project:openstack%252Fos-net-config+status:open+branch:stable/ussuri
>
> https://review.opendev.org/q/project:openstack%252Fos-refresh-config+status:open+branch:stable/ussuri
>
> https://review.opendev.org/q/project:openstack%252Fpaunch+status:open+branch:stable/ussuri
>
> https://review.opendev.org/q/project:openstack%252Fpuppet-tripleo+status:open+branch:stable/ussuri
>
> https://review.opendev.org/q/project:openstack%252Fpython-tripleoclient+status:open+branch:stable/ussuri
>
> https://review.opendev.org/q/project:openstack%252Ftripleo-ansible+status:open+branch:stable/ussuri
>
> https://review.opendev.org/q/project:openstack%252Ftripleo-common+status:open+branch:stable/ussuri
>
> https://review.opendev.org/q/project:openstack%252Ftripleo-heat-templates+status:open+branch:stable/ussuri
>
> https://review.opendev.org/q/project:openstack%252Ftripleo-image-elements+status:open+branch:stable/ussuri
>
> https://review.opendev.org/q/project:openstack%252Ftripleo-ipsec+status:open+branch:stable/ussuri
>
> https://review.opendev.org/q/project:openstack%252Ftripleo-puppet-elements+status:open+branch:stable/ussuri
>
> https://review.opendev.org/q/project:openstack%252Ftripleo-validations+status:open+branch:stable/ussuri
>
>
> 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,
>
> thanks, marios
>
>
>
>
>> On Wed, Mar 16, 2022 at 5:45 PM Marios Andreou <marios at redhat.com> wrote:
>>
>>> Hello TripleO o/
>>>
>>> The tripleo-ci team proposes that we move the stable/ussuri branch for
>>> all tripleo repos [1] to End of Life [2].
>>>
>>> The branch was moved to extended maintenance with [3] so we can already
>>> no longer make any new releases for ussuri/tripleo repos.
>>>
>>> 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.
>>>
>>> I have posted the proposal to move to EOL at [4] and have WF-1 to wait
>>> for this discussion.
>>>
>>> If there are no objections then once we move to EOL the tripleo-ci team
>>> will remove all Ussuri related CI, check/gate/promotions.
>>>
>>> regards, marios
>>>
>>> [1] https://releases.openstack.org/teams/tripleo.html#ussuri
>>> [2]
>>> https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases
>>> [3] https://review.opendev.org/c/openstack/releases/+/817623
>>> [4] https://review.opendev.org/c/openstack/releases/+/834049
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220318/9f820bc7/attachment.htm>