From GNU MediaGoblin Wiki
Revision as of 10:34, 13 December 2011 by Eximious (Talk | contribs)

Jump to: navigation, search

Release Process

Steps to release

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

  1. Technical
  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: ./ If any tests fail, proceed no further!
  5. Update version numbers in these files:
    • mediaboglin/
    • docs/source/
  6. Tag: git tag -a vX.Y.Z
  7. Build the tarfile. ./ -r vX.Y.Z
  8. Push the tarball to the web-site: add tarball to
    directory in mediagoblin-website repository and then push the site live
  9. Update on PYPI - FIXME - need to set this up
  1. Promotional
  1. Blog post
    • Chris sends Deb technical highlights
    • Deb drafts post
    • Chris adds screenshots/links
    • We send the post to press contacts
    • Two days later we publish everywhere (see below)
  1. Update sites:
    • on
    • on diaspora
    • on Facebook (Deb)
    • on Twitter
    • our mailing list, encouraging people to fave, like, repost, etc.
    • reddit
    • digg
    • the GNU mailing list, aka "plain text is greatly preferred" omit screenshots or replace with links.
  1. Press Contacts
    • 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
Personal tools