Hello Greg and all,
the idea of postponing MH 1.4 sounds good. As an adopter instition we - at least at the Univ of Helsinki - value a robust release way more than a "shaky" one so postponing MH 1.4 really sounds wise. Also, your direct speech regarding the lack of QA etc is appreciated as it helps us adopters plan our Fall deployments not based on MH 1.4 wishes but the already released MH 1.3 which is available.
There is one wish, however, which I'd like to share to you. We've seen svn tags used in http://opencast.jira.com/svn/MH/tags but what I haven't yet found out is the way to find the post-release updates. To adopters like us post release patches are a very important thing so I'd like to propose 1.3.1, 1.3.2 etc svn cuts. I mean minor bug fixes, not new features. With these 1.3.1 etc tags we could fix the small but annoying problems we have in our current installations without needing to wait for half a year or so.
To me personally "less has always been more". By this I want to say that I regard MH a superb system already as what it is now. I personally don't wish for bells and whistles as they usually break what's been done. Instead, small bug fix releases would be awesome. Trunk is of course nice to have, but for a cautious person like me, trunk doesn't seem like the best alternative. ;)
Yours, Olli On 14.5.2012 23:22, Greg Logan wrote:
Hello adopters, and committers, Last week I put a proposal on the Matterhorn development which met with no opposition, and has therefore been adopted. This proposal was to delay the release of Mattehorn 1.4 for the immediate future. At present we are faced with a lack of development time and resources, as well as a nearly complete lack of QA testing. Please keep in mind that this is just a delay! 1.4 will be released at some point, but not in the immediate future like we had hoped. I would like to especially thank the following for their extensive (10+ commits) contributions between the end of 1.3's release cycle and now: Tobian Wunden Markus Moorman Christoph Driessen Adam McKenzie Denis Meyer Note that lots of these folks are also senior committers, and may be committing work from other developers who do not have commit rights yet. I am sure this will be unpopular, but I felt it better than repeatedly slipping release dates and our committers agreed. If you plan to deploy Matterhorn in the near future (eg: September) then I would encourage you to test with 1.3.x. 1.3.0 has a bug in it right now that was fixed in 1.3.x, a proposal for 1.3.1 with minimal bug fixes is being discussed at the developers meeting tomorrow. At present, because of our velocity, I will be replacing the release date on http://opencast.jira.com/wiki/display/MH/Release+1.4 with a target of "Ongoing". We will continue working on this release to the best of our abilities, and aim to have it out sometime in the fall. If your organization has been on the fence and thinking about contributing, now would be an excellent time to start. I am sure there will be much discussion of this at the Unconference, but we have a welcoming community that's looking for new blood even if you can't make it. Feel free to send an email to our email lists, or hop on to IRC. There are usually several developers online who can offer if not real-time, then fast answers to any questions you might have. Release Manager (1.3, 1.4), QA Manager Greg Logan _______________________________________________ Community mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/community To unsubscribe please email [email protected] _______________________________________________
-- Olli Salo Tietotekniikkakeskus Helsingin yliopisto Tel: +358 9 191 21782 Gsm: +358 50 407 5509 Email: [email protected] _______________________________________________ Community mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/community To unsubscribe please email [email protected] _______________________________________________
