[cinder] train backport potential bugfixes
Brian Rosmaita
rosmaita.fossdev at gmail.com
Mon Sep 30 16:05:58 UTC 2019
With RC-1 released and the stable/train branch cut, any new bugfixes to
be included in the Cinder Train release must be (1) merged to master,
(2) be proposed as backports to stable/train, (3) approved by the cinder
stable-maint team. and (4) merged to stable/train before the final RC
deadline (10 Oct).
If you are working on such a bugfix, please add it to this etherpad:
https://etherpad.openstack.org/p/cinder-train-backport-potential
Keep in mind that the gate is always slow around this time of the cycle,
so the earlier your fixes are proposed, the more likely they are to
actually make it into the release.
If you don't have a Cinder bugfix you're working on now, it would be
helpful if you could do some exploratory testing on Cinder RC-1. You
can checkout the tag from git, or use the release tarball:
https://releases.openstack.org/train/index.html#train-cinder
cheers,
brian
More information about the openstack-discuss
mailing list