[openstack-dev] Code review study
sam.harwell at RACKSPACE.COM
Thu Aug 15 19:22:04 UTC 2013
I like to take a different approach. If my commit message is going to take more than a couple lines for people to understand the decisions I made, I go and make an issue in the issue tracker before committing locally and then reference that issue in the commit message. This helps in a few ways:
1. If I find a technical or grammatical error in the commit message, it can be corrected.
2. Developers can provide feedback on the subject matter independently of the implementation, as well as feedback on the implementation itself.
3. I like the ability to include formatting and hyperlinks in my documentation of the commit.
From: Christopher Yeoh [mailto:cbkyeoh at gmail.com]
Sent: Thursday, August 15, 2013 7:12 AM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] Code review study
On Thu, Aug 15, 2013 at 11:42 AM, Robert Collins <robertc at robertcollins.net<mailto:robertc at robertcollins.net>> wrote:
This may interest data-driven types here.
Note specifically the citation of 200-400 lines as the knee of the review effectiveness curve: that's lower than I thought - I thought 200 was clearly fine - but no.
Very interesting article. One other point which I think is pretty relevant is point 4 about getting authors to annotate the code better (and for those who haven't read it, they don't mean comments in the code but separately) because it results in the authors picking up more bugs before they even submit the code.
So I wonder if its worth asking people to write more detailed commit logs which include some reasoning about why some of the more complex changes were done in a certain way and not just what is implemented or fixed. As it is many of the commit messages are often very succinct so I think it would help on the review efficiency side too.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev