THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Info |
|---|
This is based on the release guide of the Apache Beam project: https://beam.apache.org/contribute/release-guide/ |
Change release type:
...
| flag | version_switch |
|---|
...
...
| notflag | version_switch |
|---|
...
| Table of Contents |
|---|
Introduction
...
Most of the following commands have to be executed in the tools directory, we will prefix the command prompt to make this explicit.
...
| flag | version_switch |
|---|
...
If you are doing a new major/minor release, first create a branch for the new version that we want to release before updating the master branch to the next development version:
| Code Blockpanel-show | ||
|---|---|---|
| ||
| ||
| ||
$ git checkout -b release-$SHORT_RELEASE_VERSION
$ git checkout master
$ cd tools
tools $ OLD_VERSION=$CURRENT_SNAPSHOT_VERSION NEW_VERSION=$NEXT_SNAPSHOT_VERSION releasing/update_branch_version.sh
$ cd ..
$ git checkout -b release-$SHORT_RELEASE_VERSION |
If you're creating a new bugfix release, you will skip the above step and simply check out the the already existing branch for that version:
| Code Block | ||
|---|---|---|
| ||
$ git checkout -b release-$SHORT_RELEASE_VERSION |
The rest of this guide assumes that commands are run in the root (or tools directory) of a repository on the branch of the release version with the above environment variables set.
...