[
https://issues.apache.org/jira/browse/FLINK-34594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lincoln lee closed FLINK-34594.
-------------------------------
Resolution: Fixed
vote result https://lists.apache.org/thread/stps3d8m6hsny5mglbr4h09879ny5nog
> CLONE - Vote on the release candidate
> -------------------------------------
>
> Key: FLINK-34594
> URL: https://issues.apache.org/jira/browse/FLINK-34594
> Project: Flink
> Issue Type: Sub-task
> Affects Versions: 1.19.0
> Reporter: Lincoln Lee
> Assignee: lincoln lee
> Priority: Major
> Fix For: 1.19.0
>
>
> Once you have built and individually reviewed the release candidate, please
> share it for the community-wide review. Please review foundation-wide [voting
> guidelines|http://www.apache.org/foundation/voting.html] for more information.
> Start the review-and-vote thread on the dev@ mailing list. Here’s an email
> template; please adjust as you see fit.
> {quote}From: Release Manager
> To: [email protected]
> Subject: [VOTE] Release 1.2.3, release candidate #3
> Hi everyone,
> Please review and vote on the release candidate #3 for the version 1.2.3, 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 and binary convenience releases to be
> deployed to dist.apache.org [2], which are signed with the key with
> fingerprint FFFFFFFF [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "release-1.2.3-rc3" [5],
> * website pull request listing the new release and adding announcement blog
> post [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] link
> [3] [https://dist.apache.org/repos/dist/release/flink/KEYS]
> [4] link
> [5] link
> [6] link
> {quote}
> *If there are any issues found in the release candidate, reply on the vote
> thread to cancel the vote.* There’s no need to wait 72 hours. Proceed to the
> Fix Issues step below and address the problem. However, some issues don’t
> require cancellation. For example, if an issue is found in the website pull
> request, just correct it on the spot and the vote can continue as-is.
> For cancelling a release, the release manager needs to send an email to the
> release candidate thread, stating that the release candidate is officially
> cancelled. Next, all artifacts created specifically for the RC in the
> previous steps need to be removed:
> * Delete the staging repository in Nexus
> * Remove the source / binary RC files from dist.apache.org
> * Delete the source code tag in git
> *If there are no issues, reply on the vote thread to close the voting.* Then,
> tally the votes in a separate email. Here’s an email template; please adjust
> as you see fit.
> {quote}From: Release Manager
> To: [email protected]
> Subject: [RESULT] [VOTE] Release 1.2.3, release candidate #3
> I'm happy to announce that we have unanimously approved this release.
> There are XXX approving votes, XXX of which are binding:
> * approver 1
> * approver 2
> * approver 3
> * approver 4
> There are no disapproving votes.
> Thanks everyone!
> {quote}
>
> ----
> h3. Expectations
> * Community votes to release the proposed candidate, with at least three
> approving PMC votes
> Any issues that are raised till the vote is over should be either resolved or
> moved into the next release (if applicable).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
