[royale-asjs.wiki] branch master updated: Updated Task List For Royale Releases (markdown)

[ah...@apache.org]

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

aharui pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-asjs.wiki.git


The following commit(s) were added to refs/heads/master by this push:
     new 8252012  Updated Task List For Royale Releases (markdown)
8252012 is described below

commit 8252012d0ddbb1fbd965435658f23fa72c0d8e60
Author: aharui <ah...@apache.org>
AuthorDate: Wed Apr 1 20:58:50 2020 -0700

    Updated Task List For Royale Releases (markdown)
---
 Task-List-For-Royale-Releases.md | 20 ++++++++++++++++----
 1 file changed, 16 insertions(+), 4 deletions(-)

diff --git a/Task-List-For-Royale-Releases.md b/Task-List-For-Royale-Releases.md
index a340692..32c5f1e 100644
--- a/Task-List-For-Royale-Releases.md
+++ b/Task-List-For-Royale-Releases.md
@@ -3,7 +3,7 @@ The token:
 * `$rc` represents the current release candidate number.
 * 'mavenfoldernumber' represents the name of the staging repo folder on https://repository.apache.org 
 
-1. Determine if compiler-jburg-types or compiler-build-tools needs to be released.  If not skip to step 12.
+1. Determine if compiler-jburg-types or compiler-build-tools needs to be released.  If not skip to step 14.
 2. In royale-compiler/compiler-jburg-types and/or compiler-build-tools, run `mvn release:prepare -Dtag=org.apache.royale.compiler-build-tools-$releaseversion-rc$rc`
 3. Then run: `mvn release:perform`
 4. Using SVN, clone https://dist.apache.org/repos/dist/dev/royale
@@ -14,7 +14,19 @@ The token:
 9. Send an email with the subject [DISCUSS] Discuss Release Apache Royale Compiler Build Tools (note that the word Discuss is both in brackets and outside of brackets so that Gmail and other email clients separate the threads).
 10. Send an email with the subject [VOTE] Release Apache Royale Compiler Build Tools.
 11. When the vote passes:  Hit the "release" button at https://repository.apache.org
-12. Run `svn mv dev/royale/compiler-build-tools release/royale'
-13. Commit that change.
-14. 
+12. Run `svn mv dev/royale/compiler-build-tools release/royale`
+13. Commit 'svn commit`.
+14. In royale-compiler run `mvn -P option-with-swf release:branch -DautoVersionSubmodules=true -DbranchName=release/$releaseversion`
+15. `git checkout release/$releaseversion`
+16. `mvn -P option-with-swf release:prepare -DautoVersionSubmodules=true -Dtag=org.apache.royale.compiler-$releaseversion-rc$rc`
+17. `mvn release:perform`
+18. In royale-typedefs run `mvn -P option-with-swf release:branch -DautoVersionSubmodules=true -DbranchName=release/$releaseversion`
+19. `git checkout release/$releaseversion`
+20. `mvn -P option-with-swf release:prepare -DautoVersionSubmodules=true -Dtag=org.apache.royale.typedefs-$releaseversion-rc$rc`
+21. `mvn release:perform`
+22. In royale-asjs run `mvn -P with-distribution,with-examples,with-manualtests,option-with-swf release:branch -DautoVersionSubmodules=true -DbranchName=release/$releaseversion`
+23. `git checkout release/$releaseversion`
+24. `mvn -P with-distribution,with-examples,with-manualtests,option-with-swf release:prepare -DautoVersionSubmodules=true -Dtag=org.apache.royale.asjs-$releaseversion-rc$rc`
+25. `mvn release:perform`
+