[openstack-dev] [neutron] Networking-foo projects and release management in the Neutron Stadium
mestery at mestery.com
Wed Jul 8 18:05:09 UTC 2015
For now, I've modified the patch so everything follows #1. If we "graduate"
some things like l2gw and octavia, we can modify them into #2. Thanks for
On Tue, Jul 7, 2015 at 10:38 PM, Takashi Yamamoto <yamamoto at midokura.com>
> it seems two kinds of sub projects.
> one is vendor plugins, for which option #1 seems appropriate.
> another is things like l2gw and octavia, for which option #2 might
> make more sense.
> On Wed, Jul 8, 2015 at 12:23 AM, Kyle Mestery <mestery at mestery.com> wrote:
> > After some consultation with Doug and Thierry, we've boiled the change
> > recommending below down to two options:
> > 1. independent, ad-hoc backport branches, tag yourself
> > 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
> > 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 <mestery at mestery.com>
> >> The tl;dr for this email is that the patch referenced here  is moving
> >> release management tasks for the networking-foo projects into alignment
> >> 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
> >> items here. For example, merge commits, tags, and stable branch
> >> 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  which need to be
> met as
> >> stable releases are done here. Ensuring this is following existing
> >> 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
> >>  https://review.openstack.org/#/c/198749/
> >>  https://wiki.openstack.org/wiki/StableBranch
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev