On Tue, Jul 7, 2015 at 8:23 PM, Kyle Mestery <[email protected]> wrote:
> After some consultation with Doug and Thierry, we've boiled the change I'm > recommending below down to two options: > > 1. independent, ad-hoc backport branches, tag yourself > This makes sense. Standard instructions on tagging/release management will be very helpful so all the people can follow the same source when releasing. 2. cycle-with-intermediary, stable branches, tag by RelMgt team > > I think what we really want is option #1 for these projects. I'd like all > of them to be the same here, so if people are thinking differently, please > reply on this thread. I'll update the patches to reflect the fact we'll be > in charge of the ad-hoc branches and tags in the Neutron Stadium. > > Thanks! > Kyle > > > On Mon, Jul 6, 2015 at 12:20 PM, Kyle Mestery <[email protected]> wrote: > >> The tl;dr for this email is that the patch referenced here [1] is moving >> release management tasks for the networking-foo projects into alignment >> with other Neutron libraries. There is value in having this consolidated >> into a single place. >> >> The longer version is that as plugin backends and new libraries have >> integrated into the Neutron Stadium, it makes sense to align some release >> items here. For example, merge commits, tags, and stable branch management >> aspects are things which are best done by a central team for all >> networking-foo projects (along with existing projects). In particular, >> stable releases have some specific requirements [2] which need to be met as >> stable releases are done here. Ensuring this is following existing >> processes is part of the reason for this gerrit ACL change. >> >> Please comment on the reviews if you have concerns as a networking-foo >> owner. >> >> Thanks! >> Kyle >> >> [1] https://review.openstack.org/#/c/198749/ >> [2] https://wiki.openstack.org/wiki/StableBranch >> > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
