Hi Rüdiger,

I think it is in everyone's interest to upgrade ffmpeg at some point, and at 
the time we discussed your proposal, we didn't want to destabilize the build as 
we were trying to get to the next release. Right now, I don't see any reason 
not to do the upgrade (others may chime in if they think differently) and I 
very much welcome the fact that you were able to get it done!

The failing unit tests are a general problem and are not related to ffmpeg. I 
think all of us are on the same page that there can't be a commit without 
running unit and integration tests. In case that it happens regardless, 
everybody should obliged and free to ping the developer and roll back the 
conflicting changes, so other developers are not blocked in their local work.

Tobias

On 26.08.2011, at 10:57, Ruediger Rolf wrote:

> Hi,
> 
> I'm sorry for the uncomplete commit, I missed to commit of the encoding 
> properties and the properties used by the unit test. Sorry!
> The changes have not been untested and I have checked that ffmpeg version 
> works even with 1.1.x branch if the encoding profiles are updated (I don't 
> intend to backport these changes to 1.1.x, although we are using them with 
> this release too).
> 
> I did a fresh checkout to make sure that I did not miss some of my changes 
> again and build it without errors, but the integration tests fail for me, but 
> not in encoding: http://opencast.jira.com/browse/MH-8090
> 
> I proposed a while ago to upgrade the ffmpeg version for 1.2, and that was 
> refused. But for our current developments (branding and HTML5 video) this is 
> not an optional decision anymore, so I don't feel the need to discuss if we 
> want to update. If the others think that updating ffmpeg is too dangerous our 
> only option would be to continue Osnabrücks further developments in a 
> separate branch.
> 
> Regards
> Rüdiger
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to