ReleaseProcess

From GNU MediaGoblin Wiki
(Difference between revisions)
Jump to: navigation, search
(add promo)
Line 20: Line 20:
 
  * reddit
 
  * reddit
 
  * digg
 
  * digg
  * the GNU mailing list
+
  * the GNU mailing list, aka info-gnu@gnu.org "plain text is greatly
 +
preferred" omit screenshots or replace with links.
 +
 
 
   *** For 1.0 and other major versions after that one
 
   *** For 1.0 and other major versions after that one
 
       * write to Zonker
 
       * write to Zonker

Revision as of 11:41, 12 November 2011

Release Process

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
    mediaboglin/_version.py
    and
    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 site: see Update the website and add tarball to
    site/static/download/
  9. Update sites: PYPI, etc FIXME - need to set this up
  10. Announce the release
* 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. 
 *** For 1.0 and other major versions after that one
     * write to Zonker
     * LinuxJournal 
     * LWN
     * see if the FSF will blog or announce
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox