FFmpeg Release Plan: Difference between revisions

From MultimediaWiki
Jump to navigation Jump to search
(we will use the FOSDEM motto for 0.6)
(Add Theora work to pending features list; checksumming.)
Line 13: Line 13:
* HE AAC v1
* HE AAC v1
* LATM demuxing support
* LATM demuxing support
* Theora speedup work


==Release Criteria==
==Release Criteria==
Line 25: Line 26:
==Rationale for releases==
==Rationale for releases==
* Provide endorsed snapshots for external software developers to develop against
* Provide endorsed snapshots for external software developers to develop against
* Avoid sitation where external software developers using SVN head when head has transient limitations.
* 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.
* Discourage external software developers using ancient snapshots that we don't support.


Line 36: Line 37:
* Create tarball
* Create tarball
* Checksums?
* Checksums?
** md5sum ffmpeg-0.6.tar.bz2 > ffmpeg-0.6.tar.bz2.md5
** sha1sum ffmpeg-0.6.tar.bz2 > ffmpeg-0.6.tar.bz2.sha
* Upload to ffmpeg.org
* Upload to ffmpeg.org
* Update website
* Update website

Revision as of 06:51, 2 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

  • HE AAC v1
  • 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)
And NetBSD status? https://roundup.ffmpeg.org/roundup/ffmpeg/issue886
  • 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.
  • Replace version.sh by something that hardcodes 0.6.
  • svn export svn://svn.ffmpeg.org/ffmpeg/tags/0.6/ ffmpeg-0.6
  • tar -cvjf ffmpeg-0.6.tar.bz2 ffmpeg-0.6
  • Get source code
  • Create tarball
  • Checksums?
    • md5sum ffmpeg-0.6.tar.bz2 > ffmpeg-0.6.tar.bz2.md5
    • sha1sum ffmpeg-0.6.tar.bz2 > ffmpeg-0.6.tar.bz2.sha
  • 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)