Changes between Version 1 and Version 2 of ReleasePractices/Procedures


Ignore:
Timestamp:
Aug 12, 2008, 11:50:48 AM (14 years ago)
Author:
Beman Dawes
Comment:

Clarify target audience

Legend:

Unmodified
Added
Removed
Modified

  • ReleasePractices/Procedures

    v1 v2  
    11[[PageOutline]]
    22
    3 = Boost Release Procedures =
     3= Boost Release Procedures for Developers =
    44
    55''This is a placeholder page in that the content needs to be rewritten to account for the new process. When that happens the page can move to the new web site.''
    … …  
    9393                Modify | Create tag on selection... | Create tag settings | Enter the tag name to create: merged_to_RC_1_26_2, Overwrite existing tags with same name | OK.
    9494
    95 == Release Procedures for the Release Manager ==
    96 
    97 At time of branch-for-release:
    98 
    99     * Tag the main trunk  merged_to_RC_n_n_n.
    100     * Branch the main trunk with the tag RC_n_n_n.
    101 
    102 See Release Manager's Checklist for full details.
    10395
    10496== FAQ ==
    … …  
    10698What is the purpose of the merged_to_RC_n_n_n tag? This tag allows multiple merges from the main trunk to the release candidate branch. Without it, merging an initial main trunk fix  into the release candidate branch would work, but merging a second fix from main trunk to release candidate branch would result in a merge conflict. Although this procedure seems convoluted, it works much better in practice than several prior procedures we tried.
    10799
    108 == Acknowledgements ==
     100== Acknowledgments ==
    109101
    110102This web page was written by Beman Dawes, with helpful suggestions from Dave Abrahams and Steve Robbins. Jim Hyslop contributed the original CVS procedures. Updated by Jeff Garland after 1.29 release based on list discussions.