Changes between Version 1 and Version 2 of ReleaseProcedure

Timestamp:

Jun 25, 2007, 8:45:49 PM (14 years ago)

Author:

Peter Johansson

Comment:

setting project name to svndigest

ReleaseProcedure

@@ -2 +2 @@
 = Release Procedure =
 
-Pandai uses "MAJOR.MINOR.PATCH" release numbers, with the same guidelines as APR (see http://apr.apache.org/versioning.html).
+Svndigest uses "MAJOR.MINOR.PATCH" release numbers, with the same guidelines as APR (see http://apr.apache.org/versioning.html).
 
 === Creating a release branch ===
@@ -13 +13 @@
   1.  Edit `NEWS` on trunk to introduce a new section for the upcoming release. The section starts with: 
 {{{
-Version A.B.0 (released ?? ????? 200X, from /branches/A.B-stable)
-      http://lev.thep.lu.se/repository/pandai/tags/A.B
+Version A.B (released ?? ????? 200X, from /branches/A.B-stable)
+      http://lev.thep.lu.se/repository/svndigest/tags/release-A.B
 }}}
   Leave the release date blank for now. It will remain this way until rolling time.
@@ -22 +22 @@
   3.  Create a new release branch using a one liner like
 {{{
-  svn copy http://lev.thep.lu.se/repository/pandai/trunk \
-           http://lev.thep.lu.se/repository/pandai/branches/A.B-stable \
-           -m "New branch for Pandai A.B.x"
+  svn copy http://lev.thep.lu.se/repository/svndigest/trunk \
+           http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable \
+           -m "New branch for svndigest A.B.x"
 }}}
 
@@ -43 +43 @@
   3. Create a tag with 
 {{{
-  svn copy . http://lev.thep.lu.se/repository/pandai/tags/A.B \
+  svn copy . http://lev.thep.lu.se/repository/svndigest/tags/A.B \
            -m "Tagging version A.B.C"
 }}}
@@ -50 +50 @@
     * Upload gzipped tar file and update corresponding link.
     * Update link to NEWS file to `source:tags/A.B.C/NEWS`
-    * In ''Pandai latest release'' update to `[source:tags/A.B.C/NEWS NEWS]` and modify svn command to  
-      `svn checkout http://lev.thep.lu.se/repository/pandai/tags/A.B.C pandai-A.B.C`
-    * In ''Pandai stable'' update link to `[milestone:A.B.(C++) A.B.(C++)]dev` and modify svn command to 
-      `svn checkout http://lev.thep.lu.se/repository/pandai/branches/A.B-stable pandai-A.B.(C++)dev`
-    * In ''Pandai devel'' modify svn command to 
-      `svn checkout http://lev.thep.lu.se/repository/pandai/trunk pandai-A.(B++).0dev`
+    * In ''Svndigest latest release'' update to `[source:tags/A.B.C/NEWS NEWS]` and modify svn command to  
+      `svn checkout http://lev.thep.lu.se/repository/svndigest/tags/A.B.C svndigest-A.B.C`
+    * In ''Svndigest stable'' update link to `[milestone:A.B.(C++) A.B.(C++)]dev` and modify svn command to 
+      `svn checkout http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable svndigest-A.B.(C++)dev`
+    * In ''Svndigest devel'' modify svn command to 
+      `svn checkout http://lev.thep.lu.se/repository/svndigest/trunk svndigest-A.(B++).0dev`
 
   5. Set ''devel'' to `true` in `configure.ac`.
@@ -64 +64 @@
     * Find head revision (M) in release branch: `svn info | grep Rev:`
     * `cd path/to/trunk`
-    * `svn merge -r N:M http://lev.thep.lu.se/repository/pandai/branches/A.B-stable`
+    * `svn merge -r N:M http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable`
     * Run `make check` to make sure that the merge succeeded.
     * Commit changes to trunk: `svn commit -m "Merged log:branches/0.1-stable#N:M trunk."` 
@@ -73 +73 @@
 {{{
 Version A.B.0 (released ?? ????? 200X, from /branches/A.B-stable)
-      http://lev.thep.lu.se/repository/pandai/tags/A.B.(C++)
+      http://lev.thep.lu.se/repository/svndigest/tags/A.B.(C++)
 }}}
   Leave the release date blank for now. It will remain this way until rolling time.