Just discussed with Clark and Fungi on IRC, that since the branches are already tagged (*-eol), merging the patches could cause some confusions. So it's easier to just wait until RC, as Brian suggested. Thanks, Előd On 2020. 09. 10. 18:49, Clark Boylan wrote:
On Thu, Sep 10, 2020, at 5:42 AM, Andreas Jaeger wrote:
On 28.07.20 16:23, Brian Rosmaita wrote:
tl;dr - do not approve any backports to stable/ocata or stable/pike in any Cinder project deliverable
stable/ocata has been tagged with ocata-eol in cinder, os-brick, python-cinderclient, and python-brick-cinderclient-ext. Nothing should be merged into stable/ocata in any of these repositories during the interim period before the branches are deleted. When do you plan to delete those branches? We have Zuul jobs that are broken, for example due to removal of devstack-plugin-zmq and we either should remove these from the branch or delete the branch. Currently Zuul complains about broken jobs.
The two changes I talk about are: https://review.opendev.org/750887 https://review.opendev.org/750886 I think we should go ahead and land those if we are waiting for a coordinated branch deletion. The zuul configs are branch specific and should be adjustable outside of normal backport procedures, particularly if they are causing problems like global zuul config errors. We've force merged some of these changes on stable branches in other projects if CI is generally unstable. Let us know if that is appropriate for this situation as well.
Andreas
stable/pike: the changes discussed in [0] have merged, and I've proposed the pike-eol tags [1]. Nothing should be merged into stable/pike in any of our code repositories from now until the branches are deleted.
[0] http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016076.html