ReleaseProcess: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(updated release process; fleshed some things out; moved some things around) |
||
Line 1: | Line 1: | ||
= Release Process = |
= Release Process = |
||
== Steps to release == |
|||
Here's the list of steps to do a release. |
Here's the list of steps to do a release. |
||
Line 7: | Line 9: | ||
# Do a <tt>tx pull -a</tt> and make sure you have the latest [[Translations|translations]]. |
# 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 |
# Update version numbers in these files: |
||
#* mediaboglin/_version.py |
|||
#* docs/source/conf.py |
|||
# 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 web-site: add tarball to <pre>site/static/download/</pre> directory in mediagoblin-website repository and then push the site live |
||
# Update |
# Update on PYPI - '''FIXME - need to set this up''' |
||
# Update sites: |
|||
# 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. |
|||
⚫ | |||
preferred" omit screenshots or replace with links. |
|||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
== Post release process == |
|||
# change version number to the next one + <code>-dev</code> in files listed above |
|||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ |
Revision as of 17:21, 12 December 2011
Release Process
Steps to release
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 these files:
- mediaboglin/_version.py
- docs/source/conf.py
- Tag: git tag -a vX.Y.Z
- Build the tarfile. ./maketarball.sh -r vX.Y.Z
- Push the tarball to the web-site: add tarball to
site/static/download/
directory in mediagoblin-website repository and then push the site live - Update on PYPI - FIXME - need to set this up
- Update sites:
- on identi.ca
- on diaspora
- on Facebook (Deb)
- on Twitter
- our mailing list, encouraging people to fave, like, repost, etc.
- 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
Post release process
- change version number to the next one +
-dev
in files listed above