[TripleO] Moving stable/rocky for *-tripleo-* repos to End of Life OK?
Hello all, it's been ~ 2 months now since my initial mail about $subject [1] and just under a month since my last bump on the thread [2] and I haven't heard any objections so far. So I think it's now appropriate to move forward with [3] which tags the latest commits to the stable/rocky branch of all tripleo-repos [4] as 'rock-eol' (except archived things like instack/tripleo-ui). Once it merges we will no longer be able to land anything into stable/rocky for all tripleo repos and the stable/rocky branch will be deleted. So, last chance! If you object please go and -1 the patch at [3] and/or reply here thanks, marios [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019338.... [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019860.h... [3] https://review.opendev.org/c/openstack/releases/+/774244 [4] https://releases.openstack.org/teams/tripleo.html
On Fri, Feb 5, 2021 at 4:40 PM Marios Andreou <marios@redhat.com> wrote:
Hello all,
it's been ~ 2 months now since my initial mail about $subject [1] and just under a month since my last bump on the thread [2] and I haven't heard any objections so far.
So I think it's now appropriate to move forward with [3] which tags the latest commits to the stable/rocky branch of all tripleo-repos [4] as 'rock-eol' (except archived things like instack/tripleo-ui).
Once it merges we will no longer be able to land anything into stable/rocky for all tripleo repos and the stable/rocky branch will be deleted.
So, last chance! If you object please go and -1 the patch at [3] and/or reply here
bump - there has been some discussion on the proposal at https://review.opendev.org/c/openstack/releases/+/774244 which is now resolved. I just removed my blocking workflow -1 at releases/+/774244 so really really last chance now ;) regards, marios
thanks, marios
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019338.... [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019860.h... [3] https://review.opendev.org/c/openstack/releases/+/774244 [4] https://releases.openstack.org/teams/tripleo.html
On Fri, Feb 12, 2021 at 5:38 PM Marios Andreou <marios@redhat.com> wrote:
On Fri, Feb 5, 2021 at 4:40 PM Marios Andreou <marios@redhat.com> wrote:
Hello all,
it's been ~ 2 months now since my initial mail about $subject [1] and just under a month since my last bump on the thread [2] and I haven't heard any objections so far.
So I think it's now appropriate to move forward with [3] which tags the latest commits to the stable/rocky branch of all tripleo-repos [4] as 'rock-eol' (except archived things like instack/tripleo-ui).
Once it merges we will no longer be able to land anything into stable/rocky for all tripleo repos and the stable/rocky branch will be deleted.
So, last chance! If you object please go and -1 the patch at [3] and/or reply here
(explicitly added some folks into cc for attention please) Thanks to Elod, I just updated/posted v2 of the proposal at https://review.opendev.org/c/openstack/releases/+/774244 Harald, Slawek, Tom, o/ please check the comments at https://review.opendev.org/c/openstack/releases/+/774244/1/deliverables/rock... . The question is - do you really need this on stable/rocky in and of itself, or, rather because that branch is still active, and we needed it on the previous, i.e. queens? Basically sanity check again so there is no confusion later ;) do you folks object to us declaring stable/rocky as EOL? thank you! regards, marios
bump - there has been some discussion on the proposal at https://review.opendev.org/c/openstack/releases/+/774244 which is now resolved.
I just removed my blocking workflow -1 at releases/+/774244 so really really last chance now ;)
regards, marios
thanks, marios
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019338.... [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019860.h... [3] https://review.opendev.org/c/openstack/releases/+/774244 [4] https://releases.openstack.org/teams/tripleo.html
On 01/03/21 11:46 +0200, Marios Andreou wrote:
On Fri, Feb 12, 2021 at 5:38 PM Marios Andreou <marios@redhat.com> wrote:
On Fri, Feb 5, 2021 at 4:40 PM Marios Andreou <marios@redhat.com> wrote:
Hello all,
it's been ~ 2 months now since my initial mail about $subject [1] and just under a month since my last bump on the thread [2] and I haven't heard any objections so far.
So I think it's now appropriate to move forward with [3] which tags the latest commits to the stable/rocky branch of all tripleo-repos [4] as 'rock-eol' (except archived things like instack/tripleo-ui).
Once it merges we will no longer be able to land anything into stable/rocky for all tripleo repos and the stable/rocky branch will be deleted.
So, last chance! If you object please go and -1 the patch at [3] and/or reply here
(explicitly added some folks into cc for attention please)
Thanks to Elod, I just updated/posted v2 of the proposal at https://review.opendev.org/c/openstack/releases/+/774244
Harald, Slawek, Tom, o/ please check the comments at https://review.opendev.org/c/openstack/releases/+/774244/1/deliverables/rock... .
The question is - do you really need this on stable/rocky in and of itself, or, rather because that branch is still active, and we needed it on the previous, i.e. queens?
Basically sanity check again so there is no confusion later ;) do you folks object to us declaring stable/rocky as EOL?
I have no objection to declaring stable/rocky as EOL - the change I proposed there was part of a series of backports from master back to stable/queens. I posted it to stable/rocky along the way since that branch was not EOL and I didn't want to leave a gap in the series of backports.
thank you!
regards, marios
bump - there has been some discussion on the proposal at https://review.opendev.org/c/openstack/releases/+/774244 which is now resolved.
I just removed my blocking workflow -1 at releases/+/774244 so really really last chance now ;)
regards, marios
thanks, marios
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019338.... [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019860.h... [3] https://review.opendev.org/c/openstack/releases/+/774244 [4] https://releases.openstack.org/teams/tripleo.html
On Mon, Mar 1, 2021 at 2:22 PM Tom Barron <tpb@dyncloud.net> wrote:
On 01/03/21 11:46 +0200, Marios Andreou wrote:
On Fri, Feb 12, 2021 at 5:38 PM Marios Andreou <marios@redhat.com> wrote:
On Fri, Feb 5, 2021 at 4:40 PM Marios Andreou <marios@redhat.com>
wrote:
Hello all,
it's been ~ 2 months now since my initial mail about $subject [1] and just under a month since my last bump on the thread [2] and I haven't
heard
any objections so far.
So I think it's now appropriate to move forward with [3] which tags the latest commits to the stable/rocky branch of all tripleo-repos [4] as 'rock-eol' (except archived things like instack/tripleo-ui).
Once it merges we will no longer be able to land anything into stable/rocky for all tripleo repos and the stable/rocky branch will be deleted.
So, last chance! If you object please go and -1 the patch at [3] and/or reply here
(explicitly added some folks into cc for attention please)
Thanks to Elod, I just updated/posted v2 of the proposal at https://review.opendev.org/c/openstack/releases/+/774244
Harald, Slawek, Tom, o/ please check the comments at
https://review.opendev.org/c/openstack/releases/+/774244/1/deliverables/rock...
.
The question is - do you really need this on stable/rocky in and of itself, or, rather because that branch is still active, and we needed it on the previous, i.e. queens?
Basically sanity check again so there is no confusion later ;) do you folks object to us declaring stable/rocky as EOL?
I have no objection to declaring stable/rocky as EOL - the change I proposed there was part of a series of backports from master back to stable/queens. I posted it to stable/rocky along the way since that branch was not EOL and I didn't want to leave a gap in the series of backports.
ACK thanks for confirming Tom
thank you!
regards, marios
bump - there has been some discussion on the proposal at https://review.opendev.org/c/openstack/releases/+/774244 which is now resolved.
I just removed my blocking workflow -1 at releases/+/774244 so really really last chance now ;)
regards, marios
thanks, marios
[1]
http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019338....
[2]
http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019860.h...
[3] https://review.opendev.org/c/openstack/releases/+/774244 [4] https://releases.openstack.org/teams/tripleo.html
participants (2)
-
Marios Andreou
-
Tom Barron