ReleaseProcess

From GNU MediaGoblin Wiki
Revision as of 12:21, 12 December 2011 by Willkg (talk | contribs) (updated release process; fleshed some things out; moved some things around)
Jump to navigation Jump to search

Release Process

Steps to release

Here's the list of steps to do a release.

  1. Verify with others on IRC that we're good to go.
  2. Do a git fetch and make sure you have the latest code.
  3. Do a tx pull -a and make sure you have the latest translations.
  4. Run the unit tests: ./runtests.sh If any tests fail, proceed no further!
  5. Update version numbers in these files:
    • mediaboglin/_version.py
    • docs/source/conf.py
  6. Tag: git tag -a vX.Y.Z
  7. Build the tarfile. ./maketarball.sh -r vX.Y.Z
  8. Push the tarball to the web-site: add tarball to
    site/static/download/
    directory in mediagoblin-website repository and then push the site live
  9. Update on PYPI - FIXME - need to set this up
  10. Update sites:
    • on identi.ca
    • on diaspora
    • on Facebook (Deb)
    • on Twitter
    • our mailing list, encouraging people to fave, like, repost, etc.
    • reddit
    • digg
    • the GNU mailing list, aka info-gnu@gnu.org "plain text is greatly preferred" omit screenshots or replace with links.
  11. For 1.0 and other major versions after that one
    • write to Zonker
    • LinuxJournal
    • LWN
    • see if the FSF will blog or announce

Post release process

  1. change version number to the next one + -dev in files listed above