...
Start the review-and-vote thread on the dev@ mailing list. Here’s an email template; please adjust as you see fit.
| Code Block | ||
|---|---|---|
| ||
echo " From: Release Manager To: dev@flink.apache.org Subject: [VOTE] Release flink-shaded X.Y${RELEASE_VERSION}, release candidate #Z#${RC_NUM} Content: echo " Hi everyone, Please review and vote on the release candidate #${RC_NUM} for the version ${RELEASE_VERSION}, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area is available for your review, which includes: * JIRA release notes [1], * the official Apache source release to be deployed to dist.apache.org [2], which are signed with the key with fingerprint $(git config user.signingKey) [3], * all artifacts to be deployed to the Maven Central Repository [4], * source code tag \"${TAG}\" [5], * website pull request listing the new release [6]. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Thanks, Release Manager [1] link [2] https://dist.apache.org/repos/dist/dev/flink/flink-shaded-${RELEASE_VERSION}-rc${RC_NUM} [3] https://dist.apache.org/repos/dist/release/flink/KEYS [4] link [5] https://github.com/apache/flink-shaded/releases/tag/${TAG} [6] link " |
...