<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 23 November 2015 at 04:02, Rossella Sblendido <span dir="ltr"><<a href="mailto:rsblendido@suse.com" target="_blank">rsblendido@suse.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class=""><br>
<br>
On 11/20/2015 03:54 AM, Armando M. wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">
<br>
<br>
On 19 November 2015 at 18:26, Assaf Muller <<a href="mailto:amuller@redhat.com" target="_blank">amuller@redhat.com</a><br></span><span class="">
<mailto:<a href="mailto:amuller@redhat.com" target="_blank">amuller@redhat.com</a>>> wrote:<br>
<br>
On Wed, Nov 18, 2015 at 9:14 PM, Armando M. <<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a><br></span><span class="">
<mailto:<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a>>> wrote:<br>
> Hi Neutrites,<br>
><br>
> We are nearly two weeks away from the end of Mitaka 1.<br>
><br>
> I am writing this email to invite you to be mindful to what you review,<br>
> especially in the next couple of weeks. Whenever you have the time to review<br>
> code, please consider giving priority to the following:<br>
><br>
> Patches that target blueprints targeted for Mitaka;<br>
> Patches that target bugs that are either critical or high;<br>
> Patches that target rfe-approved 'bugs';<br>
> Patches that target specs that have followed the most current submission<br>
> process;<br>
<br>
Is it possible to create Gerrit dashboards for patches that answer these<br>
criteria, and then persist the links in Neutron's dashboards devref<br>
page?<br>
<a href="http://docs.openstack.org/developer/neutron/dashboards/index.html" rel="noreferrer" target="_blank">http://docs.openstack.org/developer/neutron/dashboards/index.html</a><br>
That'd be super useful.<br>
<br>
<br>
We should look into that, but to be perfectly honest I am not sure how<br>
easy it would be, since we'd need to cross-reference content that lives<br>
into gerrit as well as launchpad. Would that even be possible?<br>
</span></blockquote>
<br>
To cross-reference we can use the bug ID or the blueprint name.<br>
<br>
I created a script that queries launchpad to get:<br>
1) Bug number of the bugs tagged with approved-rfe<br>
2) Bug number of the critical/high bugs<br>
3) list of blueprints targeted for the current milestone (mitaka-1)<br>
<br>
With this info the script builds a .dash file that can be used by gerrit-dash-creator [2] to produce a dashboard url .<br>
<br>
The script prints also the queries that can be used in gerrit UI directly, e.g.:<br>
Critical/High Bugs<br>
(topic:bug/1399249 OR topic:bug/1399280 OR topic:bug/1443421 OR topic:bug/1453350 OR topic:bug/1462154 OR topic:bug/1478100 OR topic:bug/1490051 OR topic:bug/1491131 OR topic:bug/1498790 OR topic:bug/1505575 OR topic:bug/1505843 OR topic:bug/1513678 OR topic:bug/1513765 OR topic:bug/1514810)<br>
<br>
<br>
This is the dashboard I get right now [3]<br>
<br>
I tried in many ways to get Gerrit to filter patches if the commit message contains a bug ID. Something like:<br>
<br>
(message:"#1399249" OR message:"#1399280" OR message:"#1443421" OR message:"#1453350" OR message:"#1462154" OR message:"#1478100" OR message:"#1490051" OR message:"#1491131" OR message:"#1498790" OR message:"#1505575" OR message:"#1505843" OR message:"#1513678" OR message:"#1513765" OR message:"#1514810")<br>
<br>
but it doesn't work well, the result of the filter contains patches that have nothing to do with the bugs queried.<br></blockquote><div><br></div><div>Try to drop the # and quote the bug number like this:</div><div><br></div><div>message:"'1399280'" </div><div><br></div><div>Otherwise I believe gerrit looks for substring matches.</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
That's why I had to filter using the topic.<br>
<br>
CAVEAT: To make the dashboard work, bug fixes must use the topic "bug/ID" and patches implementing a blueprint the topic "bp/name". If a patch is not following this convention it won't be showed in the dashboard, since the topic is used as filter. Most of us use this convention already anyway so I hope it's not too much of a burden.<br>
<br>
Feedback is appreciated :)<br></blockquote><div><br></div><div>Nice one, I'll provide feedback on [1].</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
[1] <a href="https://review.openstack.org/248645" rel="noreferrer" target="_blank">https://review.openstack.org/248645</a><br>
[2] <a href="https://github.com/openstack/gerrit-dash-creator" rel="noreferrer" target="_blank">https://github.com/openstack/gerrit-dash-creator</a><br>
[3] <a href="https://goo.gl/sglSbp" rel="noreferrer" target="_blank">https://goo.gl/sglSbp</a><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div class="h5">
<br>
Btw, I was looking at the current blueprint assignments [1] for Mitaka:<br>
there are some blueprints that still need assignee, approver and<br>
drafter; we should close the gap. If there are volunteers, please reach<br>
out to me.<br>
<br>
Thanks,<br>
Armando<br>
<br>
[1] <a href="https://blueprints.launchpad.net/neutron/mitaka/+assignments" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/neutron/mitaka/+assignments</a><br>
<br>
<br>
><br>
> Everything else should come later, no matter how easy or interesting it is<br>
> to review; remember that as a community we have the collective duty to work<br>
> towards a common (set of) target(s), as being planned in collaboration with<br>
> the Neutron Drivers team and the larger core team.<br>
><br>
> I would invite submitters to ensure that the Launchpad resources<br>
> (blueprints, and bug report) capture the most updated view in terms of<br>
> patches etc. Work with your approver to help him/her be focussed where it<br>
> matters most.<br>
><br>
> Finally, we had plenty of discussions at the design summit, and some of<br>
> those discussions will have to be followed up with actions (aka code in<br>
> OpenStack lingo). Even though, we no longer have deadlines for feature<br>
> submission, I strongly advise you not to leave it last minute. We can only<br>
> handle so much work for any given release, and past experience tells us that<br>
> we can easily hit a breaking point at around the ~30 blueprint mark.<br>
><br>
> Once we reached it, it's likely we'll have to start pushing back work for<br>
> Mitaka and allow us some slack; things are fluid as we all know, and the<br>
> random gate breakage is always lurking round the corner! :)<br>
><br>
> Happy hacking,<br>
> Armando<br>
><br>
><br>
__________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe:<br>
<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></div></div>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><span class=""><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>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<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></span>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><span class=""><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>
<br>
<br>
<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>
</span></blockquote><div class=""><div class="h5">
<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>
</div></div></blockquote></div><br></div></div>