You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Qingsheng Ren (Jira)" <ji...@apache.org> on 2023/03/23 09:57:00 UTC
[jira] [Commented] (FLINK-31583) Build Release Candidate: 1.17.0-rc3
[ https://issues.apache.org/jira/browse/FLINK-31583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704037#comment-17704037 ]
Qingsheng Ren commented on FLINK-31583:
---------------------------------------
1.17.0 RC3 is accepted: [https://lists.apache.org/thread/cgz83tktlg25klf9fm9m3bp0n1dzwm5n]
> Build Release Candidate: 1.17.0-rc3
> -----------------------------------
>
> Key: FLINK-31583
> URL: https://issues.apache.org/jira/browse/FLINK-31583
> Project: Flink
> Issue Type: New Feature
> Affects Versions: 1.17.0
> Reporter: Qingsheng Ren
> Assignee: Qingsheng Ren
> Priority: Major
>
> The core of the release process is the build-vote-fix cycle. Each cycle produces one release candidate. The Release Manager repeats this cycle until the community approves one release candidate, which is then finalized.
> h4. Prerequisites
> Set up a few environment variables to simplify Maven commands that follow. This identifies the release candidate being built. Start with {{RC_NUM}} equal to 1 and increment it for each candidate:
> {code:java}
> RC_NUM="2"
> TAG="release-${RELEASE_VERSION}-rc${RC_NUM}"
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)