...

• Maven build: every pom.xml
• Docs: in docs/_config.yml update ZEPPELIN_VERSION, BASE_PATH.

After bumping up the version, create tag from release branch by doing below.

...

$ GPG_PASSPHRASE=[your gpg passphrase] dev/create_release.sh 0.6.0 v0.6.0-rc1

will create source and binary package for release '0.6.0' based on tag 'v0.6.0'

...

https://dist.apache.org/repos/dist/dev/zeppelin/0.6.0-rc1

Deploy maven artifact to staging repository

$ GPG_PASSPHRASE=[your gpg passphrase] ASF_USERID=[your asf user id] ASF_PASSWORD=[your asf password] dev/createpublish_release.sh [Release version] [Tag name]

...

$ GPG_PASSPHRASE=[your gpg passphrase] ASF_USERID=[your asf user id] ASF_PASSWORD=[your asf password] dev/createpublish_release.sh 0.6.0 v0.6.0-rc1

Start a vote in dev@list

...

Old release should be removed from dist.apache.org. Old releases are automatically archived (See http://www.apache.org/dev/release.html#when-to-archive for more details.)

Release maven artifacts

Release staging repo from https://repository.apache.org/

Add release to reporter tool( https://reporter.apache.org/addrelease.html?zeppelin) after releasing maven artifacts.

Close JIRA issue version

'Release' released version from JIRA

Update download page

Update download page in download.html with new releases information including release note.

Note that link to previous release should be updated while old releases will be moved from dist.apache.org -> archive.apache.org

Publish documents

• Create and publish document

...

• for released version.
• Create and publish document

...

• for next development version

...

• .
• Update latest version redirect rule: Update latest doc page to point new release version in .htacess .
• DOAP file: Add new entry of the release in doap.rdf.

Here is example to publish documents to svn repo

Also make sure that "latest" document is pointing "new version" in .htaccess file in gh-pages branch.

# Build release version document
$ git clone https://github.com/apache/zeppelin.git
$ cd zeppelin
$ git checkout v0.6.0
$ cd docs
$ bundle exec jekyll build --safe
 
# checkout ASF repo and copy release document to it
$ svn co https://svn.apache.org/repos/asf/zeppelin asf-zeppelin
$ cp -R _site asf-zeppelin/site/docs/0.6.0
 
# Build develop version document
$ git checkout master
$ bundle exec jekyll build --safe
 
# copy develop version document to ASF repo
$ cp -R _site asf-zeppelin/site/docs/0.7.0-SNAPSHOT
 
# go to Zeppelin directory and clone gh-pages
$ cd ..
$ git clone -b gh-pages https://github.com/apache/zeppelin.git gh-pages
$ cd gh-pages
$ bundle exec jekyll build --safe
 
# copy main page to ASF repo
$ cp -R _site ../docs/asf-zeppelin/site
 
# add and delete directories to svn repo
$ cd ../docs/asf-zeppelin/site/docs
$ svn delete 0.6.0-SNAPSHOT
$ svn add 0.6.0
$ svn add 0.7.0-SNAPSHOT
$ svn commit -m "Publish document 0.6.0 and 0.7.0-SNAPSHOT"

...

 Zeppelin is a collaborative data analytics and visualization tool for distributed, general-purpose data processing systems such as Apache Spark, Apache Flink, etc.

...