Repository: systemml
Updated Branches:
  refs/heads/master 723acfc09 -> 4ea1d5324


[MINOR] Add step for compiling release verification code


Project: http://git-wip-us.apache.org/repos/asf/systemml/repo
Commit: http://git-wip-us.apache.org/repos/asf/systemml/commit/4ea1d532
Tree: http://git-wip-us.apache.org/repos/asf/systemml/tree/4ea1d532
Diff: http://git-wip-us.apache.org/repos/asf/systemml/diff/4ea1d532

Branch: refs/heads/master
Commit: 4ea1d5324654f159c86847a471241894e23153fb
Parents: 723acfc
Author: Glenn Weidner <gweid...@us.ibm.com>
Authored: Fri Nov 24 10:30:58 2017 -0800
Committer: Glenn Weidner <gweid...@us.ibm.com>
Committed: Fri Nov 24 10:30:58 2017 -0800

----------------------------------------------------------------------
 docs/release-creation-process.md | 40 ++++++++++++++++++++---------------
 1 file changed, 23 insertions(+), 17 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/systemml/blob/4ea1d532/docs/release-creation-process.md
----------------------------------------------------------------------
diff --git a/docs/release-creation-process.md b/docs/release-creation-process.md
index edde97e..3115390 100644
--- a/docs/release-creation-process.md
+++ b/docs/release-creation-process.md
@@ -33,12 +33,12 @@ Prerequisite: [Project release 
guidelines](https://github.com/SparkTC/developmen
 
 Tips to prepare and release the build
 
-Step 0.        Minimum changes and verification to be done before release 
build process starts.
+Step 0: Minimum changes and verification to be done before release build 
process starts.
 
        1. ReadMe update and “Must Fix” changes are already in.
        2. Performance Test is passing for dataset size of 80GB and below.
 
-Step 1: Prepare the release
+Step 1: Prepare the release.
 
        # Extract latest code to a directory
        <GitRepoHome>
@@ -46,7 +46,7 @@ Step 1: Prepare the release
        # Go to dev/release directory
        cd <GitRepoHome>/dev/release
 
-  1.a. Dry Run (This is trial build, will not commit anything in repository)
+  1.a. Dry Run (this is trial build, will not commit anything in repository).
 
        e.g. (On Master branch with release candidate rc1, release version 
0.15.0, and next development version 1.0.0-SNAPSHOT)
        ./release-build.sh --release-prepare --releaseVersion="0.15.0" 
--developmentVersion="1.0.0-SNAPSHOT" --releaseRc="rc1" --tag="v0.15.0-rc1" 
--dryRun
@@ -55,43 +55,49 @@ Step 1: Prepare the release
        ./release-build.sh --release-prepare --releaseVersion="0.15.0" 
--developmentVersion="0.15.1-SNAPSHOT" --releaseRc="rc2" --tag="v0.15.0-rc2"  
--gitCommitHash="branch-0.15" --dryRun
 
 
-  1.b. License verification<br>
+  1.b. Compile release verification code.
+
+       ./release-verify.sh --compile
+
+  1.c. Run license verification.
+
        ./release-verify.sh --verifyLic
 
-  1.c. Run command to do release prepare step (This will commit changes to the 
repository)  
-       This is same as step 1.a, without —dryRun option.<br>
+  1.d. Run command to do release prepare step (this will commit changes to the 
repository).  
+       This is same as step 1.a, without —dryRun option.
+
        e.g. (On the Master branch)<br>
        ./release-build.sh --release-prepare --releaseVersion="0.15.0" 
--developmentVersion="1.0.0-SNAPSHOT" --releaseRc="rc1" --tag="v0.15.0-rc1"
 
        e.g. (On the branch-0.15 branch)
        ./release-build.sh --release-prepare --releaseVersion="0.15.0" 
--developmentVersion="0.15.1-SNAPSHOT" --releaseRc="rc2" --tag="v0.15.0-rc2"  
--gitCommitHash="branch-0.15"
 
-  1.d Verify the release<br>
+  1.e. Verify the release.<br>
        This will verify release on Mac Operating System (OS), assuming these 
steps are run on Mac OS. It will verify licenses, notice and all other required 
verification only on Mac OS.
        Verification of licenses and notice is required only on one platform.
 
        ./release-verify.sh --verifyAll
 
 
-Step 2: Publish the release
+Step 2: Publish the release.
 
        e.g.
        ./release-build.sh --release-publish --gitTag="v0.15.0-rc1"
 
 
-Step 3: Close the release candidate build on Nexus site
+Step 3: Close the release candidate build on Nexus site.
 
 Visit [NexusRepository](https://repository.apache.org/#stagingRepositories) 
site.
 
-       Find out SystemML under (Staging Repositories) link. It should be in 
Open State (status). Close it (button on top left to middle) with proper 
comment.
-       Once it completes copying, URL will be updated with maven location to 
be sent in mail.
+       Find out SystemML under (Staging Repositories) link. It should be in 
Open State (status). Close it (button on top left to middle) with proper 
comment. Once it completes copying, URL will be updated with maven location to 
be sent in mail.
 
-Step 4. Send mail for voting (dev PMC) (d...@systemml.apache.org)
+Step 4: Send mail for voting (dev PMC d...@systemml.apache.org).
 
 Please check [Project release 
guidelines](https://github.com/SparkTC/development-guidelines/blob/master/project-release-guidelines.md)
 or previous mail thread for format/content of the mail.
 
 Step 5: Create a branch based on release to be released.
+
        # Create a branch based on TAG
        Syntax: git branch <branch name> <Tag Name>
        e.g.    git branch branch-0.15 v0.15.0-rc1
@@ -106,7 +112,7 @@ Step 6: If there is failure to get votes then address 
issues and repeat from ste
 
 Step 7: If release has been approved, then make it available for general use 
for everyone.
 
-       7.a     Move distribution from dev to release (Run following commands 
from command line)
+       7.a. Move distribution from dev to release (run following commands from 
command line).
 
        
RELEASE_STAGING_LOCATION="https://dist.apache.org/repos/dist/dev/systemml/";
        
RELEASE_STAGING_LOCATION2="https://dist.apache.org/repos/dist/release/systemml/";
@@ -115,7 +121,7 @@ Step 7: If release has been approved, then make it 
available for general use for
        svn move -m "Move SystemML 0.15 from dev to release" 
$RELEASE_STAGING_LOCATION/0.15.0-rc2  $RELEASE_STAGING_LOCATION2/0.15.0
 
 
-       7.b     Move Nexus data from dev to release
+       7.b. Move Nexus data from dev to release.
        Visit following site and identify release sent for voting in step 3 
above. It would be in “closed” state (status).
 
        https://repository.apache.org/#stagingRepositories
@@ -124,12 +130,12 @@ Step 7: If release has been approved, then make it 
available for general use for
 
        Note: Release candidates which were not approved can be dropped by 
clicking “drop” button from top middle of the screen.
 
-       7.c Update pypi from following site (Request someone who has the access)
+       7.c. Update pypi from following site (request someone who has the 
access).
        https://pypi.python.org/pypi/systemml/
 
-       7.d Update documents and release notes
+       7.d. Update documents and release notes.
 
-       7.e Send ANNOUNCE NOTE
+       7.e. Send ANNOUNCE NOTE.
        To:  d...@systemml.apache.org  annou...@apache.org
        Subject e.g.
        [ANNOUNCE] Apache SystemML 0.15.0 released.

Reply via email to