[FFmpeg-devel] FOMS 2009 FFmpeg outbrief

[Robert Swain]

2009/1/26 Benjamin Larsson <banan at ludd.ltu.se>:
> M?ns Rullg?rd wrote:
>> "Ronald S. Bultje" <rsbultje at gmail.com> writes:
>>> On Mon, Jan 26, 2009 at 10:52 AM, M?ns Rullg?rd <mans at mansr.com> wrote:
>>>> "Ronald S. Bultje" <rsbultje at gmail.com> writes:
>>>>> On Mon, Jan 26, 2009 at 10:31 AM, Diego Biurrun <diego at biurrun.de> wrote:
>>>>>> On Thu, Jan 22, 2009 at 03:06:51PM +0100, Diego Biurrun wrote:
>>>>>>> What is that method?  A quick search on Google revealed nothing.
>>>>>>>
>>>>>> Can anybody shine a light on this?
>>>>>>
>>>>> It is a blind way of releasing weekly or monthly snapshots of the
>>>>> current trunk with essentially no guaranteed QA&co. The idea is to get
>>>>> it out so people use it.
>>>>>
>>>> We have a public svn repository, and we put daily snapshots on the web
>>>> server.  Isn't that enough?
>>>>
>>> It addresses the complaint that there's no releases.
>>
>> So going from daily snapshots to weekly would make these people shut
>> up?
>
> What I thought of for releases is to release 4 times a year. And around
> the time for release we just ensure that all the regressions tests pass
> on all supported platforms. And the releases wouldn't get any more Q/A
> then what is provided by all testcases from FATE and from make test.
> That shouldn't take to much developer time, when it is almost about time
> for a release just pick a svn version that is ok and make a package of it.

This would at least provide an equal footing for external software
developers to develop against and they wouldn't use ancient snapshots
that we don't support. I'm not saying we need to provide masses of
support (backporting all bug fixes to some branch might not be
necessary for example) for the releases, but at least people could
report bugs against a non-ancient version of FFmpeg.

> And regarding the roadmap, it would be nice to have something describing
> what features that are in progress or planned. But maybe not something
> that says exactly what is going to be included in the next release.

A roadmap could rather be linked to version bumps.

Regards,
Rob