Difference between revisions of "FFmpeg Release Plan"

From MultimediaWiki
Jump to navigation Jump to search
(release process details)
(HE-AAC v1 has been merged)
Line 11: Line 11:
 
Pending features that would be nice to have in 0.6
 
Pending features that would be nice to have in 0.6
  
* HE AAC v1
 
 
* LATM demuxing support
 
* LATM demuxing support
 
* Theora speedup work
 
* Theora speedup work

Revision as of 21:42, 7 March 2010

Ideas and suggestions concerning FFmpeg software releases.

Things that need doing

  • Fix SVQ3 regression test?
  • Approximately 95% test coverage in FATE.
  • AAC Conformance sweep
  • Make sure API/ABI changelog is up-to-date

Release 0.6 "Works with HTML5"

Pending features that would be nice to have in 0.6

  • LATM demuxing support
  • Theora speedup work

Release Criteria

  • make test passes.
  • FATE test coverage passes for all platforms of interest.
  • All 'important' bugs reported in roundup fixed/closed.
Except 46, 127 and possibly 192 and 452 --Ce 05:36, 3 February 2010 (EST)
  • No half-implemented functionality that may break existing user apps.
  • Endurance/memleak testing on film-length files.

Rationale for releases

  • Provide endorsed snapshots for external software developers to develop against
  • Avoid situation where external software developers using SVN head when head has transient limitations.
  • Discourage external software developers using ancient snapshots that we don't support.

Release Process

  • Create a branch in Subversion.
  • Add VERSION file that hardcodes 0.6.
  • Create release tarballs (repeat the process for gzip compression)
    • svn export svn://svn.ffmpeg.org/ffmpeg/tags/0.6/ ffmpeg-0.6
    • tar -cjf ffmpeg-0.6.tar.bz2 ffmpeg-0.6
    • md5sum ffmpeg-0.6.tar.bz2 > ffmpeg-0.6.tar.bz2.md5
    • sha1sum ffmpeg-0.6.tar.bz2 > ffmpeg-0.6.tar.bz2.sha
    • signatures from the release managers (concatenate all signatures into one file)
      • gpg --armor --detach-sign ffmpeg-0.6.tar.bz2
  • Upload to ffmpeg.org
  • Update website
  • Who needs to be notified?
    • Major dependent projects, major distribution package maintainers --Rathann 09:43, 29 January 2009 (EST)