[jira] [Updated] (FLINK-31146) Prepare Flink 1.17 Release

2023-03-23 Thread Leonard Xu (Jira)


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

Leonard Xu updated FLINK-31146:
---
Component/s: Release System

> Prepare Flink 1.17 Release
> --
>
> Key: FLINK-31146
> URL: https://issues.apache.org/jira/browse/FLINK-31146
> Project: Flink
>  Issue Type: New Feature
>  Components: Release System
>Affects Versions: 1.17.0
>Reporter: Matthias Pohl
>Assignee: Leonard Xu
>Priority: Major
> Fix For: 1.17.0
>
>
> This umbrella issue is meant as a test balloon for moving the [release 
> documentation|https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release]
>  into Jira.
> h3. Prerequisites
> h4. Environment Variables
> Commands in the subtasks might expect some of the following enviroment 
> variables to be set accordingly to the version that is about to be released:
> {code:bash}
> RELEASE_VERSION="1.5.0"
> SHORT_RELEASE_VERSION="1.5"
> CURRENT_SNAPSHOT_VERSION="$SHORT_RELEASE_VERSION-SNAPSHOT"
> NEXT_SNAPSHOT_VERSION="1.6-SNAPSHOT"
> SHORT_NEXT_SNAPSHOT_VERSION="1.6"
> {code}
> h4. Build Tools
> All of the following steps require to use Maven 3.2.5 and Java 8. Modify your 
> PATH environment variable accordingly if needed.
> h4. Flink Source
>  * Create a new directory for this release and clone the Flink repository 
> from Github to ensure you have a clean workspace (this step is optional).
>  * Run {{mvn -Prelease clean install}} to ensure that the build processes 
> that are specific to that profile are in good shape (this step is optional).
> The rest of this instructions assumes that commands are run in the root (or 
> {{./tools}} directory) of a repository on the branch of the release version 
> with the above environment variables set.



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


[jira] [Updated] (FLINK-31146) Prepare Flink 1.17 Release

2023-02-21 Thread Matthias Pohl (Jira)


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

Matthias Pohl updated FLINK-31146:
--
Description: 
This umbrella issue is meant as a test balloon for moving the [release 
documentation|https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release]
 into Jira.
h3. Prerequisites
h4. Environment Variables

Commands in the subtasks might expect some of the following enviroment 
variables to be set accordingly to the version that is about to be released:
{code:bash}
RELEASE_VERSION="1.5.0"
SHORT_RELEASE_VERSION="1.5"
CURRENT_SNAPSHOT_VERSION="$SHORT_RELEASE_VERSION-SNAPSHOT"
NEXT_SNAPSHOT_VERSION="1.6-SNAPSHOT"
SHORT_NEXT_SNAPSHOT_VERSION="1.6"
{code}
h4. Build Tools

All of the following steps require to use Maven 3.2.5 and Java 8. Modify your 
PATH environment variable accordingly if needed.
h4. Flink Source
 * Create a new directory for this release and clone the Flink repository from 
Github to ensure you have a clean workspace (this step is optional).
 * Run {{mvn -Prelease clean install}} to ensure that the build processes that 
are specific to that profile are in good shape (this step is optional).

The rest of this instructions assumes that commands are run in the root (or 
{{./tools}} directory) of a repository on the branch of the release version 
with the above environment variables set.

  was:
This umbrella issue is meant as a test balloon for moving the [release 
documentation|https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release]
 into Jira.
h3. Prerequisites
h4. Environment Variables

Commands in the subtasks might expect some of the following enviroment 
variables to be set accordingly to the version that is about to be released:
{code:bash}
RELEASE_VERSION="1.5.0"
SHORT_RELEASE_VERSION="1.5"
CURRENT_SNAPSHOT_VERSION="$SHORT_RELEASE_VERSION-SNAPSHOT"
NEXT_SNAPSHOT_VERSION="1.6-SNAPSHOT"
SHORT_NEXT_SNAPSHOT_VERSION="1.6"
{code}
h4. Build Tools

All of the following steps require to use Maven 3.2.5 and Java 8. Modify your 
PATH environment variable accordingly if needed.
h4. Flink Source
 * Create a new directory for this release and clone the Flink repository from 
Github to ensure you have a clean workspace (this step is optional).
 * Run {{mvn -Prelease clean install}} to ensure that the build processes that 
are specific to that profile are in good shape (this step is optional).

The rest of this instructions assumes that commands are run in the root (or 
{{./tools}} directory) of a repository on the branch of the release version 
with the above environment variables set.

