Changes between Version 71 and Version 72 of ReleaseProcedure

Timestamp:

Mar 4, 2011, 4:15:04 AM (12 years ago)

Author:

Peter Johansson

Comment:

resolve ticket #466 (make tarball and tag identical)

ReleaseProcedure

@@ -106 +106 @@
   1. Update copyright statements with commands
 {{{
-make check && ./bin/svncopyright -v
+make 
+./bin/svncopyright -v
 }}}
   Examine the updates and commit changes with `svn ci -m "updating
@@ -121 +122 @@
 }}}
      Fix potential problems.[[br]][[br]]
-  1. Check that you are synchronized with repository
-{{{
-svn status -qu
-}}}
-  and then create a tag using a one liner like
-{{{
-svn copy ^/branches/A.B-stable ^/tags/A.B -m "tagging version A.B"
+  1. Create a tag using
+{{{
+make tag
+}}}
+  1. Update wc to latest revision and create tarball
+{{{
+svn update
+make release
 }}}
   1. Upload `svndigest-A.B.tar.gz` and md5 file to sourceforge using scp like
@@ -234 +236 @@
   1. Update copyright statements with commands[[br]][[br]]
 {{{
-make check && ./bin/svncopyright -v
+make
+./bin/svncopyright -v
 }}}
     Examine the updates and commit changes with `svn ci -m "updating
@@ -249 +252 @@
 }}}
      Fix potential problems[[br]][[br]]
-  1. Check that you are synchronized with repository
-{{{
-svn status -qu
-}}}
-   and then create a tag 
-{{{
-svn copy ^/branches/A.B-stable ^/tags/A.B.C -m "tagging version A.B.C"
+  1. Create a tag using
+{{{
+make tag
+}}}
+  1. Update wc to latest revision and create tarball
+{{{
+svn update
+make release
 }}}
   1. Upload `svndigest-A.B.C.tar.gz` and md5 file to sourceforge using scp like