[FFmpeg-devel] releases and stuff

Daniel Serpell dserpell
Wed Feb 11 19:27:39 CET 2009


Hi!

El Tue, Feb 10, 2009 at 06:16:52PM +0100, Diego Biurrun escribio:
> On Tue, Feb 10, 2009 at 06:14:54PM +0100, Vitor Sessak wrote:
> > Benjamin Larsson wrote:
> > > Diego Biurrun wrote:
> > >> On Tue, Feb 10, 2009 at 03:56:47PM +0100, Diego Biurrun wrote:
> > >>   
> > >>> On Tue, Feb 10, 2009 at 01:17:07PM +0100, Dominik 'Rathann' Mierzejewski wrote:
> > >>>     
> > >>>> On Tuesday, 10 February 2009 at 00:32, Carl Eugen Hoyos wrote:
> > >>>>       
> > >>>>> Roman V. Shaposhnik <rvs <at> sun.com> writes:
> > >>>>>
> > >>>>>> -4435d87463cd6c5407bd88cca241ca56 *./tests/data/a-wmav1.asf
> > >>>>>> +6f7f3116b801ea641ce14f827de05cce *./tests/data/a-wmav1.asf
> > >>>>>>           
> > >>>>> I remember posting an incredibly beautiful patch to fix it, fortunately I can't
> > >>>>> find it now;-)
> > >>>>>         
> > >>>> This?
> > >>>>
> > > 
> > > I strongly object. Doing regressions tests on float code is bound to 
> > > trigger these things.
> > 
> > I don't like this either. It'll come back over and over again every time 
> > someone ports ffmpeg to a new arch/compiler/gcc major ver. I think that 
> > the only clean way to do it is to use some Makefile/configure machinery 
> > to run this test only in the systems it is supposed to work.
> 
> I'm currently tempted to disable the test in the release version.

I think that it's better to simply document it in the release notes.

   Daniel.





More information about the ffmpeg-devel mailing list