[Ffmpeg-devel] Re: [Ffmpeg-devel-old] Re: Using ffmpeg libs in an OSS project is a nightmare

Burkhard Plaum plaum
Tue Aug 9 02:01:38 CEST 2005

Kenneth Lavrsen <kenneth <at> lavrsen.dk> writes:

> I am for sure interested. And I do not even see the reason for an 
> additional CVS.

I just thought it could be handy sometimes to have a reference codebase 
available for everyone to test. In principle, this could also be a tar.gz
on a webserver, but I personally would prefer CVS.

> We can just agree - 3 times per year - 

Doesn't need to be that strict IMHO. We can also try to synchronize it
to the release cycles of our projects. But the more projects participate,
the harder it's gonna be, so 3 times a year might be better then.
> We choose a release candidate - test it - and if it works for all of us - 
> we release.
> If not - we try another one.

I would try to report/fix them for the upstream ffmpeg also.
I really think, that the ffmpeg people can have an advantage from that:
Fewer bugreports from years old versions and regular testing phases from 
application developers.

> That will be very simple and I will be happy to participate in that with 
> Motion.

Gmerlin and libquicktime would also join :)

> I am sure we can arrange with the major packagers that they follow up with 
> their RPMs and debs.

That would, for sure, help.


More information about the ffmpeg-devel mailing list