From: Loic Dachary <loic@dachary.org>
To: Gregory Farnum <greg@gregs42.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Pull requests : speed up the reviews
Date: Mon, 10 Nov 2014 20:50:55 +0100 [thread overview]
Message-ID: <5461171F.8080401@dachary.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1411101116110.24475@cobra.newdream.net>
[-- Attachment #1: Type: text/plain, Size: 2210 bytes --]
Hi Greg,
> On Mon, 10 Nov 2014, Gregory Farnum wrote:
>> I suppose one way of handling this might be to ask everybody to
>> dedicate a small amount of time to reviews (as you suggest), but to
>> emphasize PR management as much as doing the actual review.
>>
>> 1) If you don't have assigned PRs, look at the unassigned PRs from
>> oldest to newest, and based on the target area assign it to the person
>> you think most appropriate.after doing basic due diligence for issues
>> that you can handle (ie, the feature is something you don't know is
>> inappropriate; skimming the code doesn't make you cry; etc)
>>
>> 2) Manage any reviews assigned to you:
>> 2a) if you're the wrong target, assign it to somebody more appropriate
>> 2b) If you're the right target but are trying to get somebody else
>> acquainted with the code base, maybe assign it to them
>> 2c) assign priorities based on importance and age
>>
>> 3) review PRs in appropriate order at the level they deserve, and then
>> either merge or assign it back to the author
I'll do as you suggest.
>> In particular, this clearly assigns responsibility for a PR to an
>> individual. It lets people offload as necessary, and gives feedback to
>> contributors quickly even if that feedback is just "we appreciate your
>> submission and it is in somebody's queue". It lets people contribute
>> to the PR process even if there isn't something they feel qualified to
>> review directly. And it doesn't emphasize the time spent reviewing so
>> much as the act of moving a PR through the stages of merging. (A
>> 15-minute timebox might sound great, but trust me we have lots of PRs
>> that would never make it into the code base if they were done in
>> 15-minute chunks.)
I see what you mean. However there are few pull requests of that kind in the queue, or am I understimating most of them ?
>> Obviously this is also not a very formal process, but I think maybe if
>> we start approaching things this way it will help move stuff through
>> the pipeline faster. Based on Sage's sudden enthusiasm for assigning
>> PR owners I think he might agree...?
+1
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2014-11-10 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-08 17:32 Pull requests : speed up the reviews Loic Dachary
2014-11-09 12:08 ` Joao Eduardo Luis
2014-11-10 5:10 ` David Zafman
2014-11-10 19:07 ` Gregory Farnum
2014-11-10 19:17 ` Sage Weil
2014-11-10 19:50 ` Loic Dachary [this message]
2014-11-10 21:03 ` Gregory Farnum
2014-11-11 18:07 ` Sage Weil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5461171F.8080401@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@gregs42.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.