Changes between Version 1 and Version 2 of Dev_ReleaseManagement


Ignore:
Timestamp:
Mar 9, 2009 5:55:02 PM (4 years ago)
Author:
till
Comment:

refined with feedback from Thomas

Legend:

Unmodified
Added
Removed
Modified

  • Dev_ReleaseManagement

    v1 v2  
    1 How do we release? 
     1How do we release a new version of RoundCube? This document aims to provide an answer. 
    22 
    33= Create a branch = 
    … …  
    1515{{{ 
    1616svn cp trunk/ branches/release-x.y 
    17 svn cp trunk/ tags/release-x.y 
    18 svn ci -m "new x.y release" 
     17svn del branches/release-x.y/bin/dumpschema.php 
     18svn del branches/release-x.y/bin/makedoc.sh 
     19svn del branches/release-x.y/tests 
     20}}} 
     21 
     22 * edit branches/release-x.y/CHANGELOG 
     23 * edit branches/release-x.y/README and remove SVN disclaimer 
     24 * bump up RoundCube's version in `config/main.inc.php.dist` 
     25 * bump up RoundCube's version in `index.php` 
     26 * bump up RoundCube's version in `program/include/iniset.php` 
     27 
     28{{{ 
     29svn ci -m "new x.y release branch" 
     30svn cp branches/release-x.y tags/release-x.y 
     31svn ci -m "new x.y release tag" 
    1932}}} 
    2033 
    … …  
    2235 
    2336 * a tag may not be "patched" or "hotfixed" 
    24  * branch maybe "patched" or "hotfixed" 
    25  * in case you apply a fix to a branch, please create a new tag as well 
     37 * branch may be "patched" or "hotfixed" 
     38 * in case you apply a fix to a branch, please create a new tag from it 
    2639 
    2740== creating a tag after a fix == 
    … …  
    3245}}} 
    3346 
    34 = create download = 
     47= Create Download = 
    3548 
    36 == major relase == 
     49== Major Relase == 
     50 
    3751{{{ 
    3852svn export http://trac.roundcube.net/branches/release-x.y ./roundcubemail 
    … …  
    4256}}} 
    4357 
     58 * the version naming should obviously match the branch/tag 
    4459 * distribute release on SourceForge 
    4560 * adjust naming in case of a "hotfix" / "patch" 
    4661 
    47 == minor release / hotfix == 
     62== Minor Release / Hotfix == 
    4863 
    4964 * repeat entire process 
    … …  
    5772 * distribute patch on SourceForge 
    5873 
    59 = announcements = 
     74= Announcements = 
    6075 
    6176 * write news entry on SourceForge 
    … …  
    6782 * encourage maintainers to subscribe to announce@ 
    6883 * seperately ping distros 
     84 * maybe a PEAR package with replacement tasks? (`@package_version@`)