[openstack-dev] *How* to keep up with code reviews

Mark McLoughlin markmc at redhat.com
Thu May 30 09:44:02 UTC 2013


Hey

On Thu, 2013-05-30 at 03:23 -0500, Dolph Mathews wrote:
> Following Russell Bryant's quest to analyze our review-related performance
> [1], I started wondering how we can go about improving those numbers.
> Specifically, how can we reduce the average wait time for feedback on a
> change?
> 
> The simple answer: provide a better way to put reviewers in front of
> changes worth reviewing. So, how about:
> 
>   $ next-review
>   https://review.openstack.org/29429 Make nova.virt.fake.FakeDriver useable
> in integration testing
> 
> This change was selected from all my watched projects in gerrit and
> next-review automatically opens the review in my browser.
> 
> To get started:
> 
>   $ pip install next-review
> 
> The logic for selecting an ideal review has a lot room for improvement
> (e.g. based on bug priority, blueprint priority, pending feature freezes,
> etc).

Have you seen reviewday?

  http://status.openstack.org/reviews/#keystone

Cheers,
Mark.




More information about the OpenStack-dev mailing list