ReleaseProcess

Steps to release
Here's the list of steps to do a release.

Technical

Pre-release checklist:


 * 1) Update AUTHORS file
 * 2) check git commits
 * 3) ask on mailing list
 * 4) other ways?
 * 5) Update documentation
 * 6) update README
 * 7) update docs/source/siteadmin/relnotes.rst
 * 8) update install guide
 * 9) other things?

Release checklist:


 * 1) Verify with others on IRC that we're good to go.
 * 2) Do a  and make sure you have the latest code.
 * 3) Do a  and make sure you have the latest translations.
 * 4) Do a  to make sure building the docs and tarball works. If any errors, proceed no further!
 * 5) Do a  to wipe all non-repository files out (THIS DELETES EVERYTHING), go through hacking howto to reinstall.
 * 6) Run the unit tests:   If any tests fail, proceed no further!
 * 7) Update version numbers in mediaboglin/_version.py
 * 8) Tag:  (consider  to create a signed tag).
 * 9) Push the tag to origin:
 * 10) Update stable branch to current release and push to origin
 * 11) Build the tarfile.    (Note, you may have to do this in a virtualenv...  before running)
 * 12) Push the tarball to the web-site: add tarball to site/static/download/ directory in mediagoblin-website repository and then push the site live
 * 13) Update on PYPI -

EasyDeployments contributions (a suggestion made by JF)


 * 1) Contact the EasyDeployments contributors, asking them to update, e.g. by filing issues at:
 * 2) https://notabug.org/dachary/mediagoblin-docker/issues
 * 3) https://github.com/jparyani/mediagoblin/issues
 * 4) (check the Wiki page to see if this list is still accurate)

Promotional


 * 1) Blog post
 * 2) * Chris sends Deb technical highlights
 * 3) * Deb drafts post
 * 4) * Chris adds screenshots/links
 * 5) * We send the post to press contacts
 * 6) * Two days later we publish everywhere (see below)

Places we Update


 * 1) * on identi.ca
 * 2) * on diaspora
 * 3) * on Facebook (Deb)
 * 4) * on Twitter
 * 5) * our mailing list, encouraging people to fave, like, repost, etc.
 * 6) * reddit
 * 7) * digg
 * 8) * the GNU mailing list, aka info-gnu@gnu.org "plain text is greatly preferred" omit screenshots or replace with links.

Press Contacts


 * 1) * write to Zonker
 * 2) * LinuxJournal
 * 3) * LWN
 * 4) * OpenSource.com
 * 5) * see if the FSF will blog or announce

Post release process

 * 1) change version number to the next one +   in files listed above
 * 2) add new milestone to Trac