ReleaseProcess: Difference between revisions
Jump to navigation
Jump to search
(update version and remove obsolete command) |
(add note about translations) |
||
Line 5: | Line 5: | ||
# Verify with others on IRC that we're good to go. |
# Verify with others on IRC that we're good to go. |
||
# Do a <tt>git fetch</tt> and make sure you have the latest code. |
# Do a <tt>git fetch</tt> and make sure you have the latest code. |
||
# Do a <tt>tx pull -a</tt> and make sure you have the latest [[Translations|translations]]. |
|||
# Run the unit tests: {{Cmd|./runtests.sh}} If any tests fail, proceed no further! |
# Run the unit tests: {{Cmd|./runtests.sh}} If any tests fail, proceed no further! |
||
# Update version numbers in <pre>mediaboglin/_version.py</pre> and <pre>docs/source/conf.py</pre>. |
# Update version numbers in <pre>mediaboglin/_version.py</pre> and <pre>docs/source/conf.py</pre>. |
Revision as of 02:26, 2 November 2011
Release Process
Here's the list of steps to do a release.
- Verify with others on IRC that we're good to go.
- Do a git fetch and make sure you have the latest code.
- Do a tx pull -a and make sure you have the latest translations.
- Run the unit tests: ./runtests.sh If any tests fail, proceed no further!
- Update version numbers in
mediaboglin/_version.py
anddocs/source/conf.py
. - Tag: git tag -a vX.Y.Z
- Build the tarfile. ./maketarball.sh -r vX.Y.Z
- Push the tarball to the site FIXME - need to set this up
- Update sites: PYPI, etc FIXME - need to set this up
- Update version numbers in git:
mediagoblin/_version.py
anddocs/source/conf.py
- Announce the release