Page History

...

Introduction

The Apache Flink project periodically declares and publishes releases. A release is one or more packages of the project artifact(s) that are approved for general public distribution and use. They may come with various degrees of caveat regarding their perceived quality and potential for change, such as “alpha”, “beta”, “incubating”, “stable”, etc.

...

• Create the source release archive
• Deploy jar artifacts to the Apache Nexus Repository, which is the staging area for deploying the jars to Maven Central
• Note: Please do not use VPN or change your IP address when stage artifacts to Apache Nexus Repository, it may lead to multiple staging repositories which is unexpected.

# verify the environment contains all software needed for the release process
./tools/releasing/shared/check_environment.sh

# update the versions in the poms
./tools/releasing/shared/update_branch_version.sh

# create and stage artifacts to be voted on
./tools/releasing/shared/release_git_tag.sh
./tools/releasing/shared/stage_source_release.sh

# call this once for each supported (minor) Flink version
FLINK_VERSION=1.16.0 ./tools/releasing/shared/stage_jars.sh

...

Adjust any of the above properties to the improve clarity and presentation of the Release Notes.Ensure that the JIRA release notes are also included in the release notes of the documentation (see section "Review and update documentation").

Content of Release Notes field from JIRA tickets 

...