| | 1 | = About Releases = |
| | 2 | |
| | 3 | The OKF aims to make releases CKAN regularly - minor points every two months. Find releases at: [http://pypi.python.org/pypi/ckan PyPI]. See the changes at on the [http://knowledgeforge.net/ckan/doc/ckan/CHANGELOG.html Changelog]. |
| | 4 | |
| | 5 | = Doing a CKAN release = |
| | 6 | |
| | 7 | 1. Test the code satisfactorily. |
| | 8 | 1. Summarise the tickets going in this release in the ckan/doc/CHANGELOG.rst |
| | 9 | 1. Compile the docs: |
| | 10 | {{{ |
| | 11 | $ python setup.py build_sphinx |
| | 12 | }}} |
| | 13 | 1. Upload docs to knowledgeforge. |
| | 14 | 1. Change the version number in ckan/__init__.py |
| | 15 | 1. Tag the repo with the version number (commits change). e.g. |
| | 16 | {{{ |
| | 17 | $ hg tag ckan-1.1 -m 'Release 1.1' |
| | 18 | $ hg push |
| | 19 | }}} |
| | 20 | 1. Upload the release to PyPI: |
| | 21 | {{{ |
| | 22 | python setup.py sdist upload |
| | 23 | }}} |
| | 24 | 1. Bring metastable branch in line with default: |
| | 25 | {{{ |
| | 26 | $ hg -C metastable |
| | 27 | $ hg merge -r ckan-1.1 |
| | 28 | $ hg ci -m '[merge] from release 1.1' |
| | 29 | $ hg push |
| | 30 | }}} |
| | 31 | |
| | 32 | If there have been any unreleased changes to vdm, make sure you release that too. |
