[jira] [Updated] (FLINK-33833) Build Release Candidate: 1.18.1-rc1

2023-12-14 Thread Jing Ge (Jira) 


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

Jing Ge updated FLINK-33833:

Fix Version/s: (was: 1.18.1)

> Build Release Candidate: 1.18.1-rc1
> ---
>
> Key: FLINK-33833
> URL: https://issues.apache.org/jira/browse/FLINK-33833
> Project: Flink
>  Issue Type: New Feature
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>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)

[jira] [Updated] (FLINK-33833) Build Release Candidate: 1.18.1-rc1

2023-12-14 Thread Jing Ge (Jira) 


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

Jing Ge updated FLINK-33833:

Affects Version/s: 1.18.0
   (was: 1.17.0)

> Build Release Candidate: 1.18.1-rc1
> ---
>
> Key: FLINK-33833
> URL: https://issues.apache.org/jira/browse/FLINK-33833
> Project: Flink
>  Issue Type: New Feature
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>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] [Updated] (FLINK-33833) Build Release Candidate: 1.18.1-rc1

2023-12-14 Thread Jing Ge (Jira) 


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

Jing Ge updated FLINK-33833:

Fix Version/s: 1.18.1
   (was: 1.17.0)

> Build Release Candidate: 1.18.1-rc1
> ---
>
> Key: FLINK-33833
> URL: https://issues.apache.org/jira/browse/FLINK-33833
> Project: Flink
>  Issue Type: New Feature
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Fix For: 1.18.1
>
>
> 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)