1. Disable NordVPN (some tests call actual servers and they don't work the same way behind VPN)
2. Update changelog with the date of the new release
3. Switch to JDK 8
4. Run ./mvn_release.sh and follow the instructions.
   • If build fails because of missing dependencies do:
     1. mvn install -Prelease,dist
     2. mvn release:prepare -Prelease,dist -Dresume
     3. mvn release:perform -Prelease,dist
5. Upload the artifacts to bintray.
   1. Run the ./deploy_bintray.sh script and enter the API Key (found on Bintray on the user profile page when pressing the edit button) and version to release.
   2. Login to bintray and add release notes and publish the release.
6. Generate javadoc by running the ./generate_javadoc.sh script and enter the version to release
7. Update the wiki by running the ./update_wiki.sh script and enter the previous version and the new version to release. This will clone the wiki from GitHub and replace old version to new version on all pages. Afterwards you have the script offers you to commit and push the changes. If you want to avoid having to enter the github username and password each time see this page.
8. Fix snapshot version number in https://github.com/rest-assured/rest-assured/wiki/snapshot
9. Update the README.md file to indicate that a new version was released
10. Send a message to the mailing-list and twitter announcing the new release.

The release is automatically synced to Maven central (the sync process runs hourly).

1. Disable NordVPN (some tests call actual servers and they don't work the same way behind VPN)
2. Switch to JDK 8
3. Create a branch, e.g. if you want to release version 5.3.1, call it e.g. rest-assured-5.3.1-code. The reason for not calling it rest-assured-5.3.1 is that a tag will be generated with that name.
4. Edit pom.xml and change SCM branch to rest-assured-5.3.1-code.
5. Make the changes you want to make and then run ./mvn_release.sh as normally.
6. You can now remove the local branch: git br -D rest-assured-5.3.1-code
7. You can now remove the remote branch: git push origin :rest-assured-5.3.1-code
8. Update changelog.txt and README.md in master branch.
9. Send email and twitter message if deemed appropriate