You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Weijie Guo (Jira)" <ji...@apache.org> on 2024/07/15 12:19:00 UTC

[jira] [Updated] (FLINK-35844) Build Release Candidate: 1.20.0-rc1

     [ https://issues.apache.org/jira/browse/FLINK-35844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Weijie Guo updated FLINK-35844:
-------------------------------
    Fix Version/s: 1.20.0
                       (was: 1.17.0)

>  Build Release Candidate: 1.20.0-rc1
> ------------------------------------
>
>                 Key: FLINK-35844
>                 URL: https://issues.apache.org/jira/browse/FLINK-35844
>             Project: Flink
>          Issue Type: New Feature
>    Affects Versions: 1.20.0
>            Reporter: Weijie Guo
>            Assignee: Jing Ge
>            Priority: Major
>             Fix For: 1.20.0
>
>
> 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}
> RC_NUM="1"
> TAG="release-${RELEASE_VERSION}-rc${RC_NUM}"
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)