Open Stack

On Wed, 2015-02-25 at 21:15 +0000, Ian Cordasco wrote:
> I read it the same was as Doug. I don’t think Jeremy was trying to
> imply your reviews would move through more quickly if you reviewed
> other people’s work. Just that, as with most open source projects,
> there’s always at least 2 distinct groups: people who push code more
> often and people who review code more often. 

this conversation reminded me that the median time to merge new code has
been increasing every quarter in the past year, but dropped for the
first time during last quarter (table and chart on page 23 of Q4
quarterly report [1]). The mean number of iterations (patchsets) per
proposed change has also decreased for the first time in Q4 2014.

The interesting bit of those charts is that overall for OpenStack
projects, it seems that the reviews (comments to patchsets) are arriving
quite quickly but the new patchsets take a lot more to be submitted. 

Too much debating and commenting over each patch? Or are the
authors/owners of the changeset slow to respond with new patches? I
don't have an answer. I'd be happy to look at the data with other
people.

I think more analysis is needed before we can identify and remove the
problem.

/Stef

 [1]
http://git.openstack.org/cgit/openstack-infra/activity-board/plain/reports/2014-q4/pdf/2014-q4_OpenStack_report.pdf
The analysis doesn't count the *-specs repositories, only code and docs.

PS The analysis of the individual projects are in their own pdf
http://git.openstack.org/cgit/openstack-infra/activity-board/tree/reports/2014-q4/pdf/projects