Hi Chris,

This feature is not in the trunk yet, since it's not completed (well, it's
nearly completed, i'll just have to run integration tests to see what is
broken) and there didn't seem much point in commiting code that would just
break everything and would not work. So currently, Scheduler Service is
still the same as it has been.

Nejc

2011/5/12 Christopher Brooks <[email protected]>

> Hi,
>
> Mostly aimed at Tobias and Nejc, but others please chime in.  I'm a bit
> concerned that the dublin core catalog changes that were mentioned in
> standup today might have far reaching effects on the 1.2 release, and
> am somewhat regretting that we didn't cut a branch for 1.2 already.
>
> My understanding is that if I cut the branch now this feature is only
> half done but in trunk already, so we couldn't reasonably start a QA
> cycle.  Can I get a quick response from people involved?
>
> In particular, I see four RBs on this issue now, most assigned to
> micah, 7401, 7667, 7668, and one to nejc, 5998.  Should we cut a branch
> before this feature went in, or is this an issue that can be closed off
> quite rapidly (within the next day and a half, so I can cut a 1.2
> branch for QA on the weekend?
>
> 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]
> _______________________________________________
>
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to