ReleaseProcess

From GNU MediaGoblin Wiki
Revision as of 17:49, 30 July 2011 by Willkg (talk | contribs) (throw together rough release process)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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. run the unit tests:

./runtests.sh

If any tests fail, proceed no further!


4. update version numbers

  1. setup.py
  2. docs/conf.py


5. tag

git tag -a vX.Y.Z


6. generate documentation

FIXME - this step needs more work

./generatedocs.sh


7. build the tarfile

FIXME - this step needs to incorporate the generated docs above; probably need to add an optional argument to maketarball.sh that takes a directory of stuff to add to the tarball after it's been created.

./maketarball.sh <TAG>


8. push the tarball to the site

FIXME - we need to set this up