On 11 December 2015 at 15:23, Vasudevan, Swaminathan (PNB Roseville) < swaminathan.vasude...@hpe.com> wrote:
> Hi Armando/Carl, > > Yes based on Carl’s recommendation I have categorized the bugs in the Wiki > below right now. If you think adding an Etherpad will be more appropriate, > we can add one. > > > > https://wiki.openstack.org/wiki/Meetings/Neutron-DVR > The wiki works too. Some people may like to go from LP to Gerrit or straight to Gerrit, so it might be worth linking the most current review # to each bug report. > > > > > Thanks > > Swami > > *From:* Armando M. [mailto:arma...@gmail.com] > *Sent:* Friday, December 11, 2015 3:12 PM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [Neutron][DVR] > > > > > > > > On 3 December 2015 at 10:46, Carl Baldwin <c...@ecbaldwin.net> wrote: > > 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. > > 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? > I know there is a loadimpact (or similar) tag those. Should we come > up with a couple more tags to divide the rest? > > Thoughts? > > > > Another alternative would be to capture the list of stuff to review in an > etherpad like [1]. It looks like Nova relies on a similar mechanism [2], > and it sounds it works for them, so it's worth pursuing to see if review > velocity improves. > > > > Thoughts? > > Cheers, > > Armando > > > > [1] https://etherpad.openstack.org/p/neutron-dvr > > [2] https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking > > > > > 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
