FFmpeg Release Plan: Difference between revisions

From MultimediaWiki
Jump to navigation Jump to search
(→‎Release Process: Diego's release process)
Line 19: Line 19:


== Release Process==
== Release Process==
* Do NOT create a branch in SVN
* Create a branch in Subversion.
** Okay, then can we at least create a tag/label? --[[User:Multimedia Mike|Multimedia Mike]] 12:57, 28 January 2009 (EST)
* Replace version.sh by something that hardcodes 0.5.
* svn export svn://svn.ffmpeg.org/ffmpeg/tags/0.5/ ffmpeg-0.5
* tar -cvjf ffmpeg-0.5.tar.bz2 ffmpeg-0.5
* Get source code
* Get source code
* Create tarball
* Create tarball

Revision as of 00:25, 30 January 2009

Ideas and suggestions concerning FFmpeg software releases.

Things that need doing

  • Fix DV regression tests on PPC
  • Approximately 95% test coverage in FATE.
  • Add an API/ABI changelog

Release Criteria

  • make test passes.
  • FATE test coverage passes for all platforms of interest.
  • All 'important' bugs reported in roundup fixed/closed.
  • 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 sitation 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.5.
  • svn export svn://svn.ffmpeg.org/ffmpeg/tags/0.5/ ffmpeg-0.5
  • tar -cvjf ffmpeg-0.5.tar.bz2 ffmpeg-0.5
  • Get source code
  • Create tarball
  • Checksums?
  • 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)