ReleaseProcess

From GNU MediaGoblin Wiki
(Difference between revisions)
Jump to: navigation, search
(Steps to release)
(Steps to release)
Line 5: Line 5:
 
Here's the list of steps to do a release.
 
Here's the list of steps to do a release.
  
#'''Technical'''
+
'''Technical'''
  
 
# Verify with others on IRC that we're good to go.
 
# Verify with others on IRC that we're good to go.
Line 19: Line 19:
 
# Update on PYPI - '''FIXME - need to set this up'''
 
# Update on PYPI - '''FIXME - need to set this up'''
  
#'''Promotional'''
+
'''Promotional'''
  
 
# Blog post
 
# Blog post
Line 28: Line 28:
 
#* Two days later we publish everywhere (see below)
 
#* Two days later we publish everywhere (see below)
  
# Update sites:
+
'''Places we Update'''
 
#* on identi.ca
 
#* on identi.ca
 
#* on diaspora
 
#* on diaspora
Line 38: Line 38:
 
#* 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  

Revision as of 10:35, 13 December 2011

Release Process

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

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
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox