On Mon, Jul 6, 2015 at 10:42 PM, Takashi Yamamoto <[email protected]> wrote:
> On Tue, Jul 7, 2015 at 10:44 AM, Kyle Mestery <[email protected]> wrote: > > On Mon, Jul 6, 2015 at 5:07 PM, Takashi Yamamoto <[email protected]> > > wrote: > >> > >> hi, > >> > >> On Tue, Jul 7, 2015 at 2:20 AM, 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. > >> > >> can you explain how release procedure will be changed? > >> > > > > Sure. We'll rely on the release team to help us release these backend > > libraries and API repositories. These are the same folks doing releases > for > > both clients and oslo libraries. > > so, basically a maintainer of networking-foo will ask the release team > to push a tag? > > Yes. And the neutron-stable-maint team will handle stable backports as well. > > > >> > >> > > >> > 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 > > > > > > > > > __________________________________________________________________________ > > 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 >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
