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 22046a8 Updated Release Manager Notes (markdown)
22046a8 is described below
commit 22046a807efb519ac620bbfe6fecff5cf93dd8ab
Author: aharui <[email protected]>
AuthorDate: Sun Mar 11 06:50:02 2018 +0000
Updated Release Manager Notes (markdown)
---
Release-Manager-Notes.md | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/Release-Manager-Notes.md b/Release-Manager-Notes.md
index 6d4be34..137fdbc 100644
--- a/Release-Manager-Notes.md
+++ b/Release-Manager-Notes.md
@@ -38,3 +38,28 @@ Next, go find the staging repository for Royale in the
[Apache Nexus](https://re
## Fixing an RC
Some times, during the creation of an RC, you'll see something you want to
change before you tell everyone to start examining the RC. In order to use the
"maven" step again, you will have to undo things as described in "Canceling an
RC", but also remove any tags in Git that the "maven" step created. Make sure
the repos are synced up and then on each of the 3 repos do "git tag" to list
the tags. Look for the tag for that RC. It will look like
"org.apache.royale.compiler-0.9.0-rc2" (o [...]
+
+## 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)
[...]
+
+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
+
+`gpg --list-secret-keys`
+
+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`
+
+And then import in GitBash via:
+
+`gpg --import > public.key`
+`gpg --import > private.key`
+
+
+
+
--
To stop receiving notification emails like this one, please contact
[email protected].
