Changes between Version 21 and Version 22 of Release


Ignore:
Timestamp:
02/15/11 11:54:54 (3 years ago)
Author:
waxhead
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Release

    v21 v22  
    6565 
    6666In order to allow a few days of stabilization of Padre and to allow the translators to catch up while  
    67 allowing everyone else to freely work on the main trunk we can start releasing from a branch. Trying to capture 
    68 the process here. 
     67allowing everyone else to freely work on the main trunk we can start releasing from a branch.  
    6968 
    70  * A few (2 ?) days before the planned release date the release manager creates a copy: 
     69A few (2 or 3) days before the planned release date the release manager creates an svn copy of trunk to branches/release-n.nn. 
     70 
     71Prior to creating the copy the following steps are taken: 
     72 
    7173 * run perltidy on the trunk 
    72  * svn cp http://svn.perlide.org/padre/trunk/Padre http://svn.perlide.org/padre/branches/Padre-X.XX   (replace X.XX with the future version number) 
    73  * Anyone who wants to work on the release branch can 
     74 * commit  
     75 * Update the Changes file, noting the date of the release being the date you start the branch 
     76 * commit 
     77 * set the version from the current development version number to the release version number ( should be even numbered for released odd numbers for development ) 
     78  * Note: there is a script in tools that will update the $VERSION string, however PPI::PowerToys has an awesome ppi_version, use this when you can: ppi_version change old new, ie ppi_version change 0.81 0.82 
     79 * commit 
     80 * rebuild the "messages.pot" file, run ../tools/update_pot_file.pl 
     81 * commit 
     82 
     83At this point trunk is ready for you to make the branch: 
     84 * svn cp http://svn.perlide.org/padre/trunk/Padre http://svn.perlide.org/padre/branches/release-X.XX   (replace X.XX with the future version number) 
     85 
     86You have now created the release branch for Padre. 
     87 
     88To complete the final tasks on trunk, update the Changes file by "opening" the next version. 
     89 * Modify Changes, set the next development version number, should be odd and the next release version number, should be even, ie if you have just branched release-0.82, then changes gets updated with: 
     90 
     910.84 TBA 
     92 
     930.83 Dev - not released. 
     94 
     95From this point onwards you switch your working copy between the branch and trunk as needed.  To switch between trunk and the branch: 
    7496 * cd trunk/Padre 
    75  * svn switch http://svn.perlide.org/padre/branches/Padre-X.XX . 
     97 * svn switch http://svn.perlide.org/padre/branches/release-X.XX . 
    7698 * then every commit will go to the branch while the plugins are still from trunk 
    7799 * the release can be done here but probably it is better NOT to run the perl tidy on the branch as it will make merging very difficult