[TripleO] tripleo repos going Extended Maintenance stable/train OK? (not yet IMO)
Hello TripleO o/ per [1] and the proposal at [2] the stable/train branch for all tripleo repos [3] is going to transition to extended maintenance [4]. Once [2] merges, we can still merge things to stable/train but it means we can no longer make official openstack tagged releases for stable/train. TripleO is a trailing project so if we want to hold on this for a while longer I think that is OK and that would also be my personal preference.
From a quick check just now e.g. tripleo-heat-templates @ [5] and at current time there are 87 commits since last September which isn't a tiny amount. So I don't think TripleO is ready to declare stable/train as extended maintenance, but perhaps I am wrong, what do you think?
Please comment here or directly at [2] if you prefer regards, marios [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-May/022287.html [2] https://review.opendev.org/c/openstack/releases/+/790778/2#message-e981f749a... [3] https://releases.openstack.org/teams/tripleo.html#train [4] https://docs.openstack.org/project-team-guide/stable-branches.html#maintenan... [5] https://github.com/openstack/tripleo-heat-templates/compare/11.5.0...stable/...
Hello all, as discussed at [1] the train branch across all tripleo repos will be moving to extended maintenance at the end of this week. Before we make the train-em tag I have pushed one last release on train with [2] and rebased [1] onto that. As discussed in [1] train is still an active branch for tripleo and we can and will continue to merge fixes there. It just means that we will no longer be making tagged releases for train branches. If you have any questions or concerns about any of this please reach out, regards, marios [1] https://review.opendev.org/c/openstack/releases/+/790778/2#message-e8ee1f6fe... [2] https://review.opendev.org/c/openstack/releases/+/794583 On Thu, May 13, 2021 at 3:47 PM Marios Andreou <marios@redhat.com> wrote:
Hello TripleO o/
per [1] and the proposal at [2] the stable/train branch for all tripleo repos [3] is going to transition to extended maintenance [4].
Once [2] merges, we can still merge things to stable/train but it means we can no longer make official openstack tagged releases for stable/train.
TripleO is a trailing project so if we want to hold on this for a while longer I think that is OK and that would also be my personal preference.
From a quick check just now e.g. tripleo-heat-templates @ [5] and at current time there are 87 commits since last September which isn't a tiny amount. So I don't think TripleO is ready to declare stable/train as extended maintenance, but perhaps I am wrong, what do you think?
Please comment here or directly at [2] if you prefer
regards, marios
[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-May/022287.html [2] https://review.opendev.org/c/openstack/releases/+/790778/2#message-e981f749a... [3] https://releases.openstack.org/teams/tripleo.html#train [4] https://docs.openstack.org/project-team-guide/stable-branches.html#maintenan... [5] https://github.com/openstack/tripleo-heat-templates/compare/11.5.0...stable/...
On 3 Jun 2021, at 13:57, Marios Andreou <marios@redhat.com> wrote:
Hello all,
as discussed at [1] the train branch across all tripleo repos will be moving to extended maintenance at the end of this week. Before we make the train-em tag I have pushed one last release on train with [2] and rebased [1] onto that.
As discussed in [1] train is still an active branch for tripleo and we can and will continue to merge fixes there. It just means that we will no longer be making tagged releases for train branches.
If you have any questions or concerns about any of this please reach out,
I think this would be problematic for us. We’re still actively submitting changes to stable/train for tripleo and will likely be for some time. I don’t know what the effect is to us downstream for not being able to tag upstream. I think the RDO folks (who do the packaging) would need to respond to that for us to make a suitable final call.
On Thursday, June 3, 2021, Jesse Pretorius <jpretori@redhat.com> wrote:
On 3 Jun 2021, at 13:57, Marios Andreou <marios@redhat.com> wrote:
Hello all,
as discussed at [1] the train branch across all tripleo repos will be moving to extended maintenance at the end of this week. Before we make the train-em tag I have pushed one last release on train with [2] and rebased [1] onto that.
As discussed in [1] train is still an active branch for tripleo and we can and will continue to merge fixes there. It just means that we will no longer be making tagged releases for train branches.
If you have any questions or concerns about any of this please reach out,
I think this would be problematic for us. We’re still actively submitting changes to stable/train for tripleo and will likely be for some time.
yes agree but this does not stop us from continuing to merge whatever we need across train tripleo repos. It only affects tagged releases.
I don’t know what the effect is to us downstream for not being able to tag upstream. I think the RDO folks (who do the packaging) would need to respond to that for us to make a suitable final call.
As far as I know there is no direct correlation between upstream git repo tags and downstream packaging. I believe the import point used is a particular commit hash for a given repo. I'll reach out to rhos delivery folks and point at this email though to confirm. If there is a problem I am not sure how we can resolve it as it sounds like this is a mandatory move for us per the discussion at https://review.opendev.org/c/openstack/releases/+/790778/2#message-e8ee1f6fe... But let's see what packaging folks think thanks for the suggestion regards, marios -- _sent from my mobile - sorry for spacing spelling etc_
participants (2)
-
Jesse Pretorius
-
Marios Andreou