release.txt 1.5 KB

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