On Fri, Feb 12, 2021 at 5:22 PM Alfredo Moralejo Alonso <amoralej@redhat.com> wrote:
Hi,
On Fri, Feb 12, 2021 at 3:32 PM Marios Andreou <marios@redhat.com> wrote:
hello TripleO,
per $subject I want to propose that tripleo-ipsec moves to the independent release model, as done recently for os-collect-config and friends at [1].
The tripleo-ipsec repo hasn't had much/any commits in the last year [2]. In fact, we hadn't even created a ussuri branch for this repo and no-one noticed (!).
Because of the lack of stable/ussuri some of the release jobs failed, as discussed at [3] and which ttx tried to fix (thank you!) with [4].
Unfortunately this hasn't resolved the issue and jobs are still failing, as discussed just now in openstack-release [4]. If we agree to move tripleo-ipsec to independent then it will also resolve this build job issue.
If we move tripleo-ipsec to independent it means we can still release it if required, but we will no longer create stable/branches for the repo.
please voice any objections here or go and comment on the proposal at [6]
The plan is to support any new tripleo-ipsec release on all supported openstack releases or just for master?
honestly I don't expect many/any release requests here. After a while we can likely move this to retirement if no one is using and or maintaining it. But to answer your question and in the general case for any repo, 'I guess not' i.e. we would likely pin for each release as you propose below.
Just be aware that by default RDO follows stable branches for stable releases as it's not recommended to follow master branches in stable releases (although it may be justified in some cases). For projects with independent model you have two options to specify the version used on each stable release:
- Adding it to upper-constraints.txt as RDO follows the versions listed in that file. - Pinning to specific commit or tag in rdoinfo for each release and manually proposing version bumps when needed.
Independent releases need a bit more attention in terms of deciding which version to use on each RDO release, I'm not saying it's a blocker but something to take into account after moving it to independent.
thanks very much for your helpful comments. I think pinning is the way to go here. For this particular repo I don't expect much/any activity to be honest so the overhead of updating/bumping versions will be minimal/non existent. Can you point me to the file and I'll propose a review with the commits? thanks, marios
Regards,
Alfredo
thanks for reading!
regards, marios
[1] https://review.opendev.org/c/openstacreleasereleasek/releases/+/772570 <https://review.opendev.org/c/openstack/releases/+/772570> [2] https://opendev.org/openstack/tripleo-ipsec/commits/branch/master [3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/020112.h... [4] https://review.opendev.org/c/openstack/releases/+/772995 [5] http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-rel... [6] https://review.opendev.org/c/openstack/releases/+/775395