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 7f09173 Updated Release Manager Notes (markdown)
7f09173 is described below
commit 7f091739a73bd464b4b313485dea1ff8226560b3
Author: aharui <[email protected]>
AuthorDate: Thu Jan 18 11:57:13 2018 -0800
Updated Release Manager Notes (markdown)
---
Release-Manager-Notes.md | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Release-Manager-Notes.md b/Release-Manager-Notes.md
index 002ad09..6d4be34 100644
--- a/Release-Manager-Notes.md
+++ b/Release-Manager-Notes.md
@@ -34,3 +34,7 @@ Revert these entries via "git revert <hash of commit>"
Do the above for all 3 repos. Then you can accept the changes to the release
branch and run the "maven" step again. Note that you should not merge the
develop branch into the release branch because Maven has already updated the
develop branch to the next release version.
Next, go find the staging repository for Royale in the [Apache
Nexus](https://repository.apache.org/#stagingRepositories). In the left
navigator choose "Staging Repositories", find "orgapacheroyale" in the top
right list, select the checkbox, and click on the "Drop" button. Wait a few
seconds then refresh the page and it should be gone.
+
+## 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 [...]
--
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].
