FFmpeg Release Plan: Difference between revisions
Jump to navigation
Jump to search
(My opinion) |
No edit summary |
||
Line 20: | Line 20: | ||
== Release Process== | == Release Process== | ||
* Do NOT create a branch in SVN | * Do NOT create a branch in SVN | ||
** Okay, then can we at least create a tag/label? --[[User:Multimedia Mike|Multimedia Mike]] 12:57, 28 January 2009 (EST) | |||
* Get source code | * Get source code | ||
* Create tarball | * Create tarball |
Revision as of 10:57, 28 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
- Do NOT create a branch in SVN
- Okay, then can we at least create a tag/label? --Multimedia Mike 12:57, 28 January 2009 (EST)
- Get source code
- Create tarball
- Checksums?
- Upload to ffmpeg.org
- Update website
- Who needs to be notified?