ReleaseProcess
From GNU MediaGoblin Wiki
(Difference between revisions)
(→Steps to release) |
(→Steps to release) |
||
| Line 5: | Line 5: | ||
Here's the list of steps to do a release. | Here's the list of steps to do a release. | ||
| − | + | '''Technical''' | |
# Verify with others on IRC that we're good to go. | # Verify with others on IRC that we're good to go. | ||
| Line 19: | Line 19: | ||
# Update on PYPI - '''FIXME - need to set this up''' | # Update on PYPI - '''FIXME - need to set this up''' | ||
| − | + | '''Promotional''' | |
# Blog post | # Blog post | ||
| Line 28: | Line 28: | ||
#* Two days later we publish everywhere (see below) | #* Two days later we publish everywhere (see below) | ||
| − | + | '''Places we Update''' | |
#* on identi.ca | #* on identi.ca | ||
#* on diaspora | #* on diaspora | ||
| Line 38: | Line 38: | ||
#* the GNU mailing list, aka info-gnu@gnu.org "plain text is greatly preferred" omit screenshots or replace with links. | #* the GNU mailing list, aka info-gnu@gnu.org "plain text is greatly preferred" omit screenshots or replace with links. | ||
| − | + | '''Press Contacts''' | |
#* write to Zonker | #* write to Zonker | ||
#* LinuxJournal | #* LinuxJournal | ||
Revision as of 10:35, 13 December 2011
Release Process
Steps to release
Here's the list of steps to do a release.
Technical
- 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
Promotional
- Blog post
- Chris sends Deb technical highlights
- Deb drafts post
- Chris adds screenshots/links
- We send the post to press contacts
- Two days later we publish everywhere (see below)
Places we Update
- 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.
Press Contacts
- write to Zonker
- LinuxJournal
- LWN
- OpenSource.com
- see if the FSF will blog or announce
Post release process
- change version number to the next one +
-devin files listed above
