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 9eda4c8 Updated Release Manager Notes (markdown)
9eda4c8 is described below
commit 9eda4c804ad321e6e17e4c709455a0b2229d5907
Author: aharui <[email protected]>
AuthorDate: Mon Jun 10 11:31:36 2019 -0700
Updated Release Manager Notes (markdown)
---
Release-Manager-Notes.md | 17 ++++++-----------
1 file changed, 6 insertions(+), 11 deletions(-)
diff --git a/Release-Manager-Notes.md b/Release-Manager-Notes.md
index 35b4765..bed3045 100644
--- a/Release-Manager-Notes.md
+++ b/Release-Manager-Notes.md
@@ -268,16 +268,11 @@ Also make sure that your SVN repos for dist/dev/Royale
are updated without confl
Assuming you have set up properly, creating a release candidate involves:
-1) In an empty folder, set up your local.properties
-2) copy the latest releasecandidate.xml from royale-asjs
-3) Run from that folder: `ant -f releasecandidate.xml
"-Drelease.version=x.y.z" -Drc=1 make_branches`
-4) Run: `ant -f releasecandidate.xml "-Drelease.version=x.y.z" -Drc=1 maven`
-5) Run: `ant -f releasecandidate.xml "-Drelease.version=x.y.z" -Drc=1`
+1) Run each [Release Steps job on the CI
Server](http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/Royale%20Release/)
in order. As each job completes, it will send an email to
[email protected] explaining what to do next. The final steps should
generate the packages and set up emails to send to the list for vote and
discussion.
-Step 5 should generate the packages and set up emails to send to the list for
vote and discussion. When the vote passes, do
-
-6) Verify that your SVN is up to date. Do an "svn status" on dist/dev and
dist/release. If you have non-Royale folders, they must be up to date
otherwise the svn commit will fail.
-7) Run: `ant -f releasecandidate.xml "-Drelease.version=x.y.z" -Drc=1 release`
+When the vote passes, do
+1) Verify that your SVN is up to date. Do an "svn status" on dist/dev and
dist/release. If you have non-Royale folders, they must be up to date
otherwise the svn commit will fail.
+2) Run: `ant -f releasecandidate.xml "-Drelease.version=x.y.z" -Drc=1 release`
Don't forget to run push --all in each repo folder
The released artifacts should end up on
[dist/release](https://dist.apache.org/repos/dist/release/royale/)
@@ -285,8 +280,8 @@ Don't delete the older release until the mirrors have
caught up. If there is mo
You should also clean up the RC folders on
[dist/dev](https://dist.apache.org/repos/dist/dev/royale/)
-8) Draft the announcement. Wait 48 hours for feedback and mirror propagation
before sending it. Check the mirrors by visiting
[https://www.apache.org/mirrors/](https://www.apache.org/mirrors/) and making
sure that there are few mirrors that have a "mirror age" older than when the
bits were pushed to dist/release.
-9) Send the announcement.
+3) Draft the announcement. Wait 48 hours for feedback and mirror propagation
before sending it. Check the mirrors by visiting
[https://www.apache.org/mirrors/](https://www.apache.org/mirrors/) and making
sure that there are few mirrors that have a "mirror age" older than when the
bits were pushed to dist/release.
+4) Send the announcement.
If you see this error:
```
