On 12-01-27 09:01 AM, Olli Salo wrote:
> 
> Hi Tobias,
> 
>> So are you saying that you *do* need an upgrade path to 1.3?
> At this moment, as we have told our pilot users that we're only piloting
> MH and it's not production ready in our case, the answer is actually no:
> there is no need for an upgrade path from 1.2 to 1.3 (in our case, that
> is). But I'd very much want to take MH into production use, and that's
> where the upgrade scripts become very important. You see: our colleagues
> in the different Departments would come to our office with a baseball
> bat if we told them that their videos in the production environment
> would be thrown to trash after each upgrade. :)

To be fair, all versions of Matterhorn thus far store the originals by
default.  If your colleagues did arrive with the aforementioned baseball
bats you could always offer to reprocess the lectures.  Time consuming,
but that was previous upgrade path :)

> I personally hope that immediately after the release of 1.3 we could
> throw our MH 1.2 pilot setup to trash and set it up again, this time
> using the openjdk instead of Sun Java and maybe mysql instead of
> postgresql, if mysql is the db that MH supports best. The idea behind
> this is to make our MH servers more robust than in our 2011 pilot. At
> this phase we would very much want to try any upgrade methods, if
> possible, and also report back possible bugs, if we should find any. I
> mean: if there is a good soul who has the knowledge and time to write
> the upgrade scripts then we'd be extremely interested in giving them a
> try. And if I understood you right, Tobias, this could maybe take place
> say... starting from 1.3?

As QA manager I imagine that this will fall somewhat on my shoulders.
This may not happen for 1.2 -> 1.3, but I don't see any reason why it
shouldn't for 1.3 -> 1.4.

G

Attachment: signature.asc
Description: OpenPGP digital signature

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

Reply via email to