On 09.05.2012 11:44, Tobias Wunden wrote:
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.
current status Osnabrück:
- Markus Moormann is currently working on fixing bugs. He may have even
some more free cycles for bugfixing, I talk to him about this.
- Denis, Benjamin and Waldemar are working on a contrib tool for which
we have a hard deadline in 2 weeks (4 weeks with testing). So they don't
have too much time that they can spend on bug fixing. But they are at
least looking for (release) blockers.
- Martin Abel is not yet a committer but if someone finds bugs in the
annotation feature he will fix them asap.
- I'm kind of part time vacation currently and I spent the time that I'm
working on our production system and improvements there and
administrative Matterhorn stuff (i.e. the harvard conference, a webinar)
Regards
Rüdiger
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]
_______________________________________________
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
