Should it be a release blocker?

Short answer: YES, ABSOLUTELY

Long answer: I cannot think of a serious mature system that does not allow
their users to upgrade versions keeping the data they already had on it.
Matterhorn does NOT. Therefore, I infer that it is either not serious or not
mature. I can not imagine how we can seriously expect any institution to
adopt matterhorn knowing they will have to reprocess their whole collection
if they want to upgrade the system. And this is more important than ANY
feature anyone could want to upgrade for.

Regards,
Rubén

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

> We can't reingest previous media into a new system as discussed in the
> team meeting (MH-7769).  Nejcs is looking at a work around but in the
> meantime I would like to pose the question as to whether this should be
> an RB.  In short I'm asking whether it is the expectation of a minor
> version that media packages from another system could be ingested.
>
> Comments welcome...
>
> 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