[tripleo] moving tripleo-ipsec to independent release model

Marios Andreou marios at redhat.com
Fri Feb 12 14:29:13 UTC 2021


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]

thanks for reading!

regards, marios


[1] 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.html
[4] https://review.opendev.org/c/openstack/releases/+/772995
[5]
http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-release.2021-02-12.log.html
[6] https://review.opendev.org/c/openstack/releases/+/775395
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210212/969b025a/attachment.html>


More information about the openstack-discuss mailing list