Changes between Version 1 and Version 2 of ReleaseProcess


Ignore:
Timestamp:
08/10/10 15:15:19 (4 years ago)
Author:
dread
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ReleaseProcess

    v1 v2  
    77 1. Test the code satisfactorily. 
    88 1. Summarise the tickets going in this release in the ckan/doc/CHANGELOG.rst 
     9 1. Remove the pre-release letter in the version number in ckan/__init__.py e.g. 1.1c -> 1.1 
    910 1. Compile the docs: 
    1011{{{ 
    … …  
    1213}}} 
    1314 1. Upload docs to knowledgeforge. 
    14  1. Change the version number in ckan/__init__.py 
    1515 1. Tag the repo with the version number (commits change). e.g. 
    1616{{{ 
    … …  
    2929$ hg push 
    3030}}} 
    31  
     31 1. Change the version number to the next version alpha in ckan/__init__.py e.g. 1.2a 
     32 1. Commit and push this change. 
     33 1. Merge the release to the bitbucket i18n repo and recreate the pot: 
     34{{{ 
     35??? 
     36}}} 
     37  
    3238If there have been any unreleased changes to vdm, make sure you release that too.