-
Notifications
You must be signed in to change notification settings - Fork 117
Creating Releases With releasecandidate xml
aharui edited this page Jun 10, 2019
·
1 revision
Assuming you have set up properly, creating a release candidate involves:
- In an empty folder, set up your local.properties
- copy the latest releasecandidate.xml from royale-asjs
- Run from that folder:
ant -f releasecandidate.xml "-Drelease.version=x.y.z" -Drc=1 make_branches
- Run:
ant -f releasecandidate.xml "-Drelease.version=x.y.z" -Drc=1 maven
- 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
- 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.
- Run:
ant -f releasecandidate.xml "-Drelease.version=x.y.z" -Drc=1 release
Don't forget to run push --all in each repo folder
The released artifacts should end up on dist/release Don't delete the older release until the mirrors have caught up. If there is more than one older release in the royale folder, use "svn rm" to delete it.
You should also clean up the RC folders on dist/dev
- Draft the announcement. Wait 48 hours for feedback and mirror propagation before sending it. Check the mirrors by visiting https://www.apache.org/mirrors/ and making sure that there are few mirrors that have a "mirror age" older than when the bits were pushed to dist/release.
- Send the announcement.
Apache®, Apache Royale, Royale™, and the Royale logo are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries.