Changes between Version 51 and Version 52 of ReleaseProcedure

Timestamp:

Jan 20, 2010, 3:07:21 AM (13 years ago)

Author:

Peter

Comment:

use svndigest-copy-cache in RP

ReleaseProcedure

@@ -55 +55 @@
 svndigest --copyright --no-report -v
 }}}
- (The `--no-report` option works with svndigest 0.7 and later, for
- earlier version omit the option.) Examine the updates and commit
+ Examine the updates and commit
  changes with `svn ci -m "updating copyright statements"`.  For this
  step [http://dev.thep.lu.se/svndigest svndigest] is obviously
  needed.[[br]][[br]]
- 1. Make a copy of trunk WC including svndigest cache
-{{{
-cp -rpv /path/to/yat-trunk /path/to/yat-A.B.x
-}}}
  1. Create a new minor branch using a one liner like
 {{{
@@ -70 +65 @@
     -m "New minor version A.B branch"
 }}}
- 1. Switch the new WC to follow new branch
-{{{
-cd /path/to/yat-A.B.x/
-svn switch http://dev.thep.lu.se/yat/svn/branches/A.B-stable 
-cd /path/to/yat-trunk/
-}}}
+ 1. Check out a WC from the newly created branch
+{{{
+svn co http://dev.thep.lu.se/yat/svn/branches/A.B-stable yat-A.B
+}}}
+ 1. Copy the svndigest cache from trunk WC to branch WC
+{{{
+svndigest-copy-cache -v -r /path/to/yat-trunk -t /path/to/yat-A.B
+}}}
+   which needs svndigest 0.8 or newer.[[br]][[br]]
  1. Prepare the trunk for the next minor release [[br]][[br]]
   i. Update version number in `m4/version.m4`. Locate and change the