Page History

...

Finally, propose a pull request with these changes. (Don’t merge before finalizing the release.)

Update flink-statefun-playground (for major/minor releases only)

Create a new release-${SHORT_RELEASE_VERSION} branch in flink-statefun-playground by forking the dev branch.

Make sure that all statefun versions are updated to the new ${SHORT_RELEASE_VERSION} (grep for occurrences of the old version).

Checklist to proceed to the next step

1. Maven artifacts deployed to the staging repository of repository.apache.org
2. Source distribution deployed to the dev repository of dist.apache.org
3. Website pull request proposed to list the release
4. Check docs/config.toml to ensure that
   • the version constants refer to the new version
   • the baseurl does not point to flink-statefun-docs-master  but flink-statefun-docs-release-X.Y instead
   flink-statefun-playground contains a new release branch (if major/minor release)

You can (optionally) also do additional verification by:

...

Follow the instructions in the flink-statefun-docker repo to build the new Dockerfiles and send an updated manifest to Docker Hub so the new images are built and published.

Update flink-statefun-playground (for major/minor releases only)

Create a new release-${SHORT_RELEASE_VERSION} branch in flink-statefun-playground by forking the dev branch.

Make sure that all statefun versions are updated to the new ${SHORT_RELEASE_VERSION} (grep for occurrences of the old version).

Checklist to proceed to the next step

• Python artifacts released and indexed in the PyPI Repository
• JavaScript artifacts released and indexed in the npm repository
• Maven artifacts released and indexed in the Maven Central Repository (usually takes about a day to show up)
• Source & binary distributions available in the release repository of https://dist.apache.org/repos/dist/release/flink/
• Dev repository https://dist.apache.org/repos/dist/dev/flink/ is empty
• Release tagged in the source code repository
• Release version finalized in JIRA. (Note: Not all committers have administrator access to JIRA. If you end up getting permissions errors ask on the mailing list for assistance)
• Website contains links to new release binaries and sources in download page
• For major releases, the front page references the correct new major release version and directs to the correct link
• Dockerfiles in flink-statefun-docker updated for the new release and the new images have been pushed to Dockerhub
• flink-statefun-playground contains a new release branch with updated versions (if major/minor release)

Promote the release

Once the release has been finalized, the last step of the process is to promote the release within the project and beyond. Please wait for 24h after finalizing the release in accordance with the ASF release policy.

...