Revision as of 15:34, 13 December 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 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

Press Contacts
- write to Zonker
- LinuxJournal
- LWN
- OpenSource.com
- see if the FSF will blog or announce

@@ Line 4: / Line 4: @@
 Here's the list of steps to do a release.
+#'''Technical'''
 # Verify with others on IRC that we're good to go.
@@ Line 16: / Line 18: @@
 # 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 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)
 # Update sites:
 #* on identi.ca
@@ Line 25: / Line 37: @@
 #* 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'''
+# '''Press Contacts'''
 #* write to Zonker
 #* LinuxJournal
 #* LWN
+#* OpenSource.com
 #* see if the FSF will blog or announce