ReleaseProcess: Difference between revisions

Latest revision as of 16:01, 21 December 2016

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

Technical

Pre-release checklist:

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

Release checklist:

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 ./devtools/update_translations.sh and make sure you have the latest translations.
Do a ./devtools/maketarball.sh -dr HEAD to make sure building the docs and tarball works. If any errors, proceed no further!
Do a git clean -fdx to wipe all non-repository files out (THIS DELETES EVERYTHING), go through hacking howto to reinstall.
Run the unit tests: ./runtests.sh If any tests fail, proceed no further!
Update version numbers in mediaboglin/_version.py
Tag: git tag -a vX.Y.Z (consider --sign to create a signed tag).
Push the tag to origin: git push origin vX.Y.Z
Update stable branch to current release and push to origin
Build the tarfile. ./devtools/maketarball.sh -r vX.Y.Z (Note, you may have to do this in a virtualenv... source bin/activate before running)
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 - ./bin/python setup.py sdist bdist_egg upload

EasyDeployments contributions (a suggestion made by JF)

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

Promotional

Places we Update

Press Contacts

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

@@ Line 8: / Line 8: @@
 # Update <tt>AUTHORS</tt> file
-## check github commits
+## check git commits
 ## ask on mailing list
 ## other ways?
@@ Line 27: / Line 27: @@
 # Update version numbers in <tt>mediaboglin/_version.py</tt>
 # Tag: {{Cmd|git tag -a vX.Y.Z}} (consider {{Cmd|--sign}} to create a signed tag).
-# Push the tag to gitorious: {{Cmd|git push origin vX.Y.Z}}
+# Push the tag to origin: {{Cmd|git push origin vX.Y.Z}}
+# Update stable branch to current release and push to origin
-# Build the tarfile.  {{Cmd|./devtools/maketarball.sh -r vX.Y.Z}}
+# Build the tarfile.  {{Cmd|./devtools/maketarball.sh -r vX.Y.Z}}  (Note, you may have to do this in a virtualenv... {{Cmd|source bin/activate}} before running)
 # Push the tarball to the web-site: add tarball to <tt>site/static/download/</tt> directory in mediagoblin-website repository and then push the site live
-# Update on PYPI - '''FIXME - need to set this up'''
+# Update on PYPI - {{Cmd|./bin/python setup.py sdist bdist_egg upload}}
+EasyDeployments contributions ''(a suggestion made by JF)''
+# Contact the EasyDeployments contributors, asking them to update, e.g. by filing issues at:
+## https://notabug.org/dachary/mediagoblin-docker/issues
+## https://github.com/jparyani/mediagoblin/issues
+## (check the Wiki page to see if this list is still accurate)
 '''Promotional'''