-
Notifications
You must be signed in to change notification settings - Fork 134
Release Steps
Aécio Santos edited this page Jan 18, 2020
·
1 revision
This document describes the steps for releasing new versions of this project.
- Make sure that all changes have been committed and the repository is clean.
- Change the version tag numbers using the command:
./set_version <version>-SNAPSHOT <version>
- Update
CHANGELOG.md
file with the release date. - Commit changes with commit message "Released version <version>":
git commit -m "Released version <version>"
- Create a new git tag named <version>. The git tag should include only the version number without the
v
prefix. - Make sure to push the changes to the Git repository (including the new tag).
- Create the release on the GitHub releases page. Make sure to associate the release with the tag created for the new version.
- Change version numbers to the next version number:
./set_version <version> <next-version>-SNAPSHOT
- Update
CHANGELOG.md
file creating space for the next version's changes - Commit changes files with the message: "Preparing for the next development cycle: <next-version>-SNAPSHOT"
git commit -m "Preparing for the next development cycle: <next-version>-SNAPSHOT"
- Push the changes to the Git repository