[cinder][stable][infra] branch freeze for ocata, pike
On 9/10/20 8:40 AM, ElÅ?d IllÃ©s wrote:
> Hi Infra Team,
> While reviewing Andreas' patch , I have realized, that Cinder's
> stable/ocata and stable/pike branches were not deleted yet, however
> those branches were EOL'd already (see mail below).
> According to the process , since the EOL patches have merged already,
> if @Brian doesn't object, can you please delete
> - cinder stable/ocata
> - cinder stable/pike
I have no objection, but I haven't pushed the infra team about the
actual branch deletion because as far as I know, cinder is the first
project to actually request removal, and I suspect all sorts of stuff
will break. I suggest we wait until at least after RC-time to give us
all one less thing to worry about.
As far as avoiding breakage goes, I put up two patches to devstack so
that it will check out the -eol tag of cinder/brick/cinderclient instead
of the stable branch, but I suspect these only scratch the surface of
what can be broken once the cinder project branches are deleted.
Sean suggested in an earlier thread on this topic  that instead of
deleting very old EM branches that some projects have EOL'd
project-by-project, we should just delete them wholesale across
openstack. That makes a lot of sense to me.
> Thanks in advance,
>  https://review.opendev.org/#/c/750887/
> On 2020. 07. 28. 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.
>> stable/pike: the changes discussed in  have merged, and I've
>> proposed the pike-eol tags .Â Nothing should be merged into
>> stable/pike in any of our code repositories from now until the
>> branches are deleted.
>>  https://review.opendev.org/#/c/742523/