On Thu, Dec 3, 2015 at 10:06 PM, Vasudevan, Swaminathan (PNB Roseville) < swaminathan.vasude...@hpe.com> wrote:
> Hi Carl, > Sounds reasonable suggestion. > Thanks > Swami > > -----Original Message----- > From: Carl Baldwin [mailto:c...@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 specific dashboard. > 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 new features. > 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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
