Hi, Being based in Sydney, I tend to get a lot of list traffic in one big lump when I wake up. Looking at cloudstack-commits today, there are 139 messages - most of which are a result of git branch merges. This has been the situation a few times before, but this is the largest I recall seeing.
There isn't anything necessarily wrong with that, but it has me thinking about the effectiveness of watching that list to provide oversight on the code being committed. I'm asking this out of interest as a mentor in how the podling deals with internal code review, and also to understand how the ASF can best provide git infrastructure as a relatively new service. I'm not actively developing the project, so I wanted to hear how others who are find working with it. The VPC branch is the obvious example at the moment. It has been active since June 15, and has this breakdown of commits: - 232 unique commits - 14 merge commits - 259 commits merged from master So this seems like a good period of time and work to review. Do the other developers here feel they adequately understand what is happening on a feature branch such as this, both in terms of the overall plan for the branch, and the review of the specific commits? Is the commits list remaining an effective tool to keep track of this information? Regards, Brett -- Brett Porter [email protected] http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter
