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 2a78f85 Updated Release Manager Notes (markdown)
2a78f85 is described below
commit 2a78f85fad2cdf2008f551a9c2fcf7dfd2b26147
Author: aharui <[email protected]>
AuthorDate: Fri Mar 16 19:20:14 2018 +0000
Updated Release Manager Notes (markdown)
---
Release-Manager-Notes.md | 50 +++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 49 insertions(+), 1 deletion(-)
diff --git a/Release-Manager-Notes.md b/Release-Manager-Notes.md
index 39629c6..e5eaef0 100644
--- a/Release-Manager-Notes.md
+++ b/Release-Manager-Notes.md
@@ -60,6 +60,21 @@ Make sure you have a settings.xml in your .m2 folder that
has credentials for de
Releases are staged and distributed on SVN at dist.apache.org. EVERY ASF
release is there so don't sync the entire repo. Instead do partial checkouts
of just the Royale folder in dev/Royale and release/Royale.
+To get dist.apache.org, use:
+
+`svn co --depth empty https://dist.apache.org/repos/dist <destination-folder>`
+
+Then change to that folder and do:
+
+'svn update --depth empty dev'
+'svn update --depth empty release'
+
+That should introduce dev and release folders under dist. Then change to the
dev folder and do:
+
+'svn update Royale'
+
+And do the same in the release folder.
+
## Using Windows
Set environment variable:
@@ -86,4 +101,37 @@ And then import in GitBash via:
`gpg --import > public.key`
`gpg --import > private.key`
-Then to build an RC, open a command prompt and run start-ssh-agent. Then you
should be able to run the releasecandidate.xml scripts.
\ No newline at end of file
+Then to build an RC, open a command prompt and run start-ssh-agent. Then you
should be able to run the releasecandidate.xml scripts.
+
+## local.properties
+
+It is recommended to create releases in a separate folder than your Git
working copies. Create an empty folder and create in it a local.properties
file. In local.properties, set:
+
+'my.name=Alex Harui'
+
+'svn.dist.dev=C:\\svn\\apache\\dist\\dev'
+'svn.dist.release=C:\\svn\\apache\\dist\\release'
+'svn=C:\\Program Files\\CollabNet\\Subversion Client\\svn.exe'
+
+Use double blackslash on Windows and single forward slash on Mac. Set the svn
properties to the appropriate folders in dist.apache.org
+
+## Release Steps
+
+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`
+
+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`
+Don't forget to run push --all in each repo folder
+
+Step 6 should tell you to run step 7.
+7) Run: `ant -f releasecandidate.xml -Drelease.version=x.y.z -Drc=1
release.npm`
+8) Draft the announcement. Wait 48 hours for feedback and mirror propagation
before sending it.
+9) Send the announcement.
+
--
To stop receiving notification emails like this one, please contact
[email protected].
