Tue Jun 28 20:59:38 CEST 2005
On Tuesday 28 June 2005 20:28, Diego Biurrun wrote:
> On Mon, Jun 27, 2005 at 09:00:44PM +0200, Michael Niedermayer wrote:
> > On Monday 27 June 2005 20:35, Robert Lippmann wrote:
> > > hi all,
> > >
> > > just my $.02, but judging from the number/type of cvs commits, maybe a
> > > release is in order?
> > >
> > > this can allow distro maintainers/dependent projects to have a
> > > relatively stable, fixed point to link against.
> > does anyone of the ffmpeg developers want to take care of that release,
> > if no then well no release ...
> What exactly does an FFmpeg release consist of? "Just" a CVS snapshot
> that is tarred up and announced? Or a series of tests and a
> stabilization period and whatnot?
well, heres a suggested list (comments welcome)
1. announce it 1 week ahead on the mailinglist so that whoever wants to see
something fixed before the release can fix it
2. update Changelog / INSTALL / README files if needed
3. update version information in various files
4. if there are any big problems here or later delay or return to a previous
5. take a cvs checkout
6. make a tarball
7. check compilation (follow INSTALL) & regression tests & make install
8. check against some actual files, not many just 1 or 2 for each container
type (if something doesnt work try the previous release and if it got worse
judge if its important enough to fix before the release)
9. upload the tarball as "release candidate" and announce it on the
10. if no big issues here then make the real announcement & upload
More information about the ffmpeg-devel