[openstack-dev] Fixing the Nova Core Reviewer Frustration [was Re: [Nova] PTL Candidacy]
joe.gordon0 at gmail.com
Tue Apr 7 19:41:31 UTC 2015
On Tue, Apr 7, 2015 at 11:12 AM, Tim Bell <Tim.Bell at cern.ch> wrote:
> > -----Original Message-----
> > From: James Bottomley [mailto:James.Bottomley at HansenPartnership.com]
> > Sent: 07 April 2015 19:03
> > To: Michael Still
> > Cc: OpenStack Development Mailing List (not for usage questions)
> > Subject: [openstack-dev] Fixing the Nova Core Reviewer Frustration [was
> > [Nova] PTL Candidacy]
> > On Tue, 2015-04-07 at 11:27 +1000, Michael Still wrote:
> > > Additionally, we have consistently asked for non-cores to help cover
> > > the review load. It doesn't have to be a core that notices a problem
> > > with a patch -- anyone can do that. There are many people who do help
> > > out with non-core reviews, and I am thankful for all of them. However,
> > > I keep meeting people who complain about review delays, but who don't
> > > have a history of reviewing themselves. That's confusing and
> > > frustrating to me.
> > I can understand why you're frustrated, but not why you're surprised:
> > the process needs to be different. Right now the statement is that for
> a patch
> > series to be accepted it has to have a positive review from a core plus
> one other,
> > however the "one other" can be a colleague, so it's easy. The problem,
> as far as
> > submitters see it, is getting that Core Reviewer. That's why so much
> > (which contributes to your
> > frustration) goes into it. And why all the complaining which annoys you.
> > To fix the frustration, you need to fix the process: Make the cores
> more of a
> > second level approver rather than a front line reviewer and I predict
> the frenzy
> > to get a core will go down and so will core frustration. Why not
> require a +1
> > from one (or even more than one) independent (for some useful value of
> > independent) reviewer before the cores will even look at it? That way
> the cores
> > know someone already thought the patch was good, so they're no longer
> > pestered to review any old thing and the first job of a submitter
> becomes to find
> > an independent reviewer rather than go bother a core.
> If I take a case that we were very interest in (
> https://review.openstack.org/#/c/129420/) for nested project quota, we
> seemed to need two +2s from core reviewers on the spec.
> There were many +1s but these did not seem to result in an increase in
> attention to get the +2s. Initial submission of the spec was in October but
> we did not get approval till the end of January.
I'll bite. As one of the '+2's on your spec, I don't think this is a fair
characterization of what happened.
* This spec took 36 revisions, but most of those were back to back in the
same day with no feedback. So this actually translates to about 9 or so
reviewed revisions. For a big spec like this I don't think that is too bad
* The first set of feedback came a few days after the first draft was
posted, which isn't too bad.
* The first +1 was on December 11th. So that means from the first +1 to
being merged was December to January, not October to January.
* The 'many +1s' were all from the group proposing the patch, and as
reviewer with +2 power, I generally discount those +1s since they are
inherently fairly biased. Although a lack of +1s from the teammates of the
author is an even worse sign. So I see a lack of +1s from the group as a
* The final revision was posted on December 18th (ignoring the trivial
cleanup/rebase I ran) and this finally landed on January 26th. This is
where I think we could have done better, it shouldn't have taken over a
month to get 2 +2s at this point.
* The fact that the RST didn't render properly until I went through and
fixed it myself was a bad sign:
In short, I think we dropped the ball a little bit on getting the final +2
on this, but by the time this was really ready it was already very late in
> Unfortunately, we were unable to get the code into the right shape after
> the spec approval to make it into Kilo.
> One of the issues for the academic/research sector is that there is a
> significant resource available from project resources but these are time
> limited. Thus, if a blueprint and code commit cannot be completed within
> the window for the project, the project ends and resources to complete are
> no longer available. Naturally, rejections on quality grounds such as code
> issues or lack of test cases is completely reasonable but the latency time
> can extend the time to delivery significantly.
This is the first time I heard of any time window issues or this blueprint,
so I am not sure how you expected us to work within said window. In cases
where there are some time constraints like this, you should just raise
awareness of this early on in the process so we can work around it.
> Luckily, in this case, the people concerned are happy to continue to
> completion (and the foundation is sponsoring the travel for the summit too)
> but this would not always be the case.
> > James
> > _________________________________________________________________
> > _________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> OpenStack-dev-request at 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-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev