This is an automated email from the ASF dual-hosted git repository.
bigosmallm 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 1a9115c Updated Release Manager Notes (markdown)
1a9115c is described below
commit 1a9115c8e4275cdd74d5ee57d3a92c879af114d9
Author: bigosmallm <[email protected]>
AuthorDate: Sat Sep 29 23:23:42 2018 -0700
Updated Release Manager Notes (markdown)
---
Release-Manager-Notes.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Release-Manager-Notes.md b/Release-Manager-Notes.md
index dc024b0..72fbe46 100644
--- a/Release-Manager-Notes.md
+++ b/Release-Manager-Notes.md
@@ -144,7 +144,7 @@ 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'
+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`
Step 5 should generate the packages and set up emails to send to the list for
vote and discussion. When the vote passes, do