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 c9c008e Updated Release Manager Notes (markdown)
c9c008e is described below
commit c9c008e4b9ef3165604fdaffc9b14410cced4825
Author: aharui <[email protected]>
AuthorDate: Tue Nov 13 03:27:08 2018 +0000
Updated Release Manager Notes (markdown)
---
Release-Manager-Notes.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Release-Manager-Notes.md b/Release-Manager-Notes.md
index 1548afa..fe43e98 100644
--- a/Release-Manager-Notes.md
+++ b/Release-Manager-Notes.md
@@ -172,9 +172,9 @@ And do the same in the release folder.
Set environment variable:
-`JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF8`
+`JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF-8`
-Next, 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).
+The "-" in UTF-8 is important. Sass will fail otherwise. Next, 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:
