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 6ad95ac Updated Release Manager Notes (markdown)
6ad95ac is described below
commit 6ad95ac794566b09ccd30db6bb54d5702bc2f76e
Author: aharui <[email protected]>
AuthorDate: Thu Sep 20 16:54:15 2018 -0700
Updated Release Manager Notes (markdown)
---
Release-Manager-Notes.md | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Release-Manager-Notes.md b/Release-Manager-Notes.md
index 2a59e06..dc024b0 100644
--- a/Release-Manager-Notes.md
+++ b/Release-Manager-Notes.md
@@ -135,6 +135,10 @@ Use double blackslash on Windows and single forward slash
on Mac. Set the svn p
## Release Steps
+The release scripts assume that each of the 3 repos is properly versioned.
The scripts assume that the version numbers in certain files reflect the
version being released. The RM may need to verify that the following files
have the following versions:
+A) All pom.xml files have the SNAPSHOT version of the release. So if
releasing 0.9.4, then the pom.xml files should be version 0.9.4-SNAPSHOT.
There are some properties with versions in the pom.xml files that may need to
be upgraded to 0.9.4 as well.
+B) build.properties lists the correct version (without -SNAPSHOT).
+
Assuming you have set up properly, creating a release candidate involves:
1) In an empty folder, set up your local.properties
@@ -152,4 +156,3 @@ 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.
-
