Changes between Version 26 and Version 27 of ReleaseProcedure

Timestamp:

Jul 9, 2007, 11:05:12 PM (15 years ago)

Author:

Peter Johansson

Comment:

--

ReleaseProcedure

@@ -170 +170 @@
 This section describes what to do when publishing a patch release A.B.C.
 
- 1. Make sure that all commits are performed into to the trunk, such
+ 1. Make sure that all commits are performed into to the branch, such
     as bumping version number(s) (`configure.ac`), acknowledge
     contributions (`THANKS`), update files `NEWS` and
@@ -192 +192 @@
         - http://trac.thep.lu.se/trac/svndigest/query?milestone=A.B.C&order=id
 }}}
+  where `N` is given by 
+{{{
+$ svn update
+N-2
+}}}
+  and `M` should have been set at previous release.[[br]][[br]]
   i. Commit changes to the repository, `svn ci -m "Preparing release A.B.C"`
      [[br]][[br]]
@@ -201 +207 @@
 ./bin/svndigest --copyright
 }}}
- Examine the updates and commit changes with `svn ci -m "updating copyright statements"`[[br]][[br]]
+ Examine the updates and commit changes with `svn ci -m "updating copyright statements"`.[[br]][[br]]
  1. Needless to say, make sure that the program is in a state to be
     released; make sure that all the tests pass, test the distribution
@@ -213 +219 @@
  1. Create a tag using a one liner like
 {{{
-svn copy http://lev.thep.lu.se/repository/svndigest/branch/A.B-stable \
+svn copy http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable \
     http://lev.thep.lu.se/repository/svndigest/tags/A.B.C \
     -m "Tagging version A.B.C"