Hi Tobias,

> 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. 

Adam and I are the only U of S Matterhorn folks, with of course Greg
being colocated but self-managed.  I'm on local issues for the
remainder of the summer, minus a bit of time here and there.  Adam has
dropped everything to focus on the issue that UCB has surfaced.  This
likely affects 1.4 as well, but I am doubtful that he will have a
chance to look at 1.4 specific issues until late May as the issue is
turning out to be particularly painful and focusing on it means we
have dropped some other local priorities that we need to pick up too.

So if anyone has capacity to take up his tasks for 1.4 (Rubencino?
Waldemar?) I'd welcome it.

> 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.

I agree.  The problem with the quicksand we are in here is that if we
choose 1.3 locally it means we need to backport our features from 1.4
into 1.3.  This means more of Adam's time needs to be burned doing this
instead of 1.4 QA work.

Regards,

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]
_______________________________________________

Reply via email to