THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
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.
incubator-streampipes-extensions
The next step is to prepare the extensions project for a release. The required steps are almost identical to the previous steps:
If needed, change the current SNAPSHOT version to the version that is planned for the upcoming release:
| Code Block | ||||
|---|---|---|---|---|
| ||||
# in incubator-streampipes-extensions
# 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
# Open the incubator-streampipes-extensions parent pom and change the parent version and the streampipes.version property to the SNAPSHOT version.
# Commit and 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
# In dev, update the streampipes.version property and the parent version to the next development version, e.g.:
<parent>
<groupId>org.apache.streampipes</groupId>
<artifactId>streampipes-parent</artifactId>
<version>0.67.0-SNAPSHOT</version>
</parent>
<streampipes.version>0.67.0-SNAPSHOT</streampipes.version>
# Commit and push all changes to dev |
Prepare test setup
| Anchor | ||||
|---|---|---|---|---|
|
...