ReleaseProcess: Difference between revisions
Jump to navigation
Jump to search
(throw together rough release process) |
(added pypi, fixing version numbers and announcement steps) |
||
Line 52: | Line 52: | ||
FIXME - we need to set this up |
FIXME - we need to set this up |
||
'''9. update PYPI''' |
|||
FIXME - need instructions, accounts, etc |
|||
'''10. update version numbers in git''' |
|||
# setup.py |
|||
# docs/conf.py |
|||
'''11. announce the release''' |
Revision as of 22:11, 30 July 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. run the unit tests:
./runtests.sh
If any tests fail, proceed no further!
4. update version numbers
- setup.py
- 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
9. update PYPI
FIXME - need instructions, accounts, etc
10. update version numbers in git
- setup.py
- docs/conf.py
11. announce the release