-
Notifications
You must be signed in to change notification settings - Fork 2
Release
Casper Thule edited this page May 22, 2019
·
1 revision
To release Crescendo the following shall be carried out in the development branch:
- Update Overture.release.properties in
<root>to match the new versions. - If Overture has been updated then update Overture Version in
<root>/pom.xml. Example - If Overture has been updated AND uses a new version of eclipse then update the eclipse version in:
<root>/ide/pom.xml. Example - Updated update sites in
ide/platform/p2.inf. (TBD) - Push to
development - Verify that Jenkins builds it
- Run the script
perform_release.sh. - This will create a tag with
Release/<new version> - Merge this tag into
master - Push
master. - Download binaries after Jenkins has finished at: http://overture.au.dk/crescendo/ e.g. http://overture.au.dk/crescendo/master/Build-6_2018-11-22_11-51/
- Create release on github with binaries and notes.