[jira] [Assigned] (FLINK-31154) Build Release Candidate: 1.17.0-rc1
[ https://issues.apache.org/jira/browse/FLINK-31154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qingsheng Ren reassigned FLINK-31154: - Assignee: Qingsheng Ren > Build Release Candidate: 1.17.0-rc1 > --- > > Key: FLINK-31154 > URL: https://issues.apache.org/jira/browse/FLINK-31154 > Project: Flink > Issue Type: New Feature >Affects Versions: 1.17.0 >Reporter: Matthias Pohl >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} > RC_NUM="1" > TAG="release-${RELEASE_VERSION}-rc${RC_NUM}" > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FLINK-31154) Build Release Candidate: 1.17.0-rc1
[ https://issues.apache.org/jira/browse/FLINK-31154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-31154: --- Assignee: Jing Ge (was: Qingsheng Ren) > Build Release Candidate: 1.17.0-rc1 > --- > > Key: FLINK-31154 > URL: https://issues.apache.org/jira/browse/FLINK-31154 > Project: Flink > Issue Type: New Feature >Affects Versions: 1.17.0 >Reporter: Matthias Pohl >Assignee: Jing Ge >Priority: Major > Fix For: 1.17.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)
[jira] [Assigned] (FLINK-31154) Build Release Candidate: 1.17.0-rc1
[ https://issues.apache.org/jira/browse/FLINK-31154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weijie Guo reassigned FLINK-31154: -- Assignee: Jing Ge (was: Weijie Guo) > Build Release Candidate: 1.17.0-rc1 > --- > > Key: FLINK-31154 > URL: https://issues.apache.org/jira/browse/FLINK-31154 > Project: Flink > Issue Type: New Feature >Affects Versions: 1.17.0 >Reporter: Matthias Pohl >Assignee: Jing Ge >Priority: Major > Fix For: 1.17.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)