-
Notifications
You must be signed in to change notification settings - Fork 372
HowToRelease
Giovanni Mascellani edited this page Jul 14, 2014
·
30 revisions
Some developer notes on how to do the release (magic numbers are for version 1.1):
-
Create a Release Notes page on the wiki (with some sensible content in it!) and modify History to link it.
-
Create a branch for the version number:
git checkout -b v1.1
-
Commit new version number (one change in
setup.py
, one indocs/conf.py
):git commit -a -m 'Version 1.1.0'
-
Tag the commit:
git tag v1.1.0
-
Push branch and tag to the repository. Push also changes to the wiki.
-
Check that relevant automatic links have been created by GitHub, so that there are no 404 errors around (in wiki and in docs).
-
Send Release Notes to the mailing list (for reference: http://www.freelists.org/post/contestms/CMS-100-RELEASE-NOTES).
-
Go back to
master
and commit new version numbers (one change insetup.py
, two changes indocs/conf.py
).