Changes between Version 15 and Version 16 of ReleaseProcess


Ignore:
Timestamp:
04/27/11 09:31:23 (3 years ago)
Author:
dread
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ReleaseProcess

    v15 v16  
    55See also: VersioningPolicy 
    66 
    7 = Approaching CKAN release - alpha release = 
     7= Branching for CKAN release - beta release = 
    88 
    9  1. Change the version number to the next version alpha in ckan/__init__.py e.g. 1.2a 
    10  1. Commit and push this change. 
    11  1. Bring metastable branch in line with default:  
     9Branch and release a 'beta' when you have new features you want to burn in. We normally try out a beta release on ckan.net for a week before it is released properly. 
     10 
     11 1. Run the most thorough tests on the code. 
     12 1. Create the branch for the new version, named without the beta letter and according to the branch naming policy http://wiki.ckan.net/Mercurial : 
    1213{{{ 
    13 $ hg up -C metastable 
    14 $ hg merge -r default 
    15 $ nosetests ckan/tests 
    16 $ hg ci -m '[merge] from release 1.1a.' 
    17 $ hg push 
     14$ hg branch release-v1.2 
     15}}} 
     16 1. Change the version number to the new version, but 'beta' in ckan/__init__.py e.g. 1.2b (this will show-up in the web interface, bottom-right corner.) 
     17 1. Change the pip-requirements.txt to refer to the new branch (buildbot will fail if you forget): 
     18{{{ 
     19-e hg+https://bitbucket.org/okfn/[email protected]#egg=ckan 
     20# CKAN dependencies 
     21-r https://bitbucket.org/okfn/ckan/raw/release-v1.2/requires/lucid_conflict.txt 
     22-r https://bitbucket.org/okfn/ckan/raw/release-v1.2/requires/lucid_present.txt 
     23-r https://bitbucket.org/okfn/ckan/raw/release-v1.2/requires/lucid_missing.txt 
     24}}} 
     25 1. Commit these changes: 
     26{{{ 
     27$ hg ci -m '[release] branch.' 
    1828}}} 
    1929 
     30= Doing a proper CKAN release = 
    2031 
    21 = Doing a CKAN release = 
     32Once the beta has been tested manually on a live instance for a week you can do a release. 
    2233 
    23  1. Test the code satisfactorily. 
     34 1. Run the most thorough tests. 
    2435 1. Summarise the tickets going in this release in the ckan/doc/CHANGELOG.rst 
    25  1. Remove the pre-release letter in the version number in ckan/__init__.py e.g. 1.1c -> 1.1 
     36 1. Remove the beta letter in the version number in ckan/__init__.py e.g. 1.1b -> 1.1 
    2637 1. Commit this change. 
    2738 1. Update the internationalization POT file and commit it: 
    … …  
    5768$ hg up default 
    5869$ hg merge -r release-v1.3.2 
     70$ hg revert ckan/__init__.py pip-requirements.txt  
    5971$ nosetests --ckan ckan/tests 
    6072$ hg ci -m '[merge] from release-v1.3.2.'