THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- 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
- versions in all the Dockerfile
You can bump up the version and create tag from release branch by running `tag_release.sh` script as below:
...
https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.6.0-rc1
Refer the link here. https://stackoverflow.com/questions/15510119/how-to-add-an-existing-folder-with-files-to-svn/15511432
Deploy maven artifact to staging repository
...
| Code Block | ||
|---|---|---|
| ||
$ svn mv https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.6.0-rc1 https://dist.apache.org/repos/dist/release/zeppelin/zeppelin-0.6.0 -m 'Move 0.6.0 to release folder' |
Create tag for release and clean up tags for rc
Create tag without name 'rc' and remove all 'rc' tags. Make sure that release version archived under http://archive.apache.org/dist/zeppelin/ before creating tag so that docker build succeed without error.
| Code Block | ||
|---|---|---|
| ||
git tag v0.9.0-preview1 v0.9.0-preview1-rc1 git push apache v0.9.0-preview1 git push apache :v0.9.0-preview1-rc1 |
Remove old release
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' released version from JIRA
Update download page
Update download page in download.html and supported_interpreters.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.orghttps://issues.apache.org/jira/projects/ZEPPELIN?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=unreleased
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.
...
| Code Block | ||
|---|---|---|
| ||
# Make sure you are using python 2.7 # Build release version document $ git clone https://github.com/apache/zeppelin.git $ cd zeppelin $ git checkout v0.6.0 $ cd docs # Update file _config.yml (ASSET_PATH & ZEPPELIN_VERSION & BASE_PATH) $ 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 # Do the same for snapshot version if you are releasing a new major version, e.g. 0.9.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 # Update file download.md, doap.rdf, documentation.md, supported_interpreters.md, _navigation.html $ JEKYLL_ENV=production bundle exec jekyll build # 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" |
...