Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 = Release checklist = | |
|
wtc
2015/01/28 17:50:47
This file isn't in the source tarball opus-1.1.1-b
| |
| 2 | |
| 3 == Source release == | |
| 4 | |
| 5 - Check for uncommitted changes to master. | |
| 6 - Update OPUS_LT_* API versioning in configure.ac. | |
| 7 - Update the version in version.mk | |
| 8 - Tag the release commit with 'git tag -s vN.M'. | |
| 9 - Include release notes in the tag annotation. | |
| 10 - Verify 'make distcheck' produces a tarball with | |
| 11 the desired name. | |
| 12 - Push tag to public repo. | |
| 13 - Upload source package 'opus-${version}.tar.gz' | |
| 14 - Add to https://svn.xiph.org/releases/opus/ | |
| 15 - Update checksum files | |
| 16 - svn commit | |
| 17 - Copy to ftp.mozilla.org:/pub/mozilla.org/opus/ | |
| 18 and verify file permissions. | |
| 19 - Upload source packge 'opus-${version}.tar.gz' | |
| 20 to website and verify file permissions. | |
| 21 - Add release notes to https://svn.xiph.org/websites/opus-codec.org/ | |
| 22 - Update links and checksums on the downloads page. | |
| 23 - Add a copy of the documentation to <http://www.opus-codec.org/docs/> | |
| 24 and update the links. | |
| 25 | |
| 26 Releases are commited to https://svn.xiph.org/releases/opus/ | |
| 27 which propagates to downloads.xiph.org, and copied manually | |
| 28 to https://ftp.mozilla.org/pub/mozilla.org/opus/ | |
| 29 | |
| 30 Website updates are committed to https://svn.xiph.org/websites/opus-codec.org/ | |
| 31 which propagates to http://opus-codec.org/ | |
| 32 | |
| 33 == Binary release == | |
| 34 | |
| 35 We usually build opus-tools binaries for MacOS and Windows. | |
| 36 | |
| 37 Binary releases are copied manually to | |
| 38 ftp.mozilla.org:/pub/mozilla.org/opus/win32/ | |
| 39 | |
| 40 == Website updates == | |
| 41 | |
| 42 For major releases, recreate the files on http://opus-codec.org/examples/ | |
| 43 with the next encoder. | |
| OLD | NEW |