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 a179230  Updated Release Manager Notes (markdown)
a179230 is described below

commit a17923043cc93d4855e2d829d9fe952c5463f54c
Author: aharui <aha...@apache.org>
AuthorDate: Mon Mar 12 04:31:25 2018 +0000

    Updated Release Manager Notes (markdown)
---
 Release-Manager-Notes.md | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/Release-Manager-Notes.md b/Release-Manager-Notes.md
index 137fdbc..392d895 100644
--- a/Release-Manager-Notes.md
+++ b/Release-Manager-Notes.md
@@ -1,4 +1,4 @@
-Royale releases will consist of the bundling of all 3 repos (royale-compiler, 
royale-typedefs, royale-asjs) into a single source artifact, as well as 
convenience binaries of Maven artifacts, NPM artifacts and IDE-compatible 
artifacts.
+iRoyale releases will consist of the bundling of all 3 repos (royale-compiler, 
royale-typedefs, royale-asjs) into a single source artifact, as well as 
convenience binaries of Maven artifacts, NPM artifacts and IDE-compatible 
artifacts.
 
 The release manager must be able to run Maven and Ant and have an Adobe AIR 
SDK and Adobe Flash SDK (playerglobal.swc and Flash Projector Content Debugger) 
installed, and environment variables set up.
 
@@ -41,9 +41,10 @@ Some times, during the creation of an RC, you'll see 
something you want to chang
 
 ## Using Windows
 
-I was unable to use the command prompt in Windows to create a release 
candidate.  Instead, I had to use GitBash.  I did not try Cygwin yet.  I had to 
use GitBash in order to follow the instructions for setting up SSH to GitHub.  
Here's the 
[link](https://help.github.com/articles/checking-for-existing-ssh-keys/).  Note 
the part about setting up a key-agent 
[here](https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#adding-your-ssh-key-to-the-ssh-agent)
 [...]
+First, make sure you are set up to use SSH for GitHub by following this 
[link](https://help.github.com/articles/checking-for-existing-ssh-keys/).  You 
may need to use Git-Bash to execute the the part about setting up a key-agent 
[here](https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#adding-your-ssh-key-to-the-ssh-agent).
+
+Even though you can use GPG4Win to sign releases from the command prompt, 
Maven might try to use GitBash's gpg which has a different keystore, and 
signing will fail.  If you run into this, export your keys with GPG4Win and 
import them in GitBash's GPG.  Use GitBash to verify if your key is in the 
keystore via:
 
-However, even though I was using GPG4Win to sign Flex releases, GitBash seemed 
to run its own gpg with a different keystore, so signing failed.  I had to 
export my keys with GPG4Win and import them in GitBash's GPG.  Use GitBash to 
verify if your key is in the keystore via:
 `gpg --list-keys`
 
 and
@@ -60,6 +61,4 @@ And then import in GitBash via:
 `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.

-- 
To stop receiving notification emails like this one, please contact
aha...@apache.org.

Reply via email to