On Tue, Nov 17, 2015, at 06:01 PM, Rob Vesse wrote: > On 17/11/2015 16:50, "Steve Loughran" <ste...@hortonworks.com> wrote: > > >If someone were to have some metrics of projects, the state of > >patches/pull requests would be a key issue. > > https://github.com/rvesse/gh-pr-stats > > Given a GitHub project generates statistics about the state of the Pull > Requests in the project e.g. > > ./pr-stats apache hadoop > > Fairly basic tool but should give you enough to gauge where things are
One of the things that this conversation seems to miss, to me, is defining what "C" is. In some sense, C is simply the act of publishing a change. The change MUST be published before the review, otherwise review is, obviously, impossible (how can you review something you cannot see?) What's important, as I think Greg was saying earlier, is *how we relate to each other*. Do I need to ask for PERMISSION to finally push a change through, or do my colleagues trust me to do the right thing, knowing that I'll listen to their feedback, whether the review mechanism is a commit mailing list, a JIRA ticket or a pull request. Please define what you mean by CTR or RTC before diving into further discussions about their relative merit. Otherwise we'll get locked into yet another ongoing discussion that leads nowhere! Upayavira --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
