For UCT and David's time, there are 2 issues assigned to us, one of which (I 
believe) is documentation and the other may not still be an issue but needs 
verification.

David is tied up with local Sakai work this week, but should be able to get to 
these next week.

Beyond that, it will depend on whether we are able to move to a 1.4 release for 
June/July (which now seems less likely) or will continue running 1.3 for a 
while (possibly with some merged fixes or backports). David is away effectively 
4 June to 15 June and more or less first two weeks of July.

We might be able to contribute some QA time as well.

Regards
Stephen
 

Stephen Marquard, Acting Director 
Centre for Educational Technology, University of Cape Town
http://www.cet.uct.ac.za
Email/IM/XMPP: [email protected] 
Phone: +27-21-650-5037 Cell: +27-83-500-5290 
 


>>> Tobias Wunden <[email protected]> 5/9/2012 11:44 AM >>> 
Hi all,

> Unfortunately, with the lack of developer resources we face over the
> summer I feel the need to propose that we scrub the release date for
> 1.4.  The release has been stalled for a couple of weeks now, and this
> met with no opposition in the developer meeting this morning.

this was one sad e-mail to receive!

I would like to ask for feedback from the committer's managers, namely Chris, 
RĂ¼diger, Stephen and Vicente on what they think when their developers will be 
able to continue working on closing out the remaining bugs. 

I did a rough estimate and would think that with roughly 3-4 weeks worth of 
work (not taking into account the time to QA) I could probably close out most 
of the bugs, so I wonder why it is not possible for each of us to invest a 
couple of days to get it done, especially given that we committed to getting 
1.4 done within the April/May timeframe. 

Given that 1.4 contains multiple *major* building blocks for a successful 
lecture capture deployment (most notably the ability to upgrade to future 
versions without having to republish what you have pushlished so far as well as 
critical improvements to robustness) I feel like it would certainly be worth 
everybody's time to get this out and start collecting feedback from early 
adopters. Entwine is more than willing to keep contributing major amounts of 
time, but we certainly don't want to be the only ones.

Looking at all the new members on list, on IRC and at the unconferences, there 
seems to be quite a bit of traction and it could be big times for Matterhorn. 
Skipping the releases or delaying them for an unknown period of time is the 
worst thing we could possibly be doing.

> The release date will be changed to 'Ongoing', and a link to an email
> archive of this mail to explain why.  I hope this is just the normal
> summer slump when our committers end up with higher priority local
> issues, but rather than repeatedly slip release dates and annoy our
> adopters I think we need to be realistic and put the release off until
> such time as we have active committers again.

I agree that having the date slip over and over it's better to state that there 
is no defined date yet. One important questions to answer though is:

Will trunk remain closed for the time being? My vote is certainly "yes", since 
if we open trunk again, restarting the release with more features will just be 
more work and a nightmare, because additions will likely be tailored to fit 
existing 1.3 deployments. And even if we decide to skip the current release 
date, that shouldn't mean we don't keep working on the release.

Tobias
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________






###

UNIVERSITY OF CAPE TOWN 

This e-mail is subject to the UCT ICT policies and e-mail disclaimer published 
on our website at http://www.uct.ac.za/about/policies/emaildisclaimer/ or 
obtainable from +27 21 650 9111. This e-mail is intended only for the person(s) 
to whom it is addressed. If the e-mail has reached you in error, please notify 
the author. If you are not the intended recipient of the e-mail you may not 
use, disclose, copy, redirect or print the content. If this e-mail is not 
related to the business of UCT it is sent by the sender in the sender's 
individual capacity.

###
 

_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to