...
First, update the RELEASE_NOTES in incubator-streampipes (dev) by adding significant new features from JIRA that correspond to the new release version.Afterwards, create a new branch for the upcoming release candidate:
incubator-streampipes
If needed, change the current SNAPSHOT version to the version that is planned for the upcoming release:
Code Block | ||||
---|---|---|---|---|
| ||||
# Make sure to only use a SNAPSHOT version here
mvn versions:set -DnewVersion=0.66.0-SNAPSHOT
# Check the output and briefly check if all changed version numbers in the POM files are ok
mvn versions:commit
# Manually change the project version in the package.json file in the ui/ folder.
# Push the changes to dev |
Afterwards, create a new branch for the upcoming release candidate:
Code Block | ||||
---|---|---|---|---|
| ||||
# Create a release branch by replacing VERSION with the intended release version mvn release:branch -DbranchName=rel/VERSION -DautoVersionSubmodules=true |
The maven-release-plugin will ask you to provide the version number of the next development version (use the new minor version, not the suggested patch version). Afterwards, a new branch will be created and the version number in dev is increased to the next development version. All changes will be automatically pushed by the plugin.
Prepare test setup
Anchor | ||||
---|---|---|---|---|
|
...