Version 6 (modified by dread, 4 years ago) (diff) |
---|
About Releases
The OKF aims to make releases CKAN regularly - minor points every two months. Find releases at: PyPI. See the changes at on the Changelog.
Doing a CKAN release
- Test the code satisfactorily.
- Summarise the tickets going in this release in the ckan/doc/CHANGELOG.rst
- Remove the pre-release letter in the version number in ckan/init.py e.g. 1.1c -> 1.1
- Commit this change.
- Compile the docs:
$ python setup.py build_sphinx
- Upload docs to knowledgeforge.
- 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
- 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
- Change the version number to the next version alpha in ckan/init.py e.g. 1.2a
- Commit and push this change.
- Bring metastable branch in line with default:
$ hg up -C metastable $ hg merge -r default $ nosetests ckan/tests $ 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
- 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.