Changes between Version 5 and Version 6 of ReleaseProcess

Timestamp:

08/10/10 16:51:26 (4 years ago)

Author:

dread

Comment:

--

ReleaseProcess

@@ -14 +14 @@
 }}}
  1. Upload docs to knowledgeforge.
- 1. Tag the repo with the version number (commits change). e.g.
+ 1. Tag the repo with the version number (commits change). (add -f to the tag if you want to overwrite a previous tag with this release) e.g.
 {{{
 $ hg tag ckan-1.1 -m 'Release 1.1'
 $ hg push
 }}} 
-(add -f to the tag if you want to overwrite a previous tag with this release)
- 1. Upload the release to PyPI: 
+ 1. Upload the release to PyPI (If you make a mistake, you can always go into PyPI, remove the release file and then reupload it.) 
 {{{
 python setup.py sdist upload
 }}}
-(If you make a mistake, you can always go into PyPI, remove the release file and then reupload it.)
+ 1. Change the version number to the next version alpha in ckan/__init__.py e.g. 1.2a
+ 1. Commit and push this change.
  1. Bring metastable branch in line with default: 
 {{{
-$ hg -C metastable
+$ hg up -C metastable
 $ hg merge -r default
 $ nosetests ckan/tests
-$ hg ci -m '[merge] from release 1.1'
+$ hg ci -m '[merge] from release 1.1.'
+$ hg push
+$ hg up -C default
+$ hg merge -r metastable
+$ hg ci -m '[merge] from metastable.'
 $ hg push
 }}}
- 1. Change the version number to the next version alpha in ckan/__init__.py e.g. 1.2a
- 1. Commit and push this change.
  1. Merge the release to the bitbucket i18n repo and recreate the pot:
 {{{
 ???
 }}}
- 
-If there have been any unreleased changes to vdm, make sure you release that too.
+ 1. If there have been any unreleased changes to vdm, make sure you release that too.