Zeppelin Jira

Skip to end of metadataGo to start of metadata

Project lead moon soo Lee Key ZEPPELIN Issue Status. Once Zeplin for Jira app is installed, everyone with access to your Jira project can connect their Zeplin accounts and attach screens, sections, or projects to any issues or tasks in Jira. ☝️ Zeplin for Jira Cloud is available for all subscription plans, include the Free plan. Zeplin for Jira Server is only available on the Organization. When using Zeppelin in cluster mode, I found FLINKCONFDIR, FLINKLIBDIR and FLINKPLUGINSDIR are not correct, it leads to some exceptions when submitting the Flink SQL job on Yarn. I guess FlinkInterpreterLauncher is not working in Zeppelin cluster mode. Atlassian Jira Project Management Software (v8.3.4#803005-sha1:1f96e09) About Jira.

From 0.6.0 release

A release branch need to be created for major release.

Minor release is released from the same branch with different tag.

For example, release 0.6.0 will create branch 'branch-0.6', but release 0.6.1 will be released from the same branch 'branch-0.6' with different tag.

0.5.x release

Each 0.5.x release has it's own release branch 'branch-0.5.x'. The branch cuts 'master' branch on creation.

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

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

For example

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

Create source and binary package

Clone tagged version into the machine that'll create package.

'create_release.sh' script will create source and binary package for the release candidate under '/tmp/zeppelin-release' directory

For example

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

Upload release candidate

Created release candidate needs to be uploaded into svn repository

for example, for 0.6.0 release candidate 1, contents of '/tmp/zeppelin-release' directory need to be uploaded into

Deploy maven artifact to staging repository

For example

Once release candidate is ready, start a vote thread in dev@ list. For example

Once vote is passed, post result into the dev@list. For example

Zeppelin Jar

Move release package from dev to release

for example

Create tag for release and clean up tags for rc

Zeppelin Girl Band

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.

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.) 24 names of vishnu.

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

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

Before announcing the release, you need to check the apache release status page to confirm there's no problem in the release process. https://checker.apache.org/projs/zeppelin.html

New release can be announced to some mailing lists such as

announce at apache.org
users at zeppelin.apache.org
dev at zeppelin.apache.org

Here's an example of an announce.

Please also include a short description of what Apache Zeppelin is or does as the first paragraph i.e

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

By default, when you install the Zeplin for Jira app, it will be enabled for all your Jira projects.

To enable the app for certain Jira projects, you can select “Zeplin for Jira Settings” from the Apps menu up top. From there, you can click on “Select projects” and select which projects you want to enable Zeplin for.

☝️ If you don't see the 'Select projects' option under Zepllin for Jira Settings, make sure that you have Jira admin privileges. Only admins of your Jira instance can update this setting.

Related articles: