[royale-asjs.wiki] branch master updated: Updated Release Manager Notes (markdown)

[ah...@apache.org]

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 d12eb62  Updated Release Manager Notes (markdown)
d12eb62 is described below

commit d12eb62b1a3539bc8186e146f92de34b6a994a1e
Author: aharui <ah...@apache.org>
AuthorDate: Tue Dec 4 18:35:54 2018 -0800

    Updated Release Manager Notes (markdown)
---
 Release-Manager-Notes.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Release-Manager-Notes.md b/Release-Manager-Notes.md
index 1b92409..96f8570 100644
--- a/Release-Manager-Notes.md
+++ b/Release-Manager-Notes.md
@@ -270,7 +270,8 @@ Assuming you have set up properly, creating a release candidate involves:
 
 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) Run: `ant -f releasecandidate.xml "-Drelease.version=x.y.z" -Drc=1 release`
+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`
 Don't forget to run push --all in each repo folder
 
 Step 6 should tell you to run step 7.