...

Bump up version

...

and create tag

...

There are several places you need to bump up version before creating tag:

• Maven build: every pom.xml
• Docs: in docs/_config.yml update ZEPPELIN_VERSION, BASE_PATH, interpreter installation doc
• Configuration file: conf/interpreter-list
• Helium packages: zeppelin-examples/zeppelin-example-clock/zeppelin-example-clock.json, zeppelin-web/src/app/tabledata/package.json, zeppelin-web/src/app/visualization/package.json

TODO(mina): Create bumping up script to simplify this process

After bumping You can bump up the version , and create tag from release branch by doing below.running `tag_release.sh` script as below:

Code Block
language bash
# Prepare release $ mvn versions:set -DnewVersion=0.6.0 -DgenerateBackupPoms=false $ git commit -a -m "Preparing Apache Zeppelin release 0.6.0" $ git tag v0.6.0-rc1   # Prepare next development version $ mvn versions:set -DnewVersion=0.6.1-SNAPSHOT -DgenerateBackupPoms=false $ git commit -a -m "Preparing development version 0.6.1-SNAPSHOT"   # Push changes $ git push apache v0.6.0-rc1 $ git push apache HEAD:branch-0.6CURRENT_VERSION=[current ver.] RELEASE_VERSION=[release ver.] NEXT_DEV_VERSION=[next dev ver.] RC_TAG=[rc tag] GIT_BRANCH=[branch to create tag] dev/tag_release.sh

For example

Code Block
language bash
$ CURRENT_VERSION="0.7.1-SNAPSHOT" RELEASE_VERSION="0.7.1" NEXT_DEV_VERSION="0.7.2-SNAPSHOT" RC_TAG="v0.7.1-rc1" GIT_BRANCH="branch-0.7" dev/tag_release.sh

will bump up the version of all files mentioned above and create tag for 0.7.1 first release candidate.

Create release Candidate

Create source and binary package

...