Difference between revisions of "ReleaseProcess"

From GNU MediaGoblin Wiki
Jump to navigation Jump to search
(update release process)
(tweak formatting; add "add new milestone")
Line 17: Line 17:
 
# Push the tarball to the web-site: add tarball to <tt>site/static/download/</tt> directory in mediagoblin-website repository and then push the site live
 
# Push the tarball to the web-site: add tarball to <tt>site/static/download/</tt> directory in mediagoblin-website repository and then push the site live
 
# Update on PYPI - '''FIXME - need to set this up'''
 
# Update on PYPI - '''FIXME - need to set this up'''
  +
   
 
'''Promotional'''
 
'''Promotional'''
Line 26: Line 27:
 
#* We send the post to press contacts
 
#* We send the post to press contacts
 
#* Two days later we publish everywhere (see below)
 
#* Two days later we publish everywhere (see below)
  +
   
 
'''Places we Update'''
 
'''Places we Update'''
  +
 
#* on identi.ca
 
#* on identi.ca
 
#* on diaspora
 
#* on diaspora
Line 36: Line 39:
 
#* digg
 
#* digg
 
#* the GNU mailing list, aka info-gnu@gnu.org "plain text is greatly preferred" omit screenshots or replace with links.
 
#* the GNU mailing list, aka info-gnu@gnu.org "plain text is greatly preferred" omit screenshots or replace with links.
  +
   
 
'''Press Contacts'''
 
'''Press Contacts'''
  +
 
#* write to Zonker
 
#* write to Zonker
 
#* LinuxJournal
 
#* LinuxJournal
Line 43: Line 48:
 
#* OpenSource.com
 
#* OpenSource.com
 
#* see if the FSF will blog or announce
 
#* see if the FSF will blog or announce
  +
   
 
== Post release process ==
 
== Post release process ==
   
 
# change version number to the next one + <code>-dev</code> in files listed above
 
# change version number to the next one + <code>-dev</code> in files listed above
  +
# add new milestone to Trac

Revision as of 10:01, 13 February 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. Run the unit tests: ./runtests.sh If any tests fail, proceed no further!
  6. Update version numbers in these files:
    • mediaboglin/_version.py
    • docs/source/conf.py
  7. Tag: git tag -a vX.Y.Z
  8. Build the tarfile. ./devtools/maketarball.sh -r vX.Y.Z
  9. Push the tarball to the web-site: add tarball to site/static/download/ directory in mediagoblin-website repository and then push the site live
  10. 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