Hi, There was no volunteers who would like to keep stable/pike and/or stable/ queens for networking-bagpipe and networking-bgpvpn so I just proposed procedure to make it EOL. Patches for that are here: https://review.opendev.org/c/openstack/releases/+/804351/ https://review.opendev.org/c/openstack/releases/+/804352/ On czwartek, 5 sierpnia 2021 12:20:28 CEST you wrote:
Hi,
Regarding recent email from Elod [1] CI of the stable/pike and stable/queens branches in networking-bgpvpn is broken now. I checked that it's due to Horizon which is already EOL in those branches. I proposed patch [2] to hopefully fix it quickly by using eol tag of Horizon. But even with that there are some other problems in the openstack-tox-pep8 and networking-bgpvpn-dsvm-functional jobs. Last merged patches in networking-bgpvpn were in 2019: [3] and [4]. Giving all that I propose to make networking-bgpvpn stable/pike and stable/ queens branches to be EOL now.
Networking-bagpipe project is tightly coupled with networking-bgpvpn. Last patches merged in that project were also in 2019: [5] and [6]. Because of the above, I propose also to make branches stable/pike and stable/ queens in the networking-bagpipe to be EOL.
I will wait until end of next week for anyone who would like to maybe step up as maintainer of those branches. If there will be no volunteers for that, I will EOL those branches in networking-bgpvpn and networking-bagpipe.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/ 023944.html [2] https://review.opendev.org/c/openstack/networking-bgpvpn/+/803545 [3] https://review.opendev.org/q/project:openstack/networking-bgpvpn+branch:stab... e/queens [4] https://review.opendev.org/q/project:openstack/networking-bgpvpn+branch:stab... e/queens [5] https://review.opendev.org/q/project:openstack/networking-bagpipe+branch:sta... le/queens [6] https://review.opendev.org/q/project:openstack/networking-bagpipe+branch:sta... le/pike
-- Slawek Kaplonski Principal Software Engineer Red Hat