> I will be committing MH-7882 which will enhance the user tracking > features. We will be able to reconstruct the users actions within the > UI from start to finish in each viewing session.
Sounds nice. Is there a documentation how it works? Just askin because for example germany has very strict laws on how to track user/what data can be stored to do this. So maybe we need a comparison between both. > > I'm also wondering if we should try and keep to the existing release > schedule, especially for institutions who want a lot of time to test the > release before putting it into production. One such university is ours: > We will be running with 1.2 for the September to December term, but we > would like to run with 1.3 for the spring term. I'm told that branch > being cut around the end of September would be good... Just from my poin of view it is a question of manpower and disciplin. As an observer of the E-Mail list and Jira I would propose that we have a lack of manpower to do releases with that short release cycles. I can remeber comments on list on this topic. Just increase the manpower can be diffcult for an Open Source project so maybe we need a reastic plan to see if we can cut a first release in about 6 weeks and look back on our past releases to estimate the time we need for QA and bugfixing. Regards Nils > > On 2011-08-15 6:21 PM, Adam Hochman wrote: >> Hi all, >> We had originally discussed releasing 1.3 at the end of September, but I >> think that time line is too aggressive. It would be helpful to clarify >> what folks are working on, the scope of their projects, and when they >> they'll be ready to get their code production ready. We had originally >> started a list of Release 1.3 efforts on the Matterhorn Road Map page, >> but this page is fairly basic and potentially out of date. >> http://opencast.jira.com/wiki/display/MH/Matterhorn+Road+Map >> >> I was going to map out what I thought was in scope, and what >> institutions and resources were involved and their project's latest >> status, but before I take on that difficult task I'd like to give the >> primary sources the immediate opportunity to inform the list about their >> efforts. >> >> That way we can identify and align resources around QA and Release and >> assess whether our current time line makes sense. This will help us >> determine whether projects in trunk will need to be branched, and >> potentially identify the need for more dev resources to ensure >> strategically important projects happen within our given time frame. >> >> Thanks in advance for sharing. >> >> Adam >> Matterhorn Community Liaison >> _______________________________________________ >> Matterhorn mailing list >> [email protected] >> http://lists.opencastproject.org/mailman/listinfo/matterhorn >> >> >> To unsubscribe please email >> [email protected] >> _______________________________________________ >> > > > _______________________________________________ > Matterhorn mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > To unsubscribe please email > [email protected] > _______________________________________________ _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
