Changes between Version 5 and Version 6 of ReleaseProcedure


Ignore:
Timestamp:
Oct 8, 2007, 3:31:10 AM (14 years ago)
Author:
Peter
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcedure

    v5 v6  
    2121
    2222Releases should only be performed by an appointed member of the team,
    23 the Release Manager, and merges should be performed by a Merge
    24 Manager. Of course, one team member can be both managers, thus
    25 becoming the Release and Merge Manager.
     23the ''Release Manager'', and merges should be performed by a ''Merge
     24Manager''. Of course, one team member can be both managers, thus
     25becoming the ''Release'' and ''Merge Manager''.
    2626
    2727
     
    3232=== Creating a release branch ===
    3333
    34 Once people agree that a new release branch should be made, the Release Manager creates it with the following procedure (substitute A.B with the version you are preparing, ''e.g.'' 0.3, or 1.0):
     34Once people agree that a new release branch should be made, the ''Release Manager'' creates it with the following procedure (substitute A.B with the version you are preparing, ''e.g.'' 0.3, or 1.0):
    3535
    3636 1. Update copyright statements with command:
     
    181181}}}
    182182  i. In section '''yat ''devel'' ''' update link to `[milestone:A.B+1 A.B+1]`.[[br]][[br]]
    183   i. On WikiStart update links `[source:tags/A.B/doc/readme.txt Manual]` (in two places), `[source:tags/A.B/NEWS NEWS]`, and `[source:tags/A.B/INSTALL Install]`.[[br]][[br]]
     183  i. On WikiStart update links `[source:tags/A.B/NEWS NEWS]`.[[br]][[br]]
     184  i. Generate documentation to new version of yat, and update link on WikiStart
    184185 1. Close the [http://trac.thep.lu.se/trac/yat/roadmap milestone]
    185186    associated with the release and replace `head` with appropriate revision. Add a new milestone as needed (with log link).
    186 
    187187
    188188