stable/essex is maintained by ~openstack-essex-maint

[Thierry Carrez]

stable/* branches are currently maintained in Gerrit by ~openstack-stable-maint

As described in https://wiki.openstack.org/wiki/StableBranch, only the most recent release is maintained by that team. Previous releases are maintained by specific teams. In particular Essex is maintained by the ~openstack-essex-maint team.

Gerrit needs to be aligned with policy.

[Jeremy Stanley (fungi)]

This was easy, so I went ahead and implemented it just now. I added the openstack-diablo-maint and openstack-essex-maint groups in Gerrit and gave them the same (worryingly small) list of members. I duplicated the permissions openstack-stable-maint has over refs/heads/stable/* to refs/heads/stable/diablo and essex for these new groups, including the same exclusive rights. I believe this will have the effect that openstack-stable-maint no longer has control over diablo and essex. Was that the intent (the wiki is a bit vague on that point), or should it also be an included member of those two other groups?

[Thierry Carrez (ttx)]

no, that's the intent. Stable-maint only cares about the most recent stable release.

[Alan Pevec (apevec)]

> Stable-maint only cares about the most recent stable release.

Actually, at H summit session[1] we said stable-maint will now take care of N-1 too i.e. during H cycle, we take care of both stable/folsom and stable/grizzly while stable/diablo and stable/essex go EOL.

[1] https://etherpad.openstack.org/havana-stable-branch

[Jeremy Stanley (fungi)]

Good point. I've just now emptied the openstack-diablo-maint and openstack-essex-maint groups in Gerrit and hidden them from non-administrators (Gerrit does not provide a simple way to delete internal groups). We'll probably go through the DB and clean up unused empty groups at some point.