Hello,

We (actually, Rubén González and Héctor Canto) are working on it. It's a
rather annoying bug but the fix is simple enough. Next week we'll release a
maintenance version that can ingest to pre- and post- 1.4 Matterhorns.

I would like to take the opportunity to say that I find it a very serious
issue that we don't keep backwards compatibility and we are constantly
breaking the upgrade path between versions. And not just code
compatibility, but data compatibility, as it is the case here. Any normal
platform makes both is APIs and data structures interoperable between
consecutive releases, and while I agree that the namespace changes were
necessary, I also think that this shouldn't prevent the users from using
their old mediapackages. What if I want to use a 1.3 CA with a 1.4 core? (a
perfectly valid scenario if one wants to have confidence monitoring -broken
in 1.4-). The fact that the fix is so simple makes it even more serious
--it's not that making it backward-compatible is technologically difficult;
it's that we are lazy, or we just don't care.

Best regards

Rubén Pérez
TELTEK Video Research
www.teltek.es



2012/11/6 Greg Logan <[email protected]>

> On 12-11-06 08:42 AM, James S Perrin wrote:
> > It probably went over my head at the time, still so much too learn.
> > Gives us a starting point even of we just fudge Galicaster for now. Is
> > there an issue for this I can't find one?
>
> Nope, not yet.  I'll bring it up at the dev meeting today and see if we
> can get a consensus.
>
> G
>
> > Thanks,
> > James
> >
> >
>
>
>
> _______________________________________________
> 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