Difference between revisions of "ReleaseProcess"

From GNU MediaGoblin Wiki
Jump to navigation Jump to search
Line 11: Line 11:
 
# Do a {{Cmd|git clean -fdx}} to wipe all non-repository files out (THIS DELETES EVERYTHING), go through hacking howto to reinstall.
 
# Do a {{Cmd|git clean -fdx}} to wipe all non-repository files out (THIS DELETES EVERYTHING), go through hacking howto to reinstall.
 
# Run the unit tests: {{Cmd|./runtests.sh}} If any tests fail, proceed no further!
 
# Run the unit tests: {{Cmd|./runtests.sh}} If any tests fail, proceed no further!
# Update version numbers in these files:
+
# Update version numbers in <tt>mediaboglin/_version.py</tt>
#* mediaboglin/_version.py
 
#* docs/source/conf.py
 
 
# Tag: {{Cmd|git tag -a vX.Y.Z}}
 
# Tag: {{Cmd|git tag -a vX.Y.Z}}
 
# Build the tarfile. {{Cmd|./devtools/maketarball.sh -r vX.Y.Z}}
 
# Build the tarfile. {{Cmd|./devtools/maketarball.sh -r vX.Y.Z}}

Revision as of 17:04, 22 August 2012

Steps to release

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

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 ./devtools/update_translations.sh and make sure you have the latest translations.
  4. Do a ./devtools/maketarball.sh -dr HEAD to make sure building the docs and tarball works. If any errors, proceed no further!
  5. Do a git clean -fdx to wipe all non-repository files out (THIS DELETES EVERYTHING), go through hacking howto to reinstall.
  6. Run the unit tests: ./runtests.sh If any tests fail, proceed no further!
  7. Update version numbers in mediaboglin/_version.py
  8. Tag: git tag -a vX.Y.Z
  9. Build the tarfile. ./devtools/maketarball.sh -r vX.Y.Z
  10. Push the tarball to the web-site: add tarball to site/static/download/ directory in mediagoblin-website repository and then push the site live
  11. Update on PYPI - FIXME - need to set this up


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)


Places we Update

    • 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.


Press Contacts

    • write to Zonker
    • LinuxJournal
    • LWN
    • OpenSource.com
    • see if the FSF will blog or announce


Post release process

  1. change version number to the next one + -dev in files listed above
  2. add new milestone to Trac