Release Instructions

To release Gradle:

Before releasing

1. Review all JIRA issues for the release version, and either close them or move them to another version.
2. Create a Wiki page with the release notes. The Wiki page should embed a Jira query to the fixed issues.
3. Checkout the branch which the release will happen from: git checkout master
4. Create a text version of the Jira release notes, add it to the src/changelog.txt file
5. Update the version info in the gradle.properties file so that nextVersion is set to the version you wish to release. so that nextVersion is set to the version you wish to release.
6. Build a test version of the release artifacts: gradlew clean releaseArtifacts install
7. You might do some verification:
   1. Try running the CI build with the test version: gradle cibuild
   2. Check that the builds for some open source projects which use Gradle continue to work with the test version
   3. Upload the latest website using gradlew -u -p website clean uploadLatestWebsite and test it out at http://www.gradle.org/latest/
8. Update the example output of gradle -v in src/docs/userguide/installation.xml
9. Commit any changes

To build the release

1. Execute ./gradlew clean release
2. Smoke test the uploaded distributions and documentation
3. Change to the gradle website project and execute gradle -u -u clean uploadWebsite. This will update all the links on the website.
4. Update the version info in the gradle.properties file so that previousVersion is set to the version you just released. Commit changes.
5. Push to GitHub: git push origin master, git push origin RB_version and git push origin tag REL_version

After the release

1. Update gradle.properties to reflect the next planned release.
2. Update the wrapper to use the released version.
3. Update the branch used by the release branch builds on teamcity.
4. Update the roadmap.
5. Update Jira: Mark the released version as released. Add a new revision version for the release version.
6. Send an announcement email to the Gradle and Groovy mailing lists, add the announcement also to the Gradle news. Announce it also on the GradleOrg twitter channel.
7. You might update CrossVersionCompatibilityIntegrationTest.