svn commit: r1339535 - /pivot/infra/CREATE_RELEASE_WORKFLOW

[sm...@apache.org]

Author: smartini
Date: Thu May 17 10:11:12 2012
New Revision: 1339535

URL: http://svn.apache.org/viewvc?rev=1339535&view=rev
Log:
fix typo

Modified:
    pivot/infra/CREATE_RELEASE_WORKFLOW

Modified: pivot/infra/CREATE_RELEASE_WORKFLOW
URL: http://svn.apache.org/viewvc/pivot/infra/CREATE_RELEASE_WORKFLOW?rev=1339535&r1=1339534&r2=1339535&view=diff
==============================================================================
--- pivot/infra/CREATE_RELEASE_WORKFLOW (original)
+++ pivot/infra/CREATE_RELEASE_WORKFLOW Thu May 17 10:11:12 2012
@@ -37,6 +37,9 @@ infra/bin/setup-environment-sample.sh
 
 Note that currently you need to copy its contents and paste in a terminal, or in your profile file.
 
+Note: of course <release-number> in this document has to be changed with the real release version,
+for example currenly it's 2.0.2 .
+
 
 Generated artifacts will be digitally signed by PGP / GPG, so the Release Manager MUST have a valid PGP / GPG sign (on its apache.org mail address), and must be published to some public key server (for example the MIT Key server), and that sign must be appended at the and of the KEYS file (under the trunk) and committed.
 
@@ -104,7 +107,7 @@ Note: remember to NOT commit the rat.out
 
 6 - Create the tag in svn
 From the root folder (the parent folder of trunk), for example run:
-./infra/bin/create-tag.sh 2.0.2
+./infra/bin/create-tag.sh <release-number>
 
 Important: if the tag already exist it will not be possible to proceed successfully, so you have to delete the tag by hand, and re-execute this command.
 
@@ -113,14 +116,14 @@ Note that in some cases could be safer t
 
 6 - Create the release
 From the trunk folder, for example run:
-../infra/bin/create-release.sh 2.0.2
+../infra/bin/create-release.sh <release-number>
 if all is good, after approx. 15 minutes, you have the release.tar.gz file (containing all the required stuff) under the current folder.
 
 Note: remember to NOT commit this file in svn, and the same for other temporary folders generated by builds (like maven, install, lib, and maybe others). 
 
 7- Prepare generated artifacts for the copy
-MOVE release.tar.gz outside the "root" folder in a newly created folder (for example in ../../pivot-2.0.2_release), and untar/unzip it there. And maybe COPY even the KEYS file from the trunk to that folder.
-MOVE the folder maven at the same level of the newly created folder, and rename it for example in pivot-2.0.2_maven, then make a zip/tar.gz of its bundle subfolder and then delete it (keep only the zipped version).
+MOVE release.tar.gz outside the "root" folder in a newly created folder (for example in ../../pivot-<release-number>_release), and untar/unzip it there. And maybe COPY even the KEYS file from the trunk to that folder.
+MOVE the folder maven at the same level of the newly created folder, and rename it for example in pivot-<release-number>_maven, then make a zip/tar.gz of its bundle subfolder and then delete it (keep only the zipped version).
 
 
 8 - Cleanup unnecessary files/folders from the trunk
@@ -133,11 +136,11 @@ Note that you have to create destination
 ssh smartini@people.apache.org
 
 From the maven folder, for example run:
-scp ./* smartini@people.apache.org:~/public_html/pivot-2.0.2_maven/
+scp ./* smartini@people.apache.org:~/public_html/pivot-<release-number>_maven/
 currently it contains approx. 20 Mb of files.
 
 From the release folder, for example run:
-scp ./* smartini@people.apache.org:~/public_html/pivot-2.0.2_release/
+scp ./* smartini@people.apache.org:~/public_html/pivot-<release-number>_release/
 currently it contains approx. 60 Mb of files.
 
 Than, verify with a Web Browser that all stuff has been copied and published, for example from here: