[openstack-dev] [Neutron][DVR]
Armando M.
armamig at gmail.com
Mon Dec 7 16:12:25 UTC 2015
On 7 December 2015 at 05:41, Ryan Moats <rmoats at us.ibm.com> wrote:
> "Armando M." <armamig at gmail.com> wrote on 12/04/2015 03:43:29 PM:
>
> > From: "Armando M." <armamig at gmail.com>
> > To: "OpenStack Development Mailing List (not for usage questions)"
> > <openstack-dev at lists.openstack.org>
> > Date: 12/04/2015 03:44 PM
> > Subject: Re: [openstack-dev] [Neutron][DVR]
> >
> > > On 4 December 2015 at 05:56, Ryan Moats <rmoats at us.ibm.com> wrote:
> > > I pretty much agree with Oleg here - I'm not sure an additional tag
> > > for defects is needed.
> > > The idea of a DvrImpact in the commit message is interesting, but
> > > I'm not entirely convinced - if we
> > > do it for one sub-project, do we need to do it for all sub-projects
> > > and then what does that turn into?
> > What does this mean? No other project should care about this. DVR is
> > a core feature.
>
> I'm trying to understand if (at its logical conclusion) we end up with
> commit tags for all features (i.e. RbacImpact, BareMetalImpact, DbImpact,
> etc.) and what that would do to the commit message...
>
Oh, you mean feature!
Well, even if we did have one per feature, we wouldn't have a single patch
impacting multiple features; patches are meant to be small and cohesive in
nature, and if they impacted more than one area they should be broken down.
>
>
> Ryan Moats (regXboi)
>
> __________________________________________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151207/e7f44853/attachment.html>
More information about the OpenStack-dev
mailing list