Release Guide

Check Your Environment

To make sure you could successfully complete the release for DolphinScheduler, you should check your environment and make sure all conditions are met, if any or them are missing, you should install them and make sure them work.

# JDK 1.8 above is requests
java -version
# Maven requests
mvn -version
# Python 3.6 above is requests, and you have to make keyword `python` work in your terminal and version match
python --version

GPG Settings

Install GPG

Download installation package on official GnuPG website. The command of GnuPG 1.x version can differ a little from that of 2.x version. The following instructions take GnuPG-2.1.23 version for example.

After the installation, execute the following command to check the version number.

gpg --version

Create Key

After the installation, execute the following command to create key.

This command indicates GnuPG-2.x can be used:

gpg --full-gen-key

This command indicates GnuPG-1.x can be used:

gpg --gen-key

Finish the key creation according to instructions, Notice: Please use Apache mails and its password for key creation.

gpg (GnuPG) 2.0.12; Copyright (C) 2009 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Please select what kind of key you want:
  (1) RSA and RSA (default)
  (2) DSA and Elgamal
  (3) DSA (sign only)
  (4) RSA (sign only)
Your selection? 1
RSA keys may be between 1024 and 4096 bits long.
What keysize do you want? (2048) 4096
Requested keysize is 4096 bits
Please specify how long the key should be valid.
        0 = key does not expire
     <n>  = key expires in n days
     <n>w = key expires in n weeks
     <n>m = key expires in n months
     <n>y = key expires in n years
Key is valid for? (0)
Key does not expire at all
Is this correct? (y/N) y

GnuPG needs to construct a user ID to identify your key.

Real name: ${Input username}
Email address: ${Input email}
Comment: ${Input comment}
You selected this USER-ID:
   "${Inputed username} (${Inputed comment}) <${Inputed email}>"

Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O
You need a Passphrase to protect your secret key. # Input your Apache mail passwords

Check Generated Key

gpg --list-keys

Execution Result:

pub   4096R/85E11560 2019-11-15
uid                  ${Username} (${Comment}) <{Email}>
sub   4096R/A63BC462 2019-11-15

Among them, 85E11560 is public key ID.

Upload the Public Key to Key Server

The command is as follow:

gpg --keyserver hkp:// --send-key 85E11560 is randomly chosen from public key server. Each server will automatically synchronize with one another, so it would be okay to choose any one, a backup keys servers is gpg --keyserver hkp:// --send-key <YOUR_KEY_ID>

Apache Maven Central Repository Release

Set settings-security.xml and settings.xml

In this section, we add Apache server maven configuration to prepare the release, we have to add settings-security.xml according to here firstly and then change your ~/.m2/settings.xml like below

      <username> <!-- APACHE LDAP username --> </username>
      <password> <!-- APACHE LDAP encrypted password --> </password>
      <username> <!-- APACHE LDAP username --> </username>
      <password> <!-- APACHE LDAP encrypted password --> </password>

Set Release in Environment

We will use the release version, your github name and your Apache username below several times, so it is better to store it to bash variable for easier use.


Note: We can use the variable directly in you bash after we set environment, without changing anything. For example, we can use command git clone -b "${VERSION}"-prepare to clone the release branch and it can be success by covert the "${VERSION}" to <THE-VERSION-YOU-RELEASE>. But you have to change <VERSION> manually in some of not bash step like vote mail, we using <VERSION> instead of "${VERSION}" to notice release manager they have to change by hand.

Create Release Branch

In this section, we dwonload source code from github and create new branch to release

git clone -b "${VERSION}"-prepare
cd ~/dolphinscheduler/
git pull
git checkout -b "${VERSION}"-release
git push origin "${VERSION}"-release

Pre-Release Check

# make gpg command could be run in maven correct
export GPG_TTY=$(tty)

