[royale-asjs.wiki] branch master updated: instructions for the special case of releasing tools/jburg projects

[ca...@apache.org]

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

carlosrovira 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 1a3a469  instructions for the special case of releasing tools/jburg projects
1a3a469 is described below

commit 1a3a46907c0098b18d2adb46938b097881f5f12b
Author: Carlos Rovira <ca...@apache.org>
AuthorDate: Fri Mar 27 20:19:44 2020 +0100

    instructions for the special case of releasing tools/jburg projects
---
 Release-Manager-(New-to-be-tested).md | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/Release-Manager-(New-to-be-tested).md b/Release-Manager-(New-to-be-tested).md
index 5437a9d..d48557d 100644
--- a/Release-Manager-(New-to-be-tested).md
+++ b/Release-Manager-(New-to-be-tested).md
@@ -6,6 +6,35 @@ prepare
 export FLASHPLAYER_DEBUGGER="/Users/some-username/Devtools/Adobe/Flash/FlashPlayer-32.0/Flash Player.app/Contents/MacOS/Flash Player Debugger"
 ```
 
+If you see this error: 
+```
+gpg: signing failed: Inappropriate ioctl for device
+```
+
+Run first: 
+```
+export GPG_TTY=$(tty)
+```
+
+### Optional (Release of Tools projects)
+
+In case you need to release compiler-build-tools and compiler-jburg-types:
+
+1. Ensure version in each tool is a SNAPSHOT
+2. Go to each folder and run
+ - mvn release:prepare
+ - mvn release:perform
+
+Then start a VOTE and DISCUSSION threads to approve the release.
+As the vote passes update versions in `royale-compiler` pom.xml to the new version:
+
+```
+<compiler-build-tools.version>1.2.0</compiler-build-tools.version>
+<compiler-jburg-types.version>1.2.0</compiler-jburg-types.version>
+```
+
+Now you can start the release:
+
 ## Release Compiler
 
 ### Branch