Open Stack

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 not yet for or against, I'm just trying to think what the commit
> messages are going to end up looking like...
>
> Ryan Moats (regXboi)
>
> Oleg Bondarev <obondarev at mirantis.com> wrote on 12/04/2015 02:44:58 AM:
>
> > From: Oleg Bondarev <obondarev at mirantis.com>
> > To: "OpenStack Development Mailing List (not for usage questions)"
> > <openstack-dev at lists.openstack.org>
> > Date: 12/04/2015 02:46 AM
> > Subject: Re: [openstack-dev] [Neutron][DVR]
>
> >
> > On Thu, Dec 3, 2015 at 10:06 PM, Vasudevan, Swaminathan (PNB Roseville) <
> > swaminathan.vasudevan at hpe.com> wrote:
> > Hi Carl,
> > Sounds reasonable suggestion.
> > Thanks
> > Swami
> >
> > -----Original Message-----
> > From: Carl Baldwin [mailto:carl at ecbaldwin.net <carl at ecbaldwin.net>]
> > Sent: Thursday, December 03, 2015 10:47 AM
> > To: OpenStack Development Mailing List
> > Subject: [openstack-dev] [Neutron][DVR]
> >
> > I was going to bring this up in the meeting this morning but IRC
> > troubles prevented it.
> >
> > After chatting with Armando, I'd like to suggest a few enhancements
> > to how we're tackling DVR during this cycle.  I'm hoping that these
> > changes help us to get things done faster and more efficiently.  Let
> > me know if you think otherwise.
> >
> > First, I'd like to suggest adding DvrImpact to the comment of any
> > patches that are meant to improve DVR in some way.  People have
> > asked me about reviewing DVR changes.  I can show them the DVR
> > backlog [1] in launchpad but it would be nice to have a DVR
> specificdashboard.
> > With DvrImpact in the subject, we can make it even more convenient
> > to find reviews.
> >
> > +1
> >
> >
> > The other change I'd like to propose is to categorize our DVR
> > backlog in to three categories:  broken, scale (loadimpact), and
> newfeatures.
> > I'd propose that we prioritize in that order.  Anyone have any
> > suggestions for how to tag or otherwise categorize and tackle these?
> >
> > This might be useful but honestly I don't feel a strong need for
> > categorizing dvr bugs at the moment because of the amount of bugs
> > (currently I see 31 when filtering by l3-dvr-backlog tag).
> > l3-dvr-backlog tag + High/Critical may stand for 'broken', l3-dvr-
> > backlog + loadimpact for 'scale', l3-dvr-backlog + Wishlist for new
> > (small) enhancements.
> > I might be missing something though.
> >
> > I know there is a loadimpact (or similar) tag those.  Should we come
> > up with a couple more tags to divide the rest?
> >
> > Thoughts?
> >
> > Carl
> >
> > [1] https://goo.gl/M5SwfS
> >
> >
> __________________________________________________________________________
> > 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
> > 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
> > 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
> 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/20151204/12b8eb5d/attachment.html>