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 a155d75 Updated Release Manager Notes (markdown)
a155d75 is described below
commit a155d75bafc4bacf0b223e999654da7973b39d0c
Author: aharui <[email protected]>
AuthorDate: Mon Jun 10 11:35:09 2019 -0700
Updated Release Manager Notes (markdown)
---
Release-Manager-Notes.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/Release-Manager-Notes.md b/Release-Manager-Notes.md
index 2affe28..a45e60b 100644
--- a/Release-Manager-Notes.md
+++ b/Release-Manager-Notes.md
@@ -270,6 +270,7 @@ Assuming you have set up properly, creating a release
candidate involves:
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.
+For details on each job see: [Release Steps Jobs on
Jenkins](Release-Steps-Jobs-On-Jenkins)
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`
