[Ffmpeg-devel] Release process/project/effort

[Michael Niedermayer]

Hi

On Fri, Oct 06, 2006 at 03:34:39PM -0400, Dana Hudes wrote:
> I think the very first resource we need is a separate mailing list. 
> ffmpeg-devel is a wonderfully busy place and I think that we need to not 
> add to the volume and also not get buried in patches though lately the 
> former is more the problem.

there are a few problems here
* if the one who does the releases doesnt read ffmpeg-devel he will in
  some sense be unaware of what is going on with the development of ffmpeg
  thats not a good thing 
  and btw, reading ffmpeg-svn/cvslog is a must due to security issues being
  mentioned there and of course any release related commits and possible
  comments about them ending there
* most ffmpeg developers will very likely not subscribe or post to the 
  release list, which means they will be unaware of release related stuff

so my suggestion would be to use ffmpeg-devel but its all your decission

the thing which is my decission is what will happen with the release you
produce, if its good quality it will become the official ffmpeg 0.5.0
or another version number if you can convince a majority of developers, 
personally i dont care about the version number
OTOH if its not good quality (=just a snapshot which is as bug(free) as
average snapshots) then it wont be an official release

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

In the past you could go to a library and read, borrow or copy any book
Today you'd get arrested for mere telling someone where the library is