You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jing Ge (Jira)" <ji...@apache.org> on 2023/09/14 10:38:00 UTC

[jira] [Assigned] (FLINK-32932) Build Release Candidate: 1.18.0-rc1

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

Jing Ge reassigned FLINK-32932:
-------------------------------

    Assignee: Jing Ge

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



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