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 bad8c93 Updated Release Manager Notes (markdown)
bad8c93 is described below
commit bad8c930de731f3df0bb76371cb01b30b3b4fd15
Author: aharui <[email protected]>
AuthorDate: Mon Oct 7 17:27:25 2019 -0700
Updated Release Manager Notes (markdown)
---
Release-Manager-Notes.md | 46 ++++++++++++++++++++++++++++------------------
1 file changed, 28 insertions(+), 18 deletions(-)
diff --git a/Release-Manager-Notes.md b/Release-Manager-Notes.md
index 7548101..c6a0f9c 100644
--- a/Release-Manager-Notes.md
+++ b/Release-Manager-Notes.md
@@ -93,7 +93,7 @@ Run "ant wipe" to remove all generated code. Then run:
This should result in lots of files having '0.9.4-SNAPSHOT' (and not just
"0.9.4"). The top-level pom.xml should have:
-'<royale.compiler.version>0.9.4-SNAPSHOT</royale.compiler.version>'
+`<royale.compiler.version>0.9.4-SNAPSHOT</royale.compiler.version>`
There shouldn't be any other files with that version in it.
@@ -109,15 +109,15 @@ No files should mention the newer version.
Run "ant super-clean" to remove all generated code. Then run:
-'grep -r '0\.9\.4' * | grep -v @productversion'
+`grep -r '0\.9\.4' * | grep -v @productversion`
The grep -v filters out any hits from ASDoc @productversion so it is easier to
see the build-related versions. This should result in lots of files having
'0.9.4-SNAPSHOT' (and not just "0.9.4"). The top-level pom.xml should have:
-'<royale.compiler.version>0.9.4-SNAPSHOT</royale.compiler.version>'
+`<royale.compiler.version>0.9.4-SNAPSHOT</royale.compiler.version>`
and
-'<royale.typedefs.version>0.9.4-SNAPSHOT</royale.typedefs.version>'
+`<royale.typedefs.version>0.9.4-SNAPSHOT</royale.typedefs.version>`
The following files will have just plain "0.9.4" in it:
@@ -200,13 +200,17 @@ and
For me, it was empty in GitBash but GPG4Win listed my keys. I found mykey ID
(looks like an 8 digit hexadecimal number) and used that as described below.
Per [this
link,](https://unix.stackexchange.com/questions/184947/how-to-import-secret-gpg-key-copied-from-one-machine-to-another)
I was able to use something like this in GPG4Win:
-`gpg --export ${ID} > public.key`
-`gpg --export-secret-key ${ID} > private.key`
+```
+gpg --export ${ID} > public.key
+gpg --export-secret-key ${ID} > private.key
+```
And then import in GitBash via:
-`gpg --import < public.key`
-`gpg --import < private.key`
+```
+gpg --import < public.key
+gpg --import < private.key
+```
Then to build an RC, open a command prompt and run start-ssh-agent. Then you
should be able to run the releasecandidate.xml scripts.
@@ -220,7 +224,7 @@ I first had to set the MAVEN_OPTS environment variable to
make sure there is eno
Then, I opened a Powershell window and ran:
-'"C:\Program Files\Git\cmd\start-ssh-agent.cmd"'
+`"C:\Program Files\Git\cmd\start-ssh-agent.cmd"`
For some reason, that causes the Powershell command to go away. I think
start-ssh-agent runs a command prompt shell afterwards instead of Powershell,
so that means that Powershell features go away.
@@ -228,15 +232,19 @@ Note (November 11, 2018): The above did not work for me.
The internet says tha
In c:\Users\<username>\.gitconfig, add:
-`[core]`
-` sshcommand = c:/Windows/System32/OpenSSH/ssh.exe`
+```
+[core]
+sshcommand = c:/Windows/System32/OpenSSH/ssh.exe
+```
Then in the Window "Services" app, I found OpenSSH Authentication service was
disabled. I right-clicked on the word "disabled" and changed "disabled" to
Manual".
Then in Powershell, I ran:
-`Start-Service ssh-agent`
-`ssh-add C:\Users\<username>\.ssh\id_rsa`
+```
+Start-Service ssh-agent
+ssh-add C:\Users\<username>\.ssh\id_rsa
+```
This asked me for the passphrase for the key.
@@ -246,17 +254,19 @@ Then test ssh by making a small commit (I changed
royale-compiler GIT-TEST.txt)
Because Powershell limits to 9999 lines of console output and the build spits
out many more lines than that, having Powershell fork output to a file is
useful. So I would launch another Powershell window and run Ant in there, but
pipe the output to a file via:
-'ant -f releasecandidate.xml <options> | Tee-Object -file <path to log>'
+`ant -f releasecandidate.xml <options> | Tee-Object -file <path to log>`
## local.properties
It is recommended to create releases in a separate folder than your Git
working copies. Create an empty folder and create in it a local.properties
file. In local.properties, set:
-'my.name=Alex Harui'
+```
+my.name=Alex Harui
-'svn.dist.dev=C:\\svn\\apache\\dist\\dev'
-'svn.dist.release=C:\\svn\\apache\\dist\\release'
-'svn=C:\\Program Files\\CollabNet\\Subversion Client\\svn.exe'
+svn.dist.dev=C:\\svn\\apache\\dist\\dev
+svn.dist.release=C:\\svn\\apache\\dist\\release
+svn=C:\\Program Files\\CollabNet\\Subversion Client\\svn.exe
+```
Use double blackslash on Windows and single forward slash on Mac. Set the svn
properties to the appropriate folders in dist.apache.org
