<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 1, 2015 at 5:57 AM, Tom Barron <span dir="ltr"><<a href="mailto:tpb@dyncloud.net" target="_blank">tpb@dyncloud.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">[Yesterday while discussing the following issue on IRC, jgriffith<br>
suggested that I post to the dev list in preparation for a discussion in<br>
Wednesday's cinder meeting.]<br>
<br>
Please take a look at the 10 "Low" priority reviews in the cinder<br>
Liberty 3 etherpad that were punted to Mitaka yesterday. [1]<br>
<br>
Six of these *never* [2] received a vote from a core reviewer. With the<br>
exception of the first in the list, which has 35 patch sets, none of the<br>
others received a vote before Friday, August 28. Of these, none had<br>
more than -1s on minor issues, and these have been remedied.<br>
<br>
Review <a href="https://review.openstack.org/#/c/213855" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/213855</a> "Implement<br>
manage/unmanage snapshot in Pure drivers" is a great example:<br>
<br>
* approved blueprint for a valuable feature<br>
* pristine code<br>
* passes CI and Jenkins (and by the deadline)<br>
* never reviewed<br>
<br>
We have 11 core reviewers, all of whom were very busy doing reviews<br>
during L3, but evidently this set of reviews didn't really have much<br>
chance of making it. This looks like a classic case where the<br>
individually rational priority decisions of each core reviewer<br>
collectively resulted in starving the Low Priority review queue.<br>
<br>
One way to remedy would be for the 11 core reviewers to devote a day or<br>
two to cleaning up this backlog of 10 outstanding reviews rather than<br>
punting all of them out to Mitaka.<br>
<br>
Thanks for your time and consideration.<br>
<br>
Respectfully,<br>
<br>
-- Tom Barron<br>
<br>
[1] <a href="https://etherpad.openstack.org/p/cinder-liberty-3-reviews" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/cinder-liberty-3-reviews</a><br>
[2] At the risk of stating the obvious, in this count I ignore purely<br>
procedural votes such as the final -2.<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>
</blockquote></div><br></div><div class="gmail_extra"><div class="gmail_default" style="font-family:monospace,monospace">Thanks Tom, this is sadly an ongoing problem every release. I think we have a number of things we can talk about at the summit to try and make some of this better. I honestly think that if people were to actually "use" launchpad instead of creating tracking etherpads everywhere it would help. What I mean is that there is a ranked targeting of items in Launchpad and we should use it, core team members should know that as the source of truth and things that must get reviewed.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">As far as Liberty and your patches; Yesterday was the freeze point, the entire Cinder team agreed on that (yourself included both at the mid-cycle meet up and at the team meeting two weeks ago when Thingee reiterated the deadlines). If you noticed last week that your patches weren't going anywhere YOU should've wrangled up some reviews.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">Furthermore, I've explained every release for the last 3 or 4 years that there's no silver bullet, no magic process when it come to review throughput. ESPECIALLY when it comes to the 3'rd milestone. You can try landing strips, priority listed etherpads, sponsors etc etc but the fact is that things happen, the gate slows down (or we completely break on the Cinder side like we did yesterday). This doesn't mean "oh, well then you get another day or two", it means stuff happens and it sucks but first course of action is drop low priority items. It just means if you really wanted it you probably should've made it happen earlier. Just so you know, I run into this every release as well. I had a number of things in progress that I had hoped to finish last week and yesterday, BUT my priority shifted to trying to help get the cinder patches back on track and get the items in Launchpad updated to actually reflect something that was somewhat possible.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">The only thing that works is "submit early and review often" it's simple.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">Finally, I pointed out to you yesterday that we could certainly discuss as a team what to do with your patches. BUT that given how terribly far behind we were in the process that I wanted reviewers to focus on medium, high and critical prioritized items. That's what prioritization's are for, it means when crunch time hits and things hit the fan it's usually the "low" priority things that get bumped.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">Thanks,</div><div class="gmail_default" style="font-family:monospace,monospace">John</div><br></div></div>