mvn release:prepare -Prelease,python -Darguments="-Dmaven.test.skip=true -Dcheckstyle.skip=true -Dmaven.javadoc.skip=true" -DautoVersionSubmodules=true -DdryRun=true -Dusername="${GH_USERNAME}"
  • -Prelease,python: choose release and python profile, which will pack all the source codes, jar files and executable binary packages, and Python distribute package.
  • -DautoVersionSubmodules=true: it can make the version number is inputted only once and not for each sub-module.
  • -DdryRun=true: dry run which means not to generate or submit new version number and new tag.

Prepare for the Release

First, clean local pre-release check information.

mvn release:clean

Then, prepare to execute the release.

mvn release:prepare -Prelease,python -Darguments="-Dmaven.test.skip=true -Dcheckstyle.skip=true -Dmaven.javadoc.skip=true" -DautoVersionSubmodules=true -DpushChanges=false -Dusername="${GH_USERNAME}"

It is basically the same as the previous rehearsal command, but deleting -DdryRun=true parameter.

  • -DpushChanges=fals: do not submit the edited version number and tag to GitHub automatically.

Note: You have to config your git and user.password by command git config --global "" and git config --global "Your Name" if you meet some mistake like Please tell me who you are. from git.

After making sure there is no mistake in local files, submit them to GitHub.

git push -u origin "${VERSION}"-release
git push origin --tags

Note1: In this step, you should use github token for password because native password no longer supported, you can see for more detail about how to create token about it.

Note2: After the command done, it will auto-created file and *.Backup files, their will be need in the following command and DO NOT DELETE THEM

Deploy the Release

mvn release:perform -Prelease,python -Darguments="-Dmaven.test.skip=true -Dcheckstyle.skip=true -Dmaven.javadoc.skip=true" -DautoVersionSubmodules=true -Dusername="${GH_USERNAME}"

After that command is executed, the version to be released will be uploaded to Apache staging repository automatically. Go to apache staging repositories and login by Apache LDAP. then you can see the uploaded version, the content of Repository column is the ${STAGING.REPOSITORY}. Click Close to tell Nexus that the construction is finished, because only in this way, this version can be usable. If there is any problem in gpg signature, Close will fail, but you can see the failure information through Activity.

Apache SVN Repository Release

Checkout dolphinscheduler Release Directory

If there is no local work directory, create one at first.

mkdir -p ~/ds_svn/dev/
cd ~/ds_svn/dev/

After the creation, checkout dolphinscheduler release directory from Apache SVN.

svn --username="${A_USERNAME}" co
cd ~/ds_svn/dev/dolphinscheduler

Add gpg Public Key

Only the account in its first deployment needs to add that. It is alright for KEYS to only include the public key of the deployed account.

gpg -a --export <YOUR-GPG-KEY-ID> >> KEYS

Add the Release Content to SVN Directory

Create folder by version number.

mkdir -p ~/ds_svn/dev/dolphinscheduler/"${VERSION}"
mkdir -p ~/ds_svn/dev/dolphinscheduler/"${VERSION}"/python
cd ~/ds_svn/dev/dolphinscheduler/"${VERSION}"

Add source code packages, binary packages and executable binary packages to SVN working directory.

