Page History

...

1. If you have not already, check out the Flink section of the dev repository on dist.apache.org via Subversion. In a fresh directory:

   Code Block
   language bash
   svn checkout https://dist.apache.org/repos/dist/dev/flink --depth=immediates

   
   

2. Make a directory for the new release:

   Code Block
   language bash
   mkdir flink/flink-statefun-${RELEASE_VERSION}-rc${RC_NUM}

   Copy all release distributions, hashes, and GPG signature:

   Code Block
   mv <flink-statefun-dir>/release/* flink/flink-statefun-${RELEASE_VERSION}-rc${RC_NUM}

   
   

3. Add and commit all the files.

   Code Block
   language bash
   cd flink svn add flink-statefun-${RELEASE_VERSION}-rc${RC_NUM} svn commit -m "Apache Flink Stateful Functions, version ${RELEASE_VERSION}, release candidate ${RC_NUM}"

   
   

4. Verify that files are present

(Push the release tag)

If you haven't pushed the release tag yet, here's the command:

git push <remote> refs/tags/release-${RELEASE_VERSION}-rc${RC_NUM}

...

Start by updating the variables for the latest released version released version in the top-level _config.ymltoml, and list the new release in downloads.md, linking to the source code download and the Release Notes in JIRA. Also add a new blog entry announcing the release in _posts.

...

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.ymltoml 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

...