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 df30b6b Updated Release Manager Notes (markdown) df30b6b is described below commit df30b6b1a19b40cc39c7630995a88a9ce7c37a9d Author: aharui <aha...@apache.org> AuthorDate: Mon Mar 12 04:51:00 2018 +0000 Updated Release Manager Notes (markdown) --- Release-Manager-Notes.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/Release-Manager-Notes.md b/Release-Manager-Notes.md index 392d895..a2595e5 100644 --- a/Release-Manager-Notes.md +++ b/Release-Manager-Notes.md @@ -1,4 +1,4 @@ -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. +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. 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. @@ -39,6 +39,23 @@ Next, go find the staging repository for Royale in the [Apache Nexus](https://re 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 [...] +## Other setup + +Make sure you have a settings.xml in your .m2 folder that has credentials for deploying artifacts to repository.apache.org. You should have entries like: + +`<servers>` + `<server>` + `<id>apache.releases.https</id>` + `<username>...</username>` + `<password>...</password>` + `</server>` + `<server>` + `<id>apache.snapshots.https</id>` + `<username>...</username>` + `<password>...</password>` + `</server>` +`</servers>` + ## Using Windows 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). -- To stop receiving notification emails like this one, please contact aha...@apache.org.