<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 4 December 2015 at 05:56, Ryan Moats <span dir="ltr"><<a href="mailto:rmoats@us.ibm.com" target="_blank">rmoats@us.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><p>I pretty much agree with Oleg here - I'm not sure an additional tag for defects is needed.<br>The idea of a DvrImpact in the commit message is interesting, but I'm not entirely convinced - if we<br>do it for one sub-project, do we need to do it for all sub-projects and then what does that turn into?<br></p></div></blockquote><div>What does this mean? No other project should care about this. DVR is a core feature. <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><p><br>I'm not yet for or against, I'm just trying to think what the commit messages are going to end up looking like...<br><br>Ryan Moats (regXboi)<br><br><tt>Oleg Bondarev <<a href="mailto:obondarev@mirantis.com" target="_blank">obondarev@mirantis.com</a>> wrote on 12/04/2015 02:44:58 AM:<br><br>> From: Oleg Bondarev <<a href="mailto:obondarev@mirantis.com" target="_blank">obondarev@mirantis.com</a>></tt><br><tt>> To: "OpenStack Development Mailing List (not for usage questions)" <br>> <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>></tt><br><tt>> Date: 12/04/2015 02:46 AM</tt><br><tt>> Subject: Re: [openstack-dev] [Neutron][DVR]</tt></p><div><div><br><tt>> <br>> On Thu, Dec 3, 2015 at 10:06 PM, Vasudevan, Swaminathan (PNB Roseville) <<br>> <a href="mailto:swaminathan.vasudevan@hpe.com" target="_blank">swaminathan.vasudevan@hpe.com</a>> wrote:</tt><br><tt>> Hi Carl,<br>> Sounds reasonable suggestion.<br>> Thanks<br>> Swami</tt><br><tt>> <br>> -----Original Message-----<br>> From: Carl Baldwin [<a href="mailto:carl@ecbaldwin.net" target="_blank">mailto:carl@ecbaldwin.net</a>]<br>> Sent: Thursday, December 03, 2015 10:47 AM<br>> To: OpenStack Development Mailing List<br>> Subject: [openstack-dev] [Neutron][DVR]<br>> <br>> I was going to bring this up in the meeting this morning but IRC <br>> troubles prevented it.<br>> <br>> After chatting with Armando, I'd like to suggest a few enhancements <br>> to how we're tackling DVR during this cycle. I'm hoping that these <br>> changes help us to get things done faster and more efficiently. Let<br>> me know if you think otherwise.<br>> <br>> First, I'd like to suggest adding DvrImpact to the comment of any <br>> patches that are meant to improve DVR in some way. People have <br>> asked me about reviewing DVR changes. I can show them the DVR <br>> backlog [1] in launchpad but it would be nice to have a DVR specificdashboard.<br>> With DvrImpact in the subject, we can make it even more convenient <br>> to find reviews.</tt><br><tt>> <br>> +1</tt><br><tt>> </tt><br><tt>> <br>> The other change I'd like to propose is to categorize our DVR <br>> backlog in to three categories: broken, scale (loadimpact), and newfeatures.<br>> I'd propose that we prioritize in that order. Anyone have any <br>> suggestions for how to tag or otherwise categorize and tackle these?</tt><br><tt>> <br>> This might be useful but honestly I don't feel a strong need for <br>> categorizing dvr bugs at the moment because of the amount of bugs <br>> (currently I see 31 when filtering by l3-dvr-backlog tag).</tt><br><tt>> l3-dvr-backlog tag + High/Critical may stand for 'broken', l3-dvr-<br>> backlog + loadimpact for 'scale', l3-dvr-backlog + Wishlist for new <br>> (small) enhancements.</tt><br><tt>> I might be missing something though.</tt><br><tt>> </tt><br><tt>> I know there is a loadimpact (or similar) tag those. Should we come<br>> up with a couple more tags to divide the rest?<br>> <br>> Thoughts?<br>> <br>> Carl<br>> <br>> [1] <a href="https://goo.gl/M5SwfS" target="_blank">https://goo.gl/M5SwfS</a><br>> <br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>> <br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></tt><br><tt>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br></tt><br>
</div></div><p></p></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>