Hi, First of all, sorry for the late response. About EOLing Ocata and Pike: Extended Maintenance was formed just to have a common place for interested parties, vendors, operators, to push bugfixes to. Currently these branches are in a good shape, check / gate jobs work and as far as I see there are a couple of backports, too (not too many, though). So hopefully it's not a waste of efforts. Why don't we keep them open as long as the CI works and there are patches? Of course, whenever e.g. Ocata branch / CI becomes unmaintainable (zuul v3 incompatibilities) or there aren't anyone who fixes the issues there, we can put it to EOL then. I write this, because my employer supports Extended Maintenance, and I usually try to fix CI issues on stable branches and reviewing patches there. So maybe I can be some help here, too. Please consider leaving branches in Extended Maintenance open as long as they are in a good shape and there are bugfixes coming. Thanks, Előd On 2019. 11. 25. 20:21, Brian Rosmaita wrote:
This is a courtesy notice that having received no responses to my email of 28 October [0] proposing to EOL some currently open Cinder branches, and following the policy articulated in [1], at today's Virtual PTG meeting the Cinder project team has decided to put the following stable branches into the End of Life state: driverfixes/mitaka driverfixes/newton stable/ocata stable/pike
I will submit the paperwork to get this process moving one week from today (2 December 2019).
cheers, brian
[0] http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010385.h... [1] https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-li...