[portals-pluto] branch master updated: PLUTO-777 Release Preparation 3.1.0 (Updates to the release procedure)

[as...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

asfgriff pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/portals-pluto.git


The following commit(s) were added to refs/heads/master by this push:
     new 16fd8f7  PLUTO-777 Release Preparation 3.1.0 (Updates to the release procedure)
16fd8f7 is described below

commit 16fd8f72537032592bc3a076915a7b3fd4d8e9ca
Author: Neil Griffin <ne...@gmail.com>
AuthorDate: Thu Apr 11 18:33:58 2019 -0400

    PLUTO-777 Release Preparation 3.1.0 (Updates to the release procedure)
---
 RELEASE-PROCEDURE.txt | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/RELEASE-PROCEDURE.txt b/RELEASE-PROCEDURE.txt
index 1e41521..1a69c91 100644
--- a/RELEASE-PROCEDURE.txt
+++ b/RELEASE-PROCEDURE.txt
@@ -57,7 +57,7 @@ Since 3.0.0
 4. DRY RUN
 	Do a dry run of the release:prepare step:
 
-		$ mvn -P apache-release -DrunOnlyAtExecutionRoot=true release:prepare -DdryRun=true
+		$ mvn -P apache-release,pluto -DrunOnlyAtExecutionRoot=true release:prepare -DdryRun=true
 
 	The dry run will not commit any changes back to Git and gives you the opportunity to verify that the release process will complete as expected.
 	You will be prompted for the following information :
@@ -84,12 +84,12 @@ Since 3.0.0
 6. CLEANUP AND START OVER
 	Cleanup the release prepare files again:
 
-	$ mvn -P apache-release release:clean
+	$ mvn -P apache-release,pluto release:clean
 
 7. PREPARE THE RELEASE
 	Run the "release:prepare" step for real this time. You'll be prompted for the same version information.
 
-	$ mvn -P apache-release release:prepare -DrunOnlyAtExecutionRoot=true
+	$ mvn -P apache-release,pluto release:prepare -DrunOnlyAtExecutionRoot=true
 
 	Backup (zip or tar) your local release candidate directory in case you need to rollback the release after the next step is performed.
 
@@ -108,7 +108,7 @@ Since 3.0.0
 	b. REQUIRED: Release the main Apache Pluto software modules
 
 	$ cd portals-pluto
-	$ mvn -P apache-release release:perform -Duser.name=[your_apache_uid]
+	$ mvn -P apache-release,pluto release:perform -Duser.name=[your_apache_uid]
 	$ vi portlet-tck_3.0/pom.xml # Update the parent <version/> and also the version in the <pluto.test.version/> property
 	$ git commit -m "Upgraded the TCK to Pluto test version x.y.z"
 
@@ -123,8 +123,8 @@ Since 3.0.0
 	      the portlet-tck_3.0/pom.xml and TCK sub-module POM descriptors.
 
 	$ cd portals-pluto/portlet-tck_3.0
-	$ mvn -P apache-release release:prepare -DrunOnlyAtExecutionRoot=true
-	$ mvn -P apache-release release:perform -Duser.name=[your_apache_uid]
+	$ mvn -P apache-release,pluto release:prepare -DrunOnlyAtExecutionRoot=true
+	$ mvn -P apache-release,pluto release:perform -Duser.name=[your_apache_uid]
 
 	d. OPTIONAL: Release the Archetypes (Each has its own version scheme and release schedule)