# Source and binary tarball for main code
cp -f ~/dolphinscheduler/dolphinscheduler-dist/target/*.tar.gz ~/ds_svn/dev/dolphinscheduler/"${VERSION}"
cp -f ~/dolphinscheduler/dolphinscheduler-dist/target/*.tar.gz.asc ~/ds_svn/dev/dolphinscheduler/"${VERSION}"

# Source and binary tarball for Python API
cp -f ~/dolphinscheduler/dolphinscheduler-dist/target/python/* ~/ds_svn/dev/dolphinscheduler/"${VERSION}"/python

Generate sign files

shasum -a 512 apache-dolphinscheduler-"${VERSION}"-src.tar.gz >> apache-dolphinscheduler-"${VERSION}"-src.tar.gz.sha512
shasum -b -a 512 apache-dolphinscheduler-"${VERSION}"-bin.tar.gz >> apache-dolphinscheduler-"${VERSION}"-bin.tar.gz.sha512
cd python
shasum -a 512 apache-dolphinscheduler-python-"${VERSION}".tar.gz >> apache-dolphinscheduler-python-"${VERSION}".tar.gz.sha512
shasum -b -a 512 apache_dolphinscheduler-python-"${VERSION}"-py3-none-any.whl >> apache_dolphinscheduler-python-"${VERSION}"-py3-none-any.whl.sha512
cd ../

Commit to Apache SVN

cd ~/ds_svn/dev/dolphinscheduler
svn add *
svn --username="${A_USERNAME}" commit -m "release ${VERSION}"

Check Release

Check sha512 hash

shasum -c apache-dolphinscheduler-"${VERSION}"-src.tar.gz.sha512
shasum -c apache-dolphinscheduler-"${VERSION}"-bin.tar.gz.sha512
cd python
shasum -c apache-dolphinscheduler-python-"${VERSION}".tar.gz.sha512
shasum -c apache_dolphinscheduler-python-"${VERSION}"-py3-none-any.whl.sha512
cd ../

Check gpg Signature

First, import releaser's public key. Import KEYS from SVN repository to local. (The releaser does not need to import again; the checking assistant needs to import it, with the user name filled as the releaser's. )

curl >> KEYS
gpg --import KEYS
gpg --edit-key "${A_USERNAME}"
  > trust

Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)

  1 = I don't know or won't say
  2 = I do NOT trust
  3 = I trust marginally
  4 = I trust fully
  5 = I trust ultimately
  m = back to the main menu

Your decision? 5

  > save

Then, check the gpg signature.

gpg --verify apache-dolphinscheduler-"${VERSION}"-src.tar.gz.asc
gpg --verify apache-dolphinscheduler-"${VERSION}"-bin.tar.gz.asc
cd python
gpg --verify apache-dolphinscheduler-python-"${VERSION}".tar.gz.asc
gpg --verify apache_dolphinscheduler-python-"${VERSION}"-py3-none-any.whl.asc
cd ../

Note: You have to create gpg signature manually when you can not find your asc file, the command gpg --armor --detach-sign --digest-algo=SHA512 apache-dolphinscheduler-"${VERSION}"-bin.tar.gz and gpg --armor --detach-sign --digest-algo=SHA512 apache-dolphinscheduler-"${VERSION}"-src.tar.gz will create them

Check Released Files

Check source package

Decompress apache-dolphinscheduler-<VERSION>-src.tar.gz and python/apache-dolphinscheduler-python-<VERSION>.tar.gz then check the following items:

  • Check whether source tarball is oversized for including nonessential files
  • LICENSE and NOTICE files exist
  • Correct year in NOTICE file
  • There is only text files but no binary files
  • All source files have ASF headers
  • Codes can be compiled and pass the unit tests (mvn install)
  • The contents of the release match with what's tagged in version control (diff -r a verify_dir tag_dir)
  • Check if there is any extra files or folders, empty folders for example

Check binary packages

Decompress apache-dolphinscheduler-<VERSION>-src.tar.gz and python/apache-dolphinscheduler-python-<VERSION>-bin.tar.gz to check the following items:

  • LICENSE and NOTICE files exist
  • Correct year in NOTICE file
  • Check the third party dependency license:
    • The software have a compatible license
    • All software licenses mentioned in LICENSE
    • All the third party dependency licenses are under licenses folder
    • If it depends on Apache license and has a NOTICE file, that NOTICE file need to be added to NOTICE file of the release

Call for a Vote

Update Release Notes

You should create a release note in GitHub by new release note. It should be done before vote mail because we need the release note in the mail. You could use command git log --pretty="- %s" <PREVIOUS-RELEASE-SHA>..<CURRENT-RELEASE-SHA> > to creat the changelog(some log maybe not correct, you should filter them by yourself) and classify them and paste them to GitHub release note page

Vote procedure

  1. DolphinScheduler community vote: send the vote e-mail to PMC needs to check the rightness of the version according to the document before they vote. After at least 72 hours and with at least 3 +1 and no -1 PMC member votes, it can come to the next stage of the vote.

  2. Announce the vote result: send the result vote e-mail to

Vote Templates

DolphinScheduler Community Vote Template


[VOTE] Release Apache DolphinScheduler <VERSION>


Hello DolphinScheduler Community,

This is a call for vote to release Apache DolphinScheduler version <VERSION>

Release notes:<VERSION>

The release candidates:<VERSION>/

Maven 2 staging repository:<VERSION>/org/apache/dolphinscheduler/

Git tag for the release:<VERSION>

Release Commit ID:<SHA-VALUE>

Keys to verify the Release Candidate:

Look at here for how to verify this release candidate:

The vote will be open for at least 72 hours or until necessary number of votes are reached.

Please vote accordingly:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Checklist for reference:

[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each DolphinScheduler repo.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.
  1. Announce the vote result:


The vote to release Apache DolphinScheduler <VERSION> has passed.Here is the vote result,

4 PMC member +1 votes:


1 community +1 vote:

Thanks everyone for taking time to check this release and help us.

Finish the Release

Move source packages, binary packages from the dev directory to release directory

svn mv"${VERSION}"

Export you new gpg KEYS from dev to release(optional)

Only if the first time you release with this gpg KEY, including it is you first release or you change your KEY

mkdir -p ~/ds_svn/release/
cd ~/ds_svn/release/
svn --username="${A_USERNAME}" co
gpg -a --export <YOUR-GPG-KEY-ID> >> KEYS
svn add *
svn --username="${A_USERNAME}" commit -m "new key <YOUR-GPG-KEY-ID> add"

Update Document

Website should be present before you send the announce mail this section will tell you how to change the website. For example, the release version is <VERSION>, the following updates are required(note it will take effect immediately when the PR is merged):

  • Repository apache/dolphinscheduler-website:
    • download/en-us/ and download/zh-cn/ add the download of the <VERSION> release package
    • scripts/ Add new release version <VERSION> key-value pair to variable DEV_RELEASE_DOCS_VERSIONS
  • Repository apache/dolphinscheduler:
    • docs/configs/site.js:
      • docsLatest: update to <VERSION>
      • docs0: The text of two places of en-us/zh-cn needs to be updated to latest(<VERSION>)
      • docsxyz: Add a drop-down menu with key as docsxyz and text as <VERSION> in children of two places of en-us/zh-cn
    • docs/configs/ Add <VERSION>: docsxyzConfig
    • docs/docs/en/ and docs/docs/zh/ Add new <VERSION> release docs.
    • .github/ISSUE_TEMPLATE/bug-report.yml: DolphinScheduler's GitHub bug-report issue template have Version selection bottom. So after we release DolphinScheduler we should and the new <VERSION> to bug-report.yml

Find DolphinScheduler in apache staging repositories and click Release

Send Announcement E-mail Community

You should send announcement E-mail after release process finished. The E-mail should send to and cc to

Announcement e-mail template as below:


[ANNOUNCE] Release Apache DolphinScheduler <VERSION>


Hi all,

We are glad to announce the release of Apache DolphinScheduler <VERSION>. Once again I would like to express my thanks to your help.

Dolphin Scheduler is a distributed and easy-to-extend visual workflow scheduler system,
dedicated to solving the complex task dependencies in data processing, making the scheduler system out of the box for data processing.

Download Links:

Release Notes:<VERSION>


DolphinScheduler Resources:
- Issue:
- Mailing list:
- Documents:<VERSION>/user_doc/about/introduction.html