Hi all, on the behalf of today's developers meeting, I would like to #propose the following for the release timeline and process of 1.4:
During the long period of time where we were working hard to get 1.3 out, a number of features have been developed in (local) branches that are waiing to be merged to trunk. Now that the release is about to be cut and trunk will be open to non-release-related commits again, we propose the following: 1) Starting on the day of the release of 1.3 (as announced by Greg Logan), trunk will be open for 14 calendar days where committers should merge features and improvements from their development branches. 2) Only features that are known to be working in the development branch may be merged 3) Only features that have resources attached to fix arisign issues may be merged 4) Merged features need to be documented for intensified testing on the release page [1] 5) After 14 calendar days, trunk will be closed to commits and a 1.4 release branch will be cut. 6) We follow the release process that has been outlined for 1.3 already (but was only partly followed): Release candidates will be cut on a bi-weekly basis. Bug fixes are committed to trunk and will be merged by the release manager. Features that have outstanding bugs and are not fixed in between two release candidates will be disabled. With these rules in mind, 1.4 is scheduled to be released prior to May 2012. Tobias [1] http://opencast.jira.com/wiki/display/MH/Release+1.4 (not sure if I picked the right place, I'm happy to take suggestions) _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
