Just my two bits, I think git would slow down development more right now than it would add clarity to the release process. In release 1.2 it was unclear where people were to commit changes. I don't know why, since we used the exact same (or at least I did) process as 1.1. I think we should focus on clarifying this process right now and not changing the underlying tools; I'm not sure that git fixes things completely, and I'm worried that it would just slow us down instead.
So, my preference is to just encourage developers to commit their branch fixes to the branch, and let the release manager assign a merge task after each rc. Note: the release manager assigns the task, doesn't necessarily do the merge, though this would be great if they could. Also, we have minimal testing resources. This means devs have to help test, or we get an untested product. It sucks, but that's how it is. For 1.2 we're really indebted to the work of Judy & Micah in verifying so many of the issues (others as well, of course, but these two stick out prominently in my mind). But they aren't the sole people who can QA. Until the OC board can help us get the QA resources we need, we should all pitch in. And, it could have been because it was summer, but that last release didn't seem like it was test as broadly (e.g. there was just a small group of us testing it). After the first branch was cut there was 116 commits to the 1.2.x branch and 90 to trunk. That's much higher than I would have expected to trunk while we were taking on a release; I would have felt more comfortable with a more diverse set of eyes testing things. Diversity is extremely good in testing the releases! Chris -- Christopher Brooks, BSc, MSc ARIES Laboratory, University of Saskatchewan Web: http://www.cs.usask.ca/~cab938 Phone: 1.306.966.1442 Mail: Advanced Research in Intelligent Educational Systems Laboratory Department of Computer Science University of Saskatchewan 176 Thorvaldson Building 110 Science Place Saskatoon, SK S7N 5C9 _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