h4. Verify that no exclusions were erroneously added to the japicmp plugin that 
break compatibility guarantees

Check the exclusions for the {{japicmp-maven-plugin}} in the root pom for 
exclusions that:
 * for minor releases, break source compatibility for  {{@Public}} APIs
 * for patch releases, break source/binary compatibility for {{@Public}}  / 
{{@PublicEvolving}}  APIs

Any such exclusion must be properly justified, in advance.


> Prepare Flink 1.17 Release
> --
>
> Key: FLINK-31146
> URL: https://issues.apache.org/jira/browse/FLINK-31146
> Project: Flink
>  Issue Type: New Feature
>Affects Versions: 1.17.0
>Reporter: Matthias Pohl
>Priority: Major
> Fix For: 1.17.0
>
>
> This umbrella issue is meant as a test balloon for moving the [release 
> documentation|https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release]
>  into Jira.
> h3. Prerequisites
> h4. Environment Variables
> Commands in the subtasks might expect some of the following enviroment 
> variables to be set accordingly to the version that is about to be released:
> {code:bash}
> RELEASE_VERSION="1.5.0"
> SHORT_RELEASE_VERSION="1.5"
> CURRENT_SNAPSHOT_VERSION="$SHORT_RELEASE_VERSION-SNAPSHOT"
> NEXT_SNAPSHOT_VERSION="1.6-SNAPSHOT"
> SHORT_NEXT_SNAPSHOT_VERSION="1.6"
> {code}
> h4. Build Tools
> All of the following steps require to use Maven 3.2.5 and Java 8. Modify your 
> PATH environment variable accordingly if needed.
> h4. Flink Source
>  * Create a new directory for this release and clone the Flink repository 
> from Github to ensure you have a clean workspace (this step is optional).
>  * Run {{mvn -Prelease clean install}} to ensure that the build processes 
> that are specific to that profile are in good shape (this step is optional).
> The rest of this instructions assumes that commands are run in the root (or 
> {{./tools}} directory) of a repository on the branch of the release version 
> with the above environment variables set.



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


[jira] [Updated] (FLINK-31146) Prepare Flink 1.17 Release

2023-02-20 Thread Matthias Pohl (Jira)


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

Matthias Pohl updated FLINK-31146:
--
Summary: Prepare Flink 1.17 Release  (was: Flink 1.17 Release)

> Prepare Flink 1.17 Release
> --
>
> Key: FLINK-31146
> URL: https://issues.apache.org/jira/browse/FLINK-31146
> Project: Flink
>  Issue Type: New Feature
>Affects Versions: 1.17.0
>Reporter: Matthias Pohl
>Priority: Major
> Fix For: 1.17.0
>
>
> This umbrella issue is meant as a test balloon for moving the [release 
> documentation|https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release]
>  into Jira.
> h3. Prerequisites
> h4. Environment Variables
> Commands in the subtasks might expect some of the following enviroment 
> variables to be set accordingly to the version that is about to be released:
> {code:bash}
> RELEASE_VERSION="1.5.0"
> SHORT_RELEASE_VERSION="1.5"
> CURRENT_SNAPSHOT_VERSION="$SHORT_RELEASE_VERSION-SNAPSHOT"
> NEXT_SNAPSHOT_VERSION="1.6-SNAPSHOT"
> SHORT_NEXT_SNAPSHOT_VERSION="1.6"
> {code}
> h4. Build Tools
> All of the following steps require to use Maven 3.2.5 and Java 8. Modify your 
> PATH environment variable accordingly if needed.
> h4. Flink Source
>  * Create a new directory for this release and clone the Flink repository 
> from Github to ensure you have a clean workspace (this step is optional).
>  * Run {{mvn -Prelease clean install}} to ensure that the build processes 
> that are specific to that profile are in good shape (this step is optional).
> The rest of this instructions assumes that commands are run in the root (or 
> {{./tools}} directory) of a repository on the branch of the release version 
> with the above environment variables set.
> h4. Verify that no exclusions were erroneously added to the japicmp plugin 
> that break compatibility guarantees
> Check the exclusions for the {{japicmp-maven-plugin}} in the root pom for 
> exclusions that:
>  * for minor releases, break source compatibility for  {{@Public}} APIs
>  * for patch releases, break source/binary compatibility for {{@Public}}  / 
> {{@PublicEvolving}}  APIs
> Any such exclusion must be properly justified, in advance.



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