ReleaseProcess: Difference between revisions
Jump to navigation
Jump to search
(add note about translations) |
|||
| Line 10: | Line 10: | ||
# Tag: {{Cmd|git tag -a vX.Y.Z}} |
# Tag: {{Cmd|git tag -a vX.Y.Z}} |
||
# Build the tarfile. {{Cmd|./maketarball.sh -r vX.Y.Z}} |
# Build the tarfile. {{Cmd|./maketarball.sh -r vX.Y.Z}} |
||
# Push the tarball to the site |
# Push the tarball to the site: see [[Update the website]] and add tarball to <pre>site/static/download/</pre> |
||
# Update sites: PYPI, etc '''FIXME - need to set this up''' |
# Update sites: PYPI, etc '''FIXME - need to set this up''' |
||
# Update version numbers in git: <pre>mediagoblin/_version.py</pre> and <pre>docs/source/conf.py</pre> |
|||
# Announce the release |
# Announce the release |
||
Revision as of 14:14, 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: see Update the website and add tarball to
site/static/download/
- Update sites: PYPI, etc FIXME - need to set this up
- Announce the release