You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "lincoln lee (Jira)" <ji...@apache.org> on 2024/03/06 15:51:00 UTC
[jira] [Closed] (FLINK-34530) Build Release Candidate: 1.19.0-rc1
[ https://issues.apache.org/jira/browse/FLINK-34530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
lincoln lee closed FLINK-34530.
-------------------------------
Resolution: Won't Fix
Close this as rc1 vote cancelled
> Build Release Candidate: 1.19.0-rc1
> -----------------------------------
>
> Key: FLINK-34530
> URL: https://issues.apache.org/jira/browse/FLINK-34530
> Project: Flink
> Issue Type: New Feature
> Affects Versions: 1.19.0
> Reporter: Lincoln Lee
> Assignee: lincoln lee
> Priority: Major
> Fix For: 1.19.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)