[jira] [Created] (FLINK-33848) CLONE - Other announcements
Jing Ge created FLINK-33848:
---
Summary: CLONE - Other announcements
Key: FLINK-33848
URL: https://issues.apache.org/jira/browse/FLINK-33848
Project: Flink
Issue Type: Sub-task
Reporter: Jing Ge
h3. Recordkeeping
Use [reporter.apache.org|https://reporter.apache.org/addrelease.html?flink] to
seed the information about the release into future project reports.
(Note: Only PMC members have access report releases. If you do not have access,
ask on the mailing list for assistance.)
h3. Flink blog
Major or otherwise important releases should have a blog post. Write one if
needed for this particular release. Minor releases that don’t introduce new
major functionality don’t necessarily need to be blogged (see [flink-web PR
#581 for Flink 1.15.3|https://github.com/apache/flink-web/pull/581] as an
example for a minor release blog post).
Please make sure that the release notes of the documentation (see section
"Review and update documentation") are linked from the blog post of a major
release.
We usually include the names of all contributors in the announcement blog post.
Use the following command to get the list of contributors:
{code}
# first line is required to make sort first with uppercase and then lower
export LC_ALL=C
export FLINK_PREVIOUS_RELEASE_BRANCH=
export FLINK_CURRENT_RELEASE_BRANCH=
# e.g.
# export FLINK_PREVIOUS_RELEASE_BRANCH=release-1.17
# export FLINK_CURRENT_RELEASE_BRANCH=release-1.18
git log $(git merge-base master $FLINK_PREVIOUS_RELEASE_BRANCH)..$(git show-ref
--hash ${FLINK_CURRENT_RELEASE_BRANCH}) --pretty=format:"%an%n%cn" | sort -u |
paste -sd, | sed "s/\,/\, /g"
{code}
h3. Social media
Tweet, post on Facebook, LinkedIn, and other platforms. Ask other contributors
to do the same.
h3. Flink Release Wiki page
Add a summary of things that went well or that went not so well during the
release process. This can include feedback from contributors but also more
generic things like the release have taken longer than initially anticipated
(and why) to give a bit of context to the release process.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33843) Promote release 1.18.1
Jing Ge created FLINK-33843:
---
Summary: Promote release 1.18.1
Key: FLINK-33843
URL: https://issues.apache.org/jira/browse/FLINK-33843
Project: Flink
Issue Type: New Feature
Affects Versions: 1.18.0
Reporter: Jing Ge
Assignee: Jing Ge
Once the release has been finalized (FLINK-32920), the last step of the process
is to promote the release within the project and beyond. Please wait for 24h
after finalizing the release in accordance with the [ASF release
policy|http://www.apache.org/legal/release-policy.html#release-announcements].
*Final checklist to declare this issue resolved:*
# Website pull request to [list the
release|http://flink.apache.org/downloads.html] merged
# Release announced on the user@ mailing list.
# Blog post published, if applicable.
# Release recorded in
[reporter.apache.org|https://reporter.apache.org/addrelease.html?flink].
# Release announced on social media.
# Completion declared on the dev@ mailing list.
# Update Homebrew: [https://docs.brew.sh/How-To-Open-a-Homebrew-Pull-Request]
(seems to be done automatically - at least for minor releases for both minor
and major releases)
# Updated the japicmp configuration
** corresponding SNAPSHOT branch japicmp reference version set to the just
released version, and API compatibiltity checks for {{@PublicEvolving}} was
enabled
** (minor version release only) master branch japicmp reference version set to
the just released version
** (minor version release only) master branch japicmp exclusions have been
cleared
# Update the list of previous version in {{docs/config.toml}} on the master
branch.
# Set {{show_outdated_warning: true}} in {{docs/config.toml}} in the branch of
the _now deprecated_ Flink version (i.e. 1.16 if 1.18.0 is released)
# Update stable and master alias in
[https://github.com/apache/flink/blob/master/.github/workflows/docs.yml]
# Open discussion thread for End of Life for Unsupported version (i.e. 1.16)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33850) CLONE - Updates the docs stable version
Jing Ge created FLINK-33850:
---
Summary: CLONE - Updates the docs stable version
Key: FLINK-33850
URL: https://issues.apache.org/jira/browse/FLINK-33850
Project: Flink
Issue Type: Sub-task
Reporter: Jing Ge
Update docs to "stable" in {{docs/config.toml}} in the branch of the
_just-released_ version:
* Change V{{{}ersion{}}} from {{{}x.y-SNAPSHOT }}to \{{{}x.y.z{}}}, i.e.
{{1.6-SNAPSHOT}} to {{1.6.0}}
* Change V{{{}ersionTitle{}}} from {{x.y-SNAPSHOT}} to {{{}x.y{}}}, i.e.
{{1.6-SNAPSHOT}} to {{1.6}}
* Change Branch from {{master}} to {{{}release-x.y{}}}, i.e. {{master}} to
{{release-1.6}}
* Change {{baseURL}} from
{{//[ci.apache.org/projects/flink/flink-docs-master|http://ci.apache.org/projects/flink/flink-docs-master]}}
to
{{//[ci.apache.org/projects/flink/flink-docs-release-x.y|http://ci.apache.org/projects/flink/flink-docs-release-x.y]}}
* Change {{javadocs_baseurl}} from
{{//[ci.apache.org/projects/flink/flink-docs-master|http://ci.apache.org/projects/flink/flink-docs-master]}}
to
{{//[ci.apache.org/projects/flink/flink-docs-release-x.y|http://ci.apache.org/projects/flink/flink-docs-release-x.y]}}
* Change {{IsStable}} to {{true}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33851) CLONE - Start End of Life discussion thread for now outdated Flink minor version
Jing Ge created FLINK-33851: --- Summary: CLONE - Start End of Life discussion thread for now outdated Flink minor version Key: FLINK-33851 URL: https://issues.apache.org/jira/browse/FLINK-33851 Project: Flink Issue Type: Sub-task Reporter: Jing Ge The idea is to discuss whether we should do a final release for the now not supported minor version in the community. Such a minor release shouldn't be covered by the current minor version release managers. Their only responsibility is to trigger the discussion. The intention of a final patch release for the now unsupported Flink minor version is to flush out all the fixes that didn't end up in the previous release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-33832) Verify that no exclusions were erroneously added to the japicmp plugin
[
https://issues.apache.org/jira/browse/FLINK-33832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33832:
Summary: Verify that no exclusions were erroneously added to the japicmp
plugin (was: No need for patch release - Verify that no exclusions were
erroneously added to the japicmp plugin)
> Verify that no exclusions were erroneously added to the japicmp plugin
> --
>
> Key: FLINK-33832
> URL: https://issues.apache.org/jira/browse/FLINK-33832
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> 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 (see
> [apache/flink:pom.xml:2175ff|https://github.com/apache/flink/blob/3856c49af77601cf7943a5072d8c932279ce46b4/pom.xml#L2175]
> 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)
[jira] [Reopened] (FLINK-33832) Verify that no exclusions were erroneously added to the japicmp plugin
[
https://issues.apache.org/jira/browse/FLINK-33832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reopened FLINK-33832:
-
> Verify that no exclusions were erroneously added to the japicmp plugin
> --
>
> Key: FLINK-33832
> URL: https://issues.apache.org/jira/browse/FLINK-33832
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> 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 (see
> [apache/flink:pom.xml:2175ff|https://github.com/apache/flink/blob/3856c49af77601cf7943a5072d8c932279ce46b4/pom.xml#L2175]
> 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)
[jira] [Updated] (FLINK-33843) Promote release 1.18.1
[
https://issues.apache.org/jira/browse/FLINK-33843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33843:
Description:
Once the release has been finalized, the last step of the process is to promote
the release within the project and beyond. Please wait for 24h after finalizing
the release in accordance with the [ASF release
policy|http://www.apache.org/legal/release-policy.html#release-announcements].
*Final checklist to declare this issue resolved:*
# Website pull request to [list the
release|http://flink.apache.org/downloads.html] merged
# Release announced on the user@ mailing list.
# Blog post published, if applicable.
# Release recorded in
[reporter.apache.org|https://reporter.apache.org/addrelease.html?flink].
# Release announced on social media.
# Completion declared on the dev@ mailing list.
# Update Homebrew: [https://docs.brew.sh/How-To-Open-a-Homebrew-Pull-Request]
(seems to be done automatically - at least for minor releases for both minor
and major releases)
# Updated the japicmp configuration
** corresponding SNAPSHOT branch japicmp reference version set to the just
released version, and API compatibiltity checks for {{@PublicEvolving}} was
enabled
** (minor version release only) master branch japicmp reference version set to
the just released version
** (minor version release only) master branch japicmp exclusions have been
cleared
# Update the list of previous version in {{docs/config.toml}} on the master
branch.
# Set {{show_outdated_warning: true}} in {{docs/config.toml}} in the branch of
the _now deprecated_ Flink version (i.e. 1.16 if 1.18.0 is released)
# Update stable and master alias in
[https://github.com/apache/flink/blob/master/.github/workflows/docs.yml]
# Open discussion thread for End of Life for Unsupported version (i.e. 1.16)
was:
Once the release has been finalized (FLINK-32920), the last step of the process
is to promote the release within the project and beyond. Please wait for 24h
after finalizing the release in accordance with the [ASF release
policy|http://www.apache.org/legal/release-policy.html#release-announcements].
*Final checklist to declare this issue resolved:*
# Website pull request to [list the
release|http://flink.apache.org/downloads.html] merged
# Release announced on the user@ mailing list.
# Blog post published, if applicable.
# Release recorded in
[reporter.apache.org|https://reporter.apache.org/addrelease.html?flink].
# Release announced on social media.
# Completion declared on the dev@ mailing list.
# Update Homebrew: [https://docs.brew.sh/How-To-Open-a-Homebrew-Pull-Request]
(seems to be done automatically - at least for minor releases for both minor
and major releases)
# Updated the japicmp configuration
** corresponding SNAPSHOT branch japicmp reference version set to the just
released version, and API compatibiltity checks for {{@PublicEvolving}} was
enabled
** (minor version release only) master branch japicmp reference version set to
the just released version
** (minor version release only) master branch japicmp exclusions have been
cleared
# Update the list of previous version in {{docs/config.toml}} on the master
branch.
# Set {{show_outdated_warning: true}} in {{docs/config.toml}} in the branch of
the _now deprecated_ Flink version (i.e. 1.16 if 1.18.0 is released)
# Update stable and master alias in
[https://github.com/apache/flink/blob/master/.github/workflows/docs.yml]
# Open discussion thread for End of Life for Unsupported version (i.e. 1.16)
> Promote release 1.18.1
> --
>
> Key: FLINK-33843
> URL: https://issues.apache.org/jira/browse/FLINK-33843
> Project: Flink
> Issue Type: New Feature
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
>
> Once the release has been finalized, the last step of the process is to
> promote the release within the project and beyond. Please wait for 24h after
> finalizing the release in accordance with the [ASF release
> policy|http://www.apache.org/legal/release-policy.html#release-announcements].
> *Final checklist to declare this issue resolved:*
> # Website pull request to [list the
> release|http://flink.apache.org/downloads.html] merged
> # Release announced on the user@ mailing list.
> # Blog post published, if applicable.
> # Release recorded in
> [reporter.apache.org|https://reporter.apache.org/addrelease.html?flink].
> # Release announced on social media.
> # Completion declared on the dev@ mailing list.
> # Update Homebrew:
> [https://docs.brew.sh/How-To-Open-a-Homebrew-Pull-Request] (seems to be done
> automatically - at least for minor releases for both minor and major
> releases)
> # Updated the japicmp configuration
> ** correspondi
[jira] [Created] (FLINK-33845) CLONE - Merge website pull request
Jing Ge created FLINK-33845: --- Summary: CLONE - Merge website pull request Key: FLINK-33845 URL: https://issues.apache.org/jira/browse/FLINK-33845 Project: Flink Issue Type: Sub-task Reporter: Jing Ge Merge the website pull request to [list the release|http://flink.apache.org/downloads.html]. Make sure to regenerate the website as well, as it isn't build automatically. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-33847) CLONE - Apache mailing lists announcements
Jing Ge created FLINK-33847:
---
Summary: CLONE - Apache mailing lists announcements
Key: FLINK-33847
URL: https://issues.apache.org/jira/browse/FLINK-33847
Project: Flink
Issue Type: Sub-task
Reporter: Jing Ge
Announce on the {{dev@}} mailing list that the release has been finished.
Announce on the release on the {{user@}} mailing list, listing major
improvements and contributions.
Announce the release on the [annou...@apache.org|mailto:annou...@apache.org]
mailing list.
{panel}
{panel}
|{{From: Release Manager}}
{{To: d...@flink.apache.org, u...@flink.apache.org, user...@flink.apache.org,
annou...@apache.org}}
{{Subject: [ANNOUNCE] Apache Flink 1.2.3 released}}
{{The Apache Flink community is very happy to announce the release of Apache
Flink 1.2.3, which is the third bugfix release for the Apache Flink 1.2
series.}}
{{Apache Flink® is an open-source stream processing framework for distributed,
high-performing, always-available, and accurate data streaming applications.}}
{{The release is available for download at:}}
{{[https://flink.apache.org/downloads.html]}}
{{Please check out the release blog post for an overview of the improvements
for this bugfix release:}}
{{}}
{{The full release notes are available in Jira:}}
{{}}
{{We would like to thank all contributors of the Apache Flink community who
made this release possible!}}
{{Feel free to reach out to the release managers (or respond to this thread)
with feedback on the release process. Our goal is to constantly improve the
release process. Feedback on what could be improved or things that didn't go so
well are appreciated.}}
{{Regards,}}
{{Release Manager}}|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33844) CLONE - Update japicmp configuration
Jing Ge created FLINK-33844:
---
Summary: CLONE - Update japicmp configuration
Key: FLINK-33844
URL: https://issues.apache.org/jira/browse/FLINK-33844
Project: Flink
Issue Type: Sub-task
Reporter: Jing Ge
Assignee: Sergey Nuyanzin
Fix For: 1.19.0, 1.18.1
Update the japicmp reference version and wipe exclusions / enable API
compatibility checks for {{@PublicEvolving}} APIs on the corresponding SNAPSHOT
branch with the {{update_japicmp_configuration.sh}} script (see below).
For a new major release (x.y.0), run the same command also on the master branch
for updating the japicmp reference version and removing out-dated exclusions in
the japicmp configuration.
Make sure that all Maven artifacts are already pushed to Maven Central.
Otherwise, there's a risk that CI fails due to missing reference artifacts.
{code:bash}
tools $ NEW_VERSION=$RELEASE_VERSION releasing/update_japicmp_configuration.sh
tools $ cd ..$ git add *$ git commit -m "Update japicmp configuration for
$RELEASE_VERSION" {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33849) CLONE - Update reference data for Migration Tests
Jing Ge created FLINK-33849:
---
Summary: CLONE - Update reference data for Migration Tests
Key: FLINK-33849
URL: https://issues.apache.org/jira/browse/FLINK-33849
Project: Flink
Issue Type: Sub-task
Reporter: Jing Ge
Assignee: Sergey Nuyanzin
Fix For: 1.19.0, 1.18.1
Update migration tests in master to cover migration from new version. Since
1.18, this step could be done automatically with the following steps. For more
information please refer to [this
page.|https://github.com/apache/flink/blob/master/flink-test-utils-parent/flink-migration-test-utils/README.md]
# {*}On the published release tag (e.g., release-1.16.0){*}, run
{panel}
{panel}
|{{$ mvn clean }}{{package}} {{{}-Pgenerate-migration-test-data
-Dgenerate.version={}}}{{{}1.16{}}} {{-nsu -Dfast -DskipTests}}|
The version (1.16 in the command above) should be replaced with the target one.
# Modify the content of the file
[apache/flink:flink-test-utils-parent/flink-migration-test-utils/src/main/resources/most_recently_published_version|https://github.com/apache/flink/blob/master/flink-test-utils-parent/flink-migration-test-utils/src/main/resources/most_recently_published_version]
to the latest version (it would be "v1_16" if sticking to the example where
1.16.0 was released).
# Commit the modification in step a and b with "{_}[release] Generate
reference data for state migration tests based on release-1.xx.0{_}" to the
corresponding release branch (e.g. {{release-1.16}} in our example), replace
"xx" with the actual version (in this example "16"). You should use the Jira
issue ID in case of [release] as the commit message's prefix if you have a
dedicated Jira issue for this task.
# Cherry-pick the commit to the master branch.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33846) CLONE - Remove outdated versions
Jing Ge created FLINK-33846:
---
Summary: CLONE - Remove outdated versions
Key: FLINK-33846
URL: https://issues.apache.org/jira/browse/FLINK-33846
Project: Flink
Issue Type: Sub-task
Reporter: Jing Ge
h4. dist.apache.org
For a new major release remove all release files older than 2 versions, e.g.,
when releasing 1.7, remove all releases <= 1.5.
For a new bugfix version remove all release files for previous bugfix releases
in the same series, e.g., when releasing 1.7.1, remove the 1.7.0 release.
# If you have not already, check out the Flink section of the {{release}}
repository on {{[dist.apache.org|http://dist.apache.org/]}} via Subversion. In
a fresh directory:
{code}
svn checkout https://dist.apache.org/repos/dist/release/flink --depth=immediates
cd flink
{code}
# Remove files for outdated releases and commit the changes.
{code}
svn remove flink-
svn commit
{code}
# Verify that files are
[removed|https://dist.apache.org/repos/dist/release/flink]
(!) Remember to remove the corresponding download links from the website.
h4. CI
Disable the cron job for the now-unsupported version from
(tools/azure-pipelines/[build-apache-repo.yml|https://github.com/apache/flink/blob/master/tools/azure-pipelines/build-apache-repo.yml])
in the respective branch.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [FLINK-33268][rest] Skip unknown fields in REST response deserialization [flink]
gaborgsomogyi commented on PR #23930: URL: https://github.com/apache/flink/pull/23930#issuecomment-1856093109 cc @gyfora -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (FLINK-31572) Other announcements
[
https://issues.apache.org/jira/browse/FLINK-31572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-31572:
Description:
h3. Recordkeeping
Use [reporter.apache.org|https://reporter.apache.org/addrelease.html?flink] to
seed the information about the release into future project reports.
(Note: Only PMC members have access report releases. If you do not have access,
ask on the mailing list for assistance.)
h3. Flink blog
Major or otherwise important releases should have a blog post. Write one if
needed for this particular release. Minor releases that don’t introduce new
major functionality don’t necessarily need to be blogged (see [flink-web PR
#581 for Flink 1.15.3|https://github.com/apache/flink-web/pull/581] as an
example for a minor release blog post).
Please make sure that the release notes of the documentation (see section
"Review and update documentation") are linked from the blog post of a major
release.
We usually include the names of all contributors in the announcement blog post.
Use the following command to get the list of contributors:
{code:java}
# first line is required to make sort first with uppercase and then lower
export LC_ALL=C
export FLINK_PREVIOUS_RELEASE_BRANCH=
export FLINK_CURRENT_RELEASE_BRANCH=
# e.g.
# export FLINK_PREVIOUS_RELEASE_BRANCH=release-1.16
# export FLINK_CURRENT_RELEASE_BRANCH=release-1.17
git log $(git merge-base master $FLINK_PREVIOUS_RELEASE_BRANCH)..$(git show-ref
--hash ${FLINK_CURRENT_RELEASE_BRANCH}) --pretty=format:"%an%n%cn" | sort -u |
paste -sd, | sed "s/\,/\, /g"
{code}
h3. Social media
Tweet, post on Facebook, LinkedIn, and other platforms. Ask other contributors
to do the same.
h3. Flink Release Wiki page
Add a summary of things that went well or that went not so well during the
release process. This can include feedback from contributors but also more
generic things like the release have taken longer than initially anticipated
(and why) to give a bit of context to the release process.
was:
h3. Recordkeeping
Use [reporter.apache.org|https://reporter.apache.org/addrelease.html?flink] to
seed the information about the release into future project reports.
(Note: Only PMC members have access report releases. If you do not have access,
ask on the mailing list for assistance.)
h3. Flink blog
Example:
https://flink.apache.org/2023/11/29/apache-flink-1.17.2-release-announcement/
h3. Social media
Tweet, post on Facebook, LinkedIn, and other platforms. Ask other contributors
to do the same.
h3. Flink Release Wiki page
Add a summary of things that went well or that went not so well during the
release process. This can include feedback from contributors but also more
generic things like the release have taken longer than initially anticipated
(and why) to give a bit of context to the release process.
> Other announcements
> ---
>
> Key: FLINK-31572
> URL: https://issues.apache.org/jira/browse/FLINK-31572
> Project: Flink
> Issue Type: Sub-task
>Reporter: Matthias Pohl
>Assignee: Qingsheng Ren
>Priority: Major
>
> h3. Recordkeeping
> Use [reporter.apache.org|https://reporter.apache.org/addrelease.html?flink]
> to seed the information about the release into future project reports.
> (Note: Only PMC members have access report releases. If you do not have
> access, ask on the mailing list for assistance.)
> h3. Flink blog
> Major or otherwise important releases should have a blog post. Write one if
> needed for this particular release. Minor releases that don’t introduce new
> major functionality don’t necessarily need to be blogged (see [flink-web PR
> #581 for Flink 1.15.3|https://github.com/apache/flink-web/pull/581] as an
> example for a minor release blog post).
> Please make sure that the release notes of the documentation (see section
> "Review and update documentation") are linked from the blog post of a major
> release.
> We usually include the names of all contributors in the announcement blog
> post. Use the following command to get the list of contributors:
> {code:java}
> # first line is required to make sort first with uppercase and then lower
> export LC_ALL=C
> export FLINK_PREVIOUS_RELEASE_BRANCH=
> export FLINK_CURRENT_RELEASE_BRANCH=
> # e.g.
> # export FLINK_PREVIOUS_RELEASE_BRANCH=release-1.16
> # export FLINK_CURRENT_RELEASE_BRANCH=release-1.17
> git log $(git merge-base master $FLINK_PREVIOUS_RELEASE_BRANCH)..$(git
> show-ref --hash ${FLINK_CURRENT_RELEASE_BRANCH}) --pretty=format:"%an%n%cn" |
> sort -u | paste -sd, | sed "s/\,/\, /g"
> {code}
> h3. Social media
> Tweet, post on Facebook, LinkedIn, and other platforms. Ask other
> contributors to do the same.
> h3. Flink Release Wiki page
> Add a summary of things that went well or that went not so well during the
> release process. This can include feedback f
[jira] [Assigned] (FLINK-31572) Other announcements
[ https://issues.apache.org/jira/browse/FLINK-31572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-31572: --- Assignee: Qingsheng Ren (was: Jing Ge) > Other announcements > --- > > Key: FLINK-31572 > URL: https://issues.apache.org/jira/browse/FLINK-31572 > Project: Flink > Issue Type: Sub-task >Reporter: Matthias Pohl >Assignee: Qingsheng Ren >Priority: Major > > h3. Recordkeeping > Use [reporter.apache.org|https://reporter.apache.org/addrelease.html?flink] > to seed the information about the release into future project reports. > (Note: Only PMC members have access report releases. If you do not have > access, ask on the mailing list for assistance.) > h3. Flink blog > Example: > https://flink.apache.org/2023/11/29/apache-flink-1.17.2-release-announcement/ > h3. Social media > Tweet, post on Facebook, LinkedIn, and other platforms. Ask other > contributors to do the same. > h3. Flink Release Wiki page > Add a summary of things that went well or that went not so well during the > release process. This can include feedback from contributors but also more > generic things like the release have taken longer than initially anticipated > (and why) to give a bit of context to the release process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FLINK-31572) Other announcements
[ https://issues.apache.org/jira/browse/FLINK-31572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-31572: --- Assignee: Jing Ge (was: Qingsheng Ren) > Other announcements > --- > > Key: FLINK-31572 > URL: https://issues.apache.org/jira/browse/FLINK-31572 > Project: Flink > Issue Type: Sub-task >Reporter: Matthias Pohl >Assignee: Jing Ge >Priority: Major > > h3. Recordkeeping > Use [reporter.apache.org|https://reporter.apache.org/addrelease.html?flink] > to seed the information about the release into future project reports. > (Note: Only PMC members have access report releases. If you do not have > access, ask on the mailing list for assistance.) > h3. Flink blog > Example: > https://flink.apache.org/2023/11/29/apache-flink-1.17.2-release-announcement/ > h3. Social media > Tweet, post on Facebook, LinkedIn, and other platforms. Ask other > contributors to do the same. > h3. Flink Release Wiki page > Add a summary of things that went well or that went not so well during the > release process. This can include feedback from contributors but also more > generic things like the release have taken longer than initially anticipated > (and why) to give a bit of context to the release process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-31572) Other announcements
[
https://issues.apache.org/jira/browse/FLINK-31572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-31572:
Description:
h3. Recordkeeping
Use [reporter.apache.org|https://reporter.apache.org/addrelease.html?flink] to
seed the information about the release into future project reports.
(Note: Only PMC members have access report releases. If you do not have access,
ask on the mailing list for assistance.)
h3. Flink blog
Example:
https://flink.apache.org/2023/11/29/apache-flink-1.17.2-release-announcement/
h3. Social media
Tweet, post on Facebook, LinkedIn, and other platforms. Ask other contributors
to do the same.
h3. Flink Release Wiki page
Add a summary of things that went well or that went not so well during the
release process. This can include feedback from contributors but also more
generic things like the release have taken longer than initially anticipated
(and why) to give a bit of context to the release process.
was:
h3. Recordkeeping
Use [reporter.apache.org|https://reporter.apache.org/addrelease.html?flink] to
seed the information about the release into future project reports.
(Note: Only PMC members have access report releases. If you do not have access,
ask on the mailing list for assistance.)
h3. Flink blog
Major or otherwise important releases should have a blog post. Write one if
needed for this particular release. Minor releases that don’t introduce new
major functionality don’t necessarily need to be blogged (see [flink-web PR
#581 for Flink 1.15.3|https://github.com/apache/flink-web/pull/581] as an
example for a minor release blog post).
Please make sure that the release notes of the documentation (see section
"Review and update documentation") are linked from the blog post of a major
release.
We usually include the names of all contributors in the announcement blog post.
Use the following command to get the list of contributors:
{code}
git log --pretty="%an%n%cn" .. | sort | uniq | tr "\n"
"," | sed 's/,/, /g'
{code}
h3. Social media
Tweet, post on Facebook, LinkedIn, and other platforms. Ask other contributors
to do the same.
h3. Flink Release Wiki page
Add a summary of things that went well or that went not so well during the
release process. This can include feedback from contributors but also more
generic things like the release have taken longer than initially anticipated
(and why) to give a bit of context to the release process.
> Other announcements
> ---
>
> Key: FLINK-31572
> URL: https://issues.apache.org/jira/browse/FLINK-31572
> Project: Flink
> Issue Type: Sub-task
>Reporter: Matthias Pohl
>Assignee: Qingsheng Ren
>Priority: Major
>
> h3. Recordkeeping
> Use [reporter.apache.org|https://reporter.apache.org/addrelease.html?flink]
> to seed the information about the release into future project reports.
> (Note: Only PMC members have access report releases. If you do not have
> access, ask on the mailing list for assistance.)
> h3. Flink blog
> Example:
> https://flink.apache.org/2023/11/29/apache-flink-1.17.2-release-announcement/
> h3. Social media
> Tweet, post on Facebook, LinkedIn, and other platforms. Ask other
> contributors to do the same.
> h3. Flink Release Wiki page
> Add a summary of things that went well or that went not so well during the
> release process. This can include feedback from contributors but also more
> generic things like the release have taken longer than initially anticipated
> (and why) to give a bit of context to the release process.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33840) Deploy artifacts to Maven Central Repository
[
https://issues.apache.org/jira/browse/FLINK-33840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33840:
Summary: Deploy artifacts to Maven Central Repository (was: CLONE - Deploy
artifacts to Maven Central Repository)
> Deploy artifacts to Maven Central Repository
>
>
> Key: FLINK-33840
> URL: https://issues.apache.org/jira/browse/FLINK-33840
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Qingsheng Ren
>Priority: Major
>
> Use the [Apache Nexus repository|https://repository.apache.org/] to release
> the staged binary artifacts to the Maven Central repository. In the Staging
> Repositories section, find the relevant release candidate orgapacheflink-XXX
> entry and click Release. Drop all other release candidates that are not being
> released.
> h3. Deploy source and binary releases to dist.apache.org
> Copy the source and binary releases from the dev repository to the release
> repository at [dist.apache.org|http://dist.apache.org/] using Subversion.
> {code:java}
> $ svn move -m "Release Flink ${RELEASE_VERSION}"
> https://dist.apache.org/repos/dist/dev/flink/flink-${RELEASE_VERSION}-rc${RC_NUM}
> https://dist.apache.org/repos/dist/release/flink/flink-${RELEASE_VERSION}
> {code}
> (Note: Only PMC members have access to the release repository. If you do not
> have access, ask on the mailing list for assistance.)
> h3. Remove old release candidates from
> [dist.apache.org|http://dist.apache.org/]
> Remove the old release candidates from
> [https://dist.apache.org/repos/dist/dev/flink] using Subversion.
> {code:java}
> $ svn checkout https://dist.apache.org/repos/dist/dev/flink --depth=immediates
> $ cd flink
> $ svn remove flink-${RELEASE_VERSION}-rc*
> $ svn commit -m "Remove old release candidates for Apache Flink
> ${RELEASE_VERSION}
> {code}
>
>
> h3. Expectations
> * Maven artifacts released and indexed in the [Maven Central
> Repository|https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.flink%22]
> (usually takes about a day to show up)
> * Source & binary distributions available in the release repository of
> [https://dist.apache.org/repos/dist/release/flink/]
> * Dev repository [https://dist.apache.org/repos/dist/dev/flink/] is empty
> * Website contains links to new release binaries and sources in download page
> * (for minor version updates) the front page references the correct new
> major release version and directs to the correct link
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33839) Deploy Python artifacts to PyPI
[
https://issues.apache.org/jira/browse/FLINK-33839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33839:
Summary: Deploy Python artifacts to PyPI (was: CLONE - Deploy Python
artifacts to PyPI)
> Deploy Python artifacts to PyPI
> ---
>
> Key: FLINK-33839
> URL: https://issues.apache.org/jira/browse/FLINK-33839
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> Release manager should create a PyPI account and ask the PMC add this account
> to pyflink collaborator list with Maintainer role (The PyPI admin account
> info can be found here. NOTE, only visible to PMC members) to deploy the
> Python artifacts to PyPI. The artifacts could be uploaded using
> twine([https://pypi.org/project/twine/]). To install twine, just run:
> {code:java}
> pip install --upgrade twine==1.12.0
> {code}
> Download the python artifacts from dist.apache.org and upload it to pypi.org:
> {code:java}
> svn checkout
> https://dist.apache.org/repos/dist/dev/flink/flink-${RELEASE_VERSION}-rc${RC_NUM}
> cd flink-${RELEASE_VERSION}-rc${RC_NUM}
>
> cd python
>
> #uploads wheels
> for f in *.whl; do twine upload --repository-url
> https://upload.pypi.org/legacy/ $f $f.asc; done
>
> #upload source packages
> twine upload --repository-url https://upload.pypi.org/legacy/
> apache-flink-libraries-${RELEASE_VERSION}.tar.gz
> apache-flink-libraries-${RELEASE_VERSION}.tar.gz.asc
>
> twine upload --repository-url https://upload.pypi.org/legacy/
> apache-flink-${RELEASE_VERSION}.tar.gz
> apache-flink-${RELEASE_VERSION}.tar.gz.asc
> {code}
> If upload failed or incorrect for some reason (e.g. network transmission
> problem), you need to delete the uploaded release package of the same version
> (if exists) and rename the artifact to
> {{{}apache-flink-${RELEASE_VERSION}.post0.tar.gz{}}}, then re-upload.
> (!) Note: re-uploading to pypi.org must be avoided as much as possible
> because it will cause some irreparable problems. If that happens, users
> cannot install the apache-flink package by explicitly specifying the package
> version, i.e. the following command "pip install
> apache-flink==${RELEASE_VERSION}" will fail. Instead they have to run "pip
> install apache-flink" or "pip install apache-flink==${RELEASE_VERSION}.post0"
> to install the apache-flink package.
>
>
> h3. Expectations
> * Python artifacts released and indexed in the
> [PyPI|https://pypi.org/project/apache-flink/] Repository
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33841) Create Git tag and mark version as released in Jira
[
https://issues.apache.org/jira/browse/FLINK-33841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33841:
Summary: Create Git tag and mark version as released in Jira (was: CLONE -
Create Git tag and mark version as released in Jira)
> Create Git tag and mark version as released in Jira
> ---
>
> Key: FLINK-33841
> URL: https://issues.apache.org/jira/browse/FLINK-33841
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Qingsheng Ren
>Priority: Major
>
> Create and push a new Git tag for the released version by copying the tag for
> the final release candidate, as follows:
> {code:java}
> $ git tag -s "release-${RELEASE_VERSION}" refs/tags/${TAG}^{} -m "Release
> Flink ${RELEASE_VERSION}"
> $ git push refs/tags/release-${RELEASE_VERSION}
> {code}
> In JIRA, inside [version
> management|https://issues.apache.org/jira/plugins/servlet/project-config/FLINK/versions],
> hover over the current release and a settings menu will appear. Click
> Release, and select today’s date.
> (Note: Only PMC members have access to the project administration. If you do
> not have access, ask on the mailing list for assistance.)
> If PRs have been merged to the release branch after the the last release
> candidate was tagged, make sure that the corresponding Jira tickets have the
> correct Fix Version set.
>
>
> h3. Expectations
> * Release tagged in the source code repository
> * Release version finalized in JIRA. (Note: Not all committers have
> administrator access to JIRA. If you end up getting permissions errors ask on
> the mailing list for assistance)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-33839) CLONE - Deploy Python artifacts to PyPI
[
https://issues.apache.org/jira/browse/FLINK-33839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-33839:
---
Assignee: Jing Ge (was: Qingsheng Ren)
> CLONE - Deploy Python artifacts to PyPI
> ---
>
> Key: FLINK-33839
> URL: https://issues.apache.org/jira/browse/FLINK-33839
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> Release manager should create a PyPI account and ask the PMC add this account
> to pyflink collaborator list with Maintainer role (The PyPI admin account
> info can be found here. NOTE, only visible to PMC members) to deploy the
> Python artifacts to PyPI. The artifacts could be uploaded using
> twine([https://pypi.org/project/twine/]). To install twine, just run:
> {code:java}
> pip install --upgrade twine==1.12.0
> {code}
> Download the python artifacts from dist.apache.org and upload it to pypi.org:
> {code:java}
> svn checkout
> https://dist.apache.org/repos/dist/dev/flink/flink-${RELEASE_VERSION}-rc${RC_NUM}
> cd flink-${RELEASE_VERSION}-rc${RC_NUM}
>
> cd python
>
> #uploads wheels
> for f in *.whl; do twine upload --repository-url
> https://upload.pypi.org/legacy/ $f $f.asc; done
>
> #upload source packages
> twine upload --repository-url https://upload.pypi.org/legacy/
> apache-flink-libraries-${RELEASE_VERSION}.tar.gz
> apache-flink-libraries-${RELEASE_VERSION}.tar.gz.asc
>
> twine upload --repository-url https://upload.pypi.org/legacy/
> apache-flink-${RELEASE_VERSION}.tar.gz
> apache-flink-${RELEASE_VERSION}.tar.gz.asc
> {code}
> If upload failed or incorrect for some reason (e.g. network transmission
> problem), you need to delete the uploaded release package of the same version
> (if exists) and rename the artifact to
> {{{}apache-flink-${RELEASE_VERSION}.post0.tar.gz{}}}, then re-upload.
> (!) Note: re-uploading to pypi.org must be avoided as much as possible
> because it will cause some irreparable problems. If that happens, users
> cannot install the apache-flink package by explicitly specifying the package
> version, i.e. the following command "pip install
> apache-flink==${RELEASE_VERSION}" will fail. Instead they have to run "pip
> install apache-flink" or "pip install apache-flink==${RELEASE_VERSION}.post0"
> to install the apache-flink package.
>
>
> h3. Expectations
> * Python artifacts released and indexed in the
> [PyPI|https://pypi.org/project/apache-flink/] Repository
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33842) Publish the Dockerfiles for the new release
[ https://issues.apache.org/jira/browse/FLINK-33842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge updated FLINK-33842: Summary: Publish the Dockerfiles for the new release (was: CLONE - Publish the Dockerfiles for the new release) > Publish the Dockerfiles for the new release > --- > > Key: FLINK-33842 > URL: https://issues.apache.org/jira/browse/FLINK-33842 > Project: Flink > Issue Type: Sub-task >Reporter: Jing Ge >Assignee: Matthias Pohl >Priority: Major > Labels: pull-request-available > > Note: the official Dockerfiles fetch the binary distribution of the target > Flink version from an Apache mirror. After publishing the binary release > artifacts, mirrors can take some hours to start serving the new artifacts, so > you may want to wait to do this step until you are ready to continue with the > "Promote the release" steps in the follow-up Jira. > Follow the [release instructions in the flink-docker > repo|https://github.com/apache/flink-docker#release-workflow] to build the > new Dockerfiles and send an updated manifest to Docker Hub so the new images > are built and published. > > > h3. Expectations > * Dockerfiles in [flink-docker|https://github.com/apache/flink-docker] > updated for the new Flink release and pull request opened on the Docker > official-images with an updated manifest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FLINK-33838) Finalize release 1.18.1
[ https://issues.apache.org/jira/browse/FLINK-33838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-33838: --- Assignee: Jing Ge (was: Qingsheng Ren) > Finalize release 1.18.1 > --- > > Key: FLINK-33838 > URL: https://issues.apache.org/jira/browse/FLINK-33838 > Project: Flink > Issue Type: New Feature >Affects Versions: 1.17.0 >Reporter: Jing Ge >Assignee: Jing Ge >Priority: Major > > Once the release candidate has been reviewed and approved by the community, > the release should be finalized. This involves the final deployment of the > release candidate to the release repositories, merging of the website > changes, etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-33838) Finalize release 1.18.1
[ https://issues.apache.org/jira/browse/FLINK-33838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge updated FLINK-33838: Affects Version/s: 1.18.0 (was: 1.17.0) > Finalize release 1.18.1 > --- > > Key: FLINK-33838 > URL: https://issues.apache.org/jira/browse/FLINK-33838 > Project: Flink > Issue Type: New Feature >Affects Versions: 1.18.0 >Reporter: Jing Ge >Assignee: Jing Ge >Priority: Major > > Once the release candidate has been reviewed and approved by the community, > the release should be finalized. This involves the final deployment of the > release candidate to the release repositories, merging of the website > changes, etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-33840) CLONE - Deploy artifacts to Maven Central Repository
Jing Ge created FLINK-33840:
---
Summary: CLONE - Deploy artifacts to Maven Central Repository
Key: FLINK-33840
URL: https://issues.apache.org/jira/browse/FLINK-33840
Project: Flink
Issue Type: Sub-task
Reporter: Jing Ge
Assignee: Qingsheng Ren
Use the [Apache Nexus repository|https://repository.apache.org/] to release the
staged binary artifacts to the Maven Central repository. In the Staging
Repositories section, find the relevant release candidate orgapacheflink-XXX
entry and click Release. Drop all other release candidates that are not being
released.
h3. Deploy source and binary releases to dist.apache.org
Copy the source and binary releases from the dev repository to the release
repository at [dist.apache.org|http://dist.apache.org/] using Subversion.
{code:java}
$ svn move -m "Release Flink ${RELEASE_VERSION}"
https://dist.apache.org/repos/dist/dev/flink/flink-${RELEASE_VERSION}-rc${RC_NUM}
https://dist.apache.org/repos/dist/release/flink/flink-${RELEASE_VERSION}
{code}
(Note: Only PMC members have access to the release repository. If you do not
have access, ask on the mailing list for assistance.)
h3. Remove old release candidates from [dist.apache.org|http://dist.apache.org/]
Remove the old release candidates from
[https://dist.apache.org/repos/dist/dev/flink] using Subversion.
{code:java}
$ svn checkout https://dist.apache.org/repos/dist/dev/flink --depth=immediates
$ cd flink
$ svn remove flink-${RELEASE_VERSION}-rc*
$ svn commit -m "Remove old release candidates for Apache Flink
${RELEASE_VERSION}
{code}
h3. Expectations
* Maven artifacts released and indexed in the [Maven Central
Repository|https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.flink%22]
(usually takes about a day to show up)
* Source & binary distributions available in the release repository of
[https://dist.apache.org/repos/dist/release/flink/]
* Dev repository [https://dist.apache.org/repos/dist/dev/flink/] is empty
* Website contains links to new release binaries and sources in download page
* (for minor version updates) the front page references the correct new major
release version and directs to the correct link
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33842) CLONE - Publish the Dockerfiles for the new release
Jing Ge created FLINK-33842: --- Summary: CLONE - Publish the Dockerfiles for the new release Key: FLINK-33842 URL: https://issues.apache.org/jira/browse/FLINK-33842 Project: Flink Issue Type: Sub-task Reporter: Jing Ge Assignee: Matthias Pohl Note: the official Dockerfiles fetch the binary distribution of the target Flink version from an Apache mirror. After publishing the binary release artifacts, mirrors can take some hours to start serving the new artifacts, so you may want to wait to do this step until you are ready to continue with the "Promote the release" steps in the follow-up Jira. Follow the [release instructions in the flink-docker repo|https://github.com/apache/flink-docker#release-workflow] to build the new Dockerfiles and send an updated manifest to Docker Hub so the new images are built and published. h3. Expectations * Dockerfiles in [flink-docker|https://github.com/apache/flink-docker] updated for the new Flink release and pull request opened on the Docker official-images with an updated manifest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-33841) CLONE - Create Git tag and mark version as released in Jira
Jing Ge created FLINK-33841:
---
Summary: CLONE - Create Git tag and mark version as released in
Jira
Key: FLINK-33841
URL: https://issues.apache.org/jira/browse/FLINK-33841
Project: Flink
Issue Type: Sub-task
Reporter: Jing Ge
Assignee: Qingsheng Ren
Create and push a new Git tag for the released version by copying the tag for
the final release candidate, as follows:
{code:java}
$ git tag -s "release-${RELEASE_VERSION}" refs/tags/${TAG}^{} -m "Release Flink
${RELEASE_VERSION}"
$ git push refs/tags/release-${RELEASE_VERSION}
{code}
In JIRA, inside [version
management|https://issues.apache.org/jira/plugins/servlet/project-config/FLINK/versions],
hover over the current release and a settings menu will appear. Click Release,
and select today’s date.
(Note: Only PMC members have access to the project administration. If you do
not have access, ask on the mailing list for assistance.)
If PRs have been merged to the release branch after the the last release
candidate was tagged, make sure that the corresponding Jira tickets have the
correct Fix Version set.
h3. Expectations
* Release tagged in the source code repository
* Release version finalized in JIRA. (Note: Not all committers have
administrator access to JIRA. If you end up getting permissions errors ask on
the mailing list for assistance)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33839) CLONE - Deploy Python artifacts to PyPI
Jing Ge created FLINK-33839:
---
Summary: CLONE - Deploy Python artifacts to PyPI
Key: FLINK-33839
URL: https://issues.apache.org/jira/browse/FLINK-33839
Project: Flink
Issue Type: Sub-task
Reporter: Jing Ge
Assignee: Qingsheng Ren
Release manager should create a PyPI account and ask the PMC add this account
to pyflink collaborator list with Maintainer role (The PyPI admin account info
can be found here. NOTE, only visible to PMC members) to deploy the Python
artifacts to PyPI. The artifacts could be uploaded using
twine([https://pypi.org/project/twine/]). To install twine, just run:
{code:java}
pip install --upgrade twine==1.12.0
{code}
Download the python artifacts from dist.apache.org and upload it to pypi.org:
{code:java}
svn checkout
https://dist.apache.org/repos/dist/dev/flink/flink-${RELEASE_VERSION}-rc${RC_NUM}
cd flink-${RELEASE_VERSION}-rc${RC_NUM}
cd python
#uploads wheels
for f in *.whl; do twine upload --repository-url
https://upload.pypi.org/legacy/ $f $f.asc; done
#upload source packages
twine upload --repository-url https://upload.pypi.org/legacy/
apache-flink-libraries-${RELEASE_VERSION}.tar.gz
apache-flink-libraries-${RELEASE_VERSION}.tar.gz.asc
twine upload --repository-url https://upload.pypi.org/legacy/
apache-flink-${RELEASE_VERSION}.tar.gz
apache-flink-${RELEASE_VERSION}.tar.gz.asc
{code}
If upload failed or incorrect for some reason (e.g. network transmission
problem), you need to delete the uploaded release package of the same version
(if exists) and rename the artifact to
{{{}apache-flink-${RELEASE_VERSION}.post0.tar.gz{}}}, then re-upload.
(!) Note: re-uploading to pypi.org must be avoided as much as possible because
it will cause some irreparable problems. If that happens, users cannot install
the apache-flink package by explicitly specifying the package version, i.e. the
following command "pip install apache-flink==${RELEASE_VERSION}" will fail.
Instead they have to run "pip install apache-flink" or "pip install
apache-flink==${RELEASE_VERSION}.post0" to install the apache-flink package.
h3. Expectations
* Python artifacts released and indexed in the
[PyPI|https://pypi.org/project/apache-flink/] Repository
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33838) Finalize release 1.18.1
Jing Ge created FLINK-33838: --- Summary: Finalize release 1.18.1 Key: FLINK-33838 URL: https://issues.apache.org/jira/browse/FLINK-33838 Project: Flink Issue Type: New Feature Affects Versions: 1.17.0 Reporter: Jing Ge Assignee: Qingsheng Ren Once the release candidate has been reviewed and approved by the community, the release should be finalized. This involves the final deployment of the release candidate to the release repositories, merging of the website changes, etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-33833) Build Release Candidate: 1.18.1-rc1
[
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-33824) Prepare Flink 1.18.1 Release
[
https://issues.apache.org/jira/browse/FLINK-33824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33824:
Fix Version/s: (was: 1.18.1)
> Prepare Flink 1.18.1 Release
>
>
> Key: FLINK-33824
> URL: https://issues.apache.org/jira/browse/FLINK-33824
> Project: Flink
> Issue Type: New Feature
> Components: Release System
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> 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.18.1"
> SHORT_RELEASE_VERSION="1.18"
> CURRENT_SNAPSHOT_VERSION="$SHORT_RELEASE_VERSION-SNAPSHOT"
> {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-33831) Checkout the release branch
[
https://issues.apache.org/jira/browse/FLINK-33831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33831:
Fix Version/s: (was: 1.18.1)
> Checkout the release branch
> ---
>
> Key: FLINK-33831
> URL: https://issues.apache.org/jira/browse/FLINK-33831
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> If you are doing a new minor release, you need to update Flink version in the
> following repositories and the [AzureCI project
> configuration|https://dev.azure.com/apache-flink/apache-flink/]:
> * [apache/flink|https://github.com/apache/flink]
> * [apache/flink-docker|https://github.com/apache/flink-docker]
> * [apache/flink-benchmarks|https://github.com/apache/flink-benchmarks]
> Patch releases don't require the these repositories to be touched. Simply
> checkout the already existing branch for that version:
> {code:java}
> $ git checkout release-$SHORT_RELEASE_VERSION
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33836) Propose a pull request for website updates
[
https://issues.apache.org/jira/browse/FLINK-33836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33836:
Fix Version/s: (was: 1.18.1)
> Propose a pull request for website updates
> --
>
> Key: FLINK-33836
> URL: https://issues.apache.org/jira/browse/FLINK-33836
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
>
> The final step of building the candidate is to propose a website pull request
> containing the following changes:
> # update
> [apache/flink-web:_config.yml|https://github.com/apache/flink-web/blob/asf-site/_config.yml]
> ## update {{FLINK_VERSION_STABLE}} and {{FLINK_VERSION_STABLE_SHORT}} as
> required
> ## update version references in quickstarts ({{{}q/{}}} directory) as
> required
> ## (major only) add a new entry to {{flink_releases}} for the release
> binaries and sources
> ## (minor only) update the entry for the previous release in the series in
> {{flink_releases}}
> ### Please pay notice to the ids assigned to the download entries. They
> should be unique and reflect their corresponding version number.
> ## add a new entry to {{release_archive.flink}}
> # add a blog post announcing the release in _posts
> # add a organized release notes page under docs/content/release-notes and
> docs/content.zh/release-notes (like
> [https://nightlies.apache.org/flink/flink-docs-release-1.15/release-notes/flink-1.15/]).
> The page is based on the non-empty release notes collected from the issues,
> and only the issues that affect existing users should be included (e.g.,
> instead of new functionality). It should be in a separate PR since it would
> be merged to the flink project.
> (!) Don’t merge the PRs before finalizing the release.
>
>
> h3. Expectations
> * Website pull request proposed to list the
> [release|http://flink.apache.org/downloads.html]
> * (major only) Check {{docs/config.toml}} to ensure that
> ** the version constants refer to the new version
> ** the {{baseurl}} does not point to {{flink-docs-master}} but
> {{flink-docs-release-X.Y}} instead
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33837) Vote on the release candidate
[
https://issues.apache.org/jira/browse/FLINK-33837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33837:
Fix Version/s: (was: 1.18.1)
> Vote on the release candidate
> -
>
> Key: FLINK-33837
> URL: https://issues.apache.org/jira/browse/FLINK-33837
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> Once you have built and individually reviewed the release candidate, please
> share it for the community-wide review. Please review foundation-wide [voting
> guidelines|http://www.apache.org/foundation/voting.html] for more information.
> Start the review-and-vote thread on the dev@ mailing list. Here’s an email
> template; please adjust as you see fit.
> {quote}From: Release Manager
> To: d...@flink.apache.org
> Subject: [VOTE] Release 1.2.3, release candidate #3
> Hi everyone,
> Please review and vote on the release candidate #3 for the version 1.2.3, as
> follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
> The complete staging area is available for your review, which includes:
> * JIRA release notes [1],
> * the official Apache source release and binary convenience releases to be
> deployed to dist.apache.org [2], which are signed with the key with
> fingerprint [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "release-1.2.3-rc3" [5],
> * website pull request listing the new release and adding announcement blog
> post [6].
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
> Thanks,
> Release Manager
> [1] link
> [2] link
> [3] [https://dist.apache.org/repos/dist/release/flink/KEYS]
> [4] link
> [5] link
> [6] link
> {quote}
> *If there are any issues found in the release candidate, reply on the vote
> thread to cancel the vote.* There’s no need to wait 72 hours. Proceed to the
> Fix Issues step below and address the problem. However, some issues don’t
> require cancellation. For example, if an issue is found in the website pull
> request, just correct it on the spot and the vote can continue as-is.
> For cancelling a release, the release manager needs to send an email to the
> release candidate thread, stating that the release candidate is officially
> cancelled. Next, all artifacts created specifically for the RC in the
> previous steps need to be removed:
> * Delete the staging repository in Nexus
> * Remove the source / binary RC files from dist.apache.org
> * Delete the source code tag in git
> *If there are no issues, reply on the vote thread to close the voting.* Then,
> tally the votes in a separate email. Here’s an email template; please adjust
> as you see fit.
> {quote}From: Release Manager
> To: d...@flink.apache.org
> Subject: [RESULT] [VOTE] Release 1.2.3, release candidate #3
> I'm happy to announce that we have unanimously approved this release.
> There are XXX approving votes, XXX of which are binding:
> * approver 1
> * approver 2
> * approver 3
> * approver 4
> There are no disapproving votes.
> Thanks everyone!
> {quote}
>
>
> h3. Expectations
> * Community votes to release the proposed candidate, with at least three
> approving PMC votes
> Any issues that are raised till the vote is over should be either resolved or
> moved into the next release (if applicable).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [FLINK-33268][rest] Skip unknown fields in REST response deserialization [flink]
flinkbot commented on PR #23930: URL: https://github.com/apache/flink/pull/23930#issuecomment-1856059558 ## CI report: * cdef4fd4b4b21dad5c1ae52b9fd2a17ddb101a7f UNKNOWN Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run azure` re-run the last Azure build -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (FLINK-33833) Build Release Candidate: 1.18.1-rc1
[
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
[
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)
[jira] [Assigned] (FLINK-33837) Vote on the release candidate
[
https://issues.apache.org/jira/browse/FLINK-33837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-33837:
---
Assignee: Jing Ge (was: Qingsheng Ren)
> Vote on the release candidate
> -
>
> Key: FLINK-33837
> URL: https://issues.apache.org/jira/browse/FLINK-33837
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.17.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Fix For: 1.17.0
>
>
> Once you have built and individually reviewed the release candidate, please
> share it for the community-wide review. Please review foundation-wide [voting
> guidelines|http://www.apache.org/foundation/voting.html] for more information.
> Start the review-and-vote thread on the dev@ mailing list. Here’s an email
> template; please adjust as you see fit.
> {quote}From: Release Manager
> To: d...@flink.apache.org
> Subject: [VOTE] Release 1.2.3, release candidate #3
> Hi everyone,
> Please review and vote on the release candidate #3 for the version 1.2.3, as
> follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
> The complete staging area is available for your review, which includes:
> * JIRA release notes [1],
> * the official Apache source release and binary convenience releases to be
> deployed to dist.apache.org [2], which are signed with the key with
> fingerprint [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "release-1.2.3-rc3" [5],
> * website pull request listing the new release and adding announcement blog
> post [6].
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
> Thanks,
> Release Manager
> [1] link
> [2] link
> [3] [https://dist.apache.org/repos/dist/release/flink/KEYS]
> [4] link
> [5] link
> [6] link
> {quote}
> *If there are any issues found in the release candidate, reply on the vote
> thread to cancel the vote.* There’s no need to wait 72 hours. Proceed to the
> Fix Issues step below and address the problem. However, some issues don’t
> require cancellation. For example, if an issue is found in the website pull
> request, just correct it on the spot and the vote can continue as-is.
> For cancelling a release, the release manager needs to send an email to the
> release candidate thread, stating that the release candidate is officially
> cancelled. Next, all artifacts created specifically for the RC in the
> previous steps need to be removed:
> * Delete the staging repository in Nexus
> * Remove the source / binary RC files from dist.apache.org
> * Delete the source code tag in git
> *If there are no issues, reply on the vote thread to close the voting.* Then,
> tally the votes in a separate email. Here’s an email template; please adjust
> as you see fit.
> {quote}From: Release Manager
> To: d...@flink.apache.org
> Subject: [RESULT] [VOTE] Release 1.2.3, release candidate #3
> I'm happy to announce that we have unanimously approved this release.
> There are XXX approving votes, XXX of which are binding:
> * approver 1
> * approver 2
> * approver 3
> * approver 4
> There are no disapproving votes.
> Thanks everyone!
> {quote}
>
>
> h3. Expectations
> * Community votes to release the proposed candidate, with at least three
> approving PMC votes
> Any issues that are raised till the vote is over should be either resolved or
> moved into the next release (if applicable).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33837) Vote on the release candidate
[
https://issues.apache.org/jira/browse/FLINK-33837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33837:
Fix Version/s: 1.18.1
(was: 1.17.0)
> Vote on the release candidate
> -
>
> Key: FLINK-33837
> URL: https://issues.apache.org/jira/browse/FLINK-33837
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Fix For: 1.18.1
>
>
> Once you have built and individually reviewed the release candidate, please
> share it for the community-wide review. Please review foundation-wide [voting
> guidelines|http://www.apache.org/foundation/voting.html] for more information.
> Start the review-and-vote thread on the dev@ mailing list. Here’s an email
> template; please adjust as you see fit.
> {quote}From: Release Manager
> To: d...@flink.apache.org
> Subject: [VOTE] Release 1.2.3, release candidate #3
> Hi everyone,
> Please review and vote on the release candidate #3 for the version 1.2.3, as
> follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
> The complete staging area is available for your review, which includes:
> * JIRA release notes [1],
> * the official Apache source release and binary convenience releases to be
> deployed to dist.apache.org [2], which are signed with the key with
> fingerprint [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "release-1.2.3-rc3" [5],
> * website pull request listing the new release and adding announcement blog
> post [6].
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
> Thanks,
> Release Manager
> [1] link
> [2] link
> [3] [https://dist.apache.org/repos/dist/release/flink/KEYS]
> [4] link
> [5] link
> [6] link
> {quote}
> *If there are any issues found in the release candidate, reply on the vote
> thread to cancel the vote.* There’s no need to wait 72 hours. Proceed to the
> Fix Issues step below and address the problem. However, some issues don’t
> require cancellation. For example, if an issue is found in the website pull
> request, just correct it on the spot and the vote can continue as-is.
> For cancelling a release, the release manager needs to send an email to the
> release candidate thread, stating that the release candidate is officially
> cancelled. Next, all artifacts created specifically for the RC in the
> previous steps need to be removed:
> * Delete the staging repository in Nexus
> * Remove the source / binary RC files from dist.apache.org
> * Delete the source code tag in git
> *If there are no issues, reply on the vote thread to close the voting.* Then,
> tally the votes in a separate email. Here’s an email template; please adjust
> as you see fit.
> {quote}From: Release Manager
> To: d...@flink.apache.org
> Subject: [RESULT] [VOTE] Release 1.2.3, release candidate #3
> I'm happy to announce that we have unanimously approved this release.
> There are XXX approving votes, XXX of which are binding:
> * approver 1
> * approver 2
> * approver 3
> * approver 4
> There are no disapproving votes.
> Thanks everyone!
> {quote}
>
>
> h3. Expectations
> * Community votes to release the proposed candidate, with at least three
> approving PMC votes
> Any issues that are raised till the vote is over should be either resolved or
> moved into the next release (if applicable).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-33268) Flink REST API response parsing throws exception on new fields
[ https://issues.apache.org/jira/browse/FLINK-33268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Somogyi reassigned FLINK-33268: - Assignee: Gabor Somogyi > Flink REST API response parsing throws exception on new fields > -- > > Key: FLINK-33268 > URL: https://issues.apache.org/jira/browse/FLINK-33268 > Project: Flink > Issue Type: Improvement > Components: Runtime / REST >Affects Versions: 1.19.0 >Reporter: Gabor Somogyi >Assignee: Gabor Somogyi >Priority: Major > Labels: pull-request-available > > At the moment Flink is not ignoring unknown fields when parsing REST > responses. An example for such a class is JobDetailsInfo but this applies to > all others. It would be good to add this support to increase compatibility. > The real life use-case is when the Flink k8s operator wants to handle 2 jobs > with 2 different Flink versions where the newer version has added a new field > to any REST response. Such case the operator gets an exception when for > example it tries to poll the job details with the additional field. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-33837) Vote on the release candidate
[
https://issues.apache.org/jira/browse/FLINK-33837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33837:
Affects Version/s: 1.18.0
(was: 1.17.0)
> Vote on the release candidate
> -
>
> Key: FLINK-33837
> URL: https://issues.apache.org/jira/browse/FLINK-33837
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Fix For: 1.17.0
>
>
> Once you have built and individually reviewed the release candidate, please
> share it for the community-wide review. Please review foundation-wide [voting
> guidelines|http://www.apache.org/foundation/voting.html] for more information.
> Start the review-and-vote thread on the dev@ mailing list. Here’s an email
> template; please adjust as you see fit.
> {quote}From: Release Manager
> To: d...@flink.apache.org
> Subject: [VOTE] Release 1.2.3, release candidate #3
> Hi everyone,
> Please review and vote on the release candidate #3 for the version 1.2.3, as
> follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
> The complete staging area is available for your review, which includes:
> * JIRA release notes [1],
> * the official Apache source release and binary convenience releases to be
> deployed to dist.apache.org [2], which are signed with the key with
> fingerprint [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "release-1.2.3-rc3" [5],
> * website pull request listing the new release and adding announcement blog
> post [6].
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
> Thanks,
> Release Manager
> [1] link
> [2] link
> [3] [https://dist.apache.org/repos/dist/release/flink/KEYS]
> [4] link
> [5] link
> [6] link
> {quote}
> *If there are any issues found in the release candidate, reply on the vote
> thread to cancel the vote.* There’s no need to wait 72 hours. Proceed to the
> Fix Issues step below and address the problem. However, some issues don’t
> require cancellation. For example, if an issue is found in the website pull
> request, just correct it on the spot and the vote can continue as-is.
> For cancelling a release, the release manager needs to send an email to the
> release candidate thread, stating that the release candidate is officially
> cancelled. Next, all artifacts created specifically for the RC in the
> previous steps need to be removed:
> * Delete the staging repository in Nexus
> * Remove the source / binary RC files from dist.apache.org
> * Delete the source code tag in git
> *If there are no issues, reply on the vote thread to close the voting.* Then,
> tally the votes in a separate email. Here’s an email template; please adjust
> as you see fit.
> {quote}From: Release Manager
> To: d...@flink.apache.org
> Subject: [RESULT] [VOTE] Release 1.2.3, release candidate #3
> I'm happy to announce that we have unanimously approved this release.
> There are XXX approving votes, XXX of which are binding:
> * approver 1
> * approver 2
> * approver 3
> * approver 4
> There are no disapproving votes.
> Thanks everyone!
> {quote}
>
>
> h3. Expectations
> * Community votes to release the proposed candidate, with at least three
> approving PMC votes
> Any issues that are raised till the vote is over should be either resolved or
> moved into the next release (if applicable).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33837) Vote on the release candidate
[
https://issues.apache.org/jira/browse/FLINK-33837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33837:
Summary: Vote on the release candidate (was: CLONE - Vote on the release
candidate)
> Vote on the release candidate
> -
>
> Key: FLINK-33837
> URL: https://issues.apache.org/jira/browse/FLINK-33837
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.17.0
>Reporter: Jing Ge
>Assignee: Qingsheng Ren
>Priority: Major
> Fix For: 1.17.0
>
>
> Once you have built and individually reviewed the release candidate, please
> share it for the community-wide review. Please review foundation-wide [voting
> guidelines|http://www.apache.org/foundation/voting.html] for more information.
> Start the review-and-vote thread on the dev@ mailing list. Here’s an email
> template; please adjust as you see fit.
> {quote}From: Release Manager
> To: d...@flink.apache.org
> Subject: [VOTE] Release 1.2.3, release candidate #3
> Hi everyone,
> Please review and vote on the release candidate #3 for the version 1.2.3, as
> follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
> The complete staging area is available for your review, which includes:
> * JIRA release notes [1],
> * the official Apache source release and binary convenience releases to be
> deployed to dist.apache.org [2], which are signed with the key with
> fingerprint [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "release-1.2.3-rc3" [5],
> * website pull request listing the new release and adding announcement blog
> post [6].
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
> Thanks,
> Release Manager
> [1] link
> [2] link
> [3] [https://dist.apache.org/repos/dist/release/flink/KEYS]
> [4] link
> [5] link
> [6] link
> {quote}
> *If there are any issues found in the release candidate, reply on the vote
> thread to cancel the vote.* There’s no need to wait 72 hours. Proceed to the
> Fix Issues step below and address the problem. However, some issues don’t
> require cancellation. For example, if an issue is found in the website pull
> request, just correct it on the spot and the vote can continue as-is.
> For cancelling a release, the release manager needs to send an email to the
> release candidate thread, stating that the release candidate is officially
> cancelled. Next, all artifacts created specifically for the RC in the
> previous steps need to be removed:
> * Delete the staging repository in Nexus
> * Remove the source / binary RC files from dist.apache.org
> * Delete the source code tag in git
> *If there are no issues, reply on the vote thread to close the voting.* Then,
> tally the votes in a separate email. Here’s an email template; please adjust
> as you see fit.
> {quote}From: Release Manager
> To: d...@flink.apache.org
> Subject: [RESULT] [VOTE] Release 1.2.3, release candidate #3
> I'm happy to announce that we have unanimously approved this release.
> There are XXX approving votes, XXX of which are binding:
> * approver 1
> * approver 2
> * approver 3
> * approver 4
> There are no disapproving votes.
> Thanks everyone!
> {quote}
>
>
> h3. Expectations
> * Community votes to release the proposed candidate, with at least three
> approving PMC votes
> Any issues that are raised till the vote is over should be either resolved or
> moved into the next release (if applicable).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33268) Flink REST API response parsing throws exception on new fields
[ https://issues.apache.org/jira/browse/FLINK-33268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated FLINK-33268: --- Labels: pull-request-available (was: ) > Flink REST API response parsing throws exception on new fields > -- > > Key: FLINK-33268 > URL: https://issues.apache.org/jira/browse/FLINK-33268 > Project: Flink > Issue Type: Improvement > Components: Runtime / REST >Affects Versions: 1.19.0 >Reporter: Gabor Somogyi >Priority: Major > Labels: pull-request-available > > At the moment Flink is not ignoring unknown fields when parsing REST > responses. An example for such a class is JobDetailsInfo but this applies to > all others. It would be good to add this support to increase compatibility. > The real life use-case is when the Flink k8s operator wants to handle 2 jobs > with 2 different Flink versions where the newer version has added a new field > to any REST response. Such case the operator gets an exception when for > example it tries to poll the job details with the additional field. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] [FLINK-33268][rest] Skip unknown fields in REST response deserialization [flink]
gaborgsomogyi opened a new pull request, #23930: URL: https://github.com/apache/flink/pull/23930 ## What is the purpose of the change At the moment Flink is throwing exception on unknown fields when parsing REST responses. An example for such a class is `JobDetailsInfo` but this applies to all others. In this PR we ignore all unknown fields in case of REST response JSON deserialization. This is implemented based on [FLIP-401](https://cwiki.apache.org/confluence/display/FLINK/FLIP-401%3A+REST+API+JSON+response+deserialization+unknown+field+tolerance). ## Brief change log Ignore all unknown fields in case of REST response JSON deserialization. ## Verifying this change Added new unit test. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): no - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: no - The serializers: no - The runtime per-record code paths (performance sensitive): no - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? no - If yes, how is the feature documented? not applicable -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (FLINK-33835) Stage source and binary releases on dist.apache.org
[
https://issues.apache.org/jira/browse/FLINK-33835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-33835:
---
Assignee: Jing Ge (was: Qingsheng Ren)
> Stage source and binary releases on dist.apache.org
> ---
>
> Key: FLINK-33835
> URL: https://issues.apache.org/jira/browse/FLINK-33835
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> Copy the source release to the dev repository of dist.apache.org:
> # If you have not already, check out the Flink section of the dev repository
> on dist.apache.org via Subversion. In a fresh directory:
> {code:bash}
> $ svn checkout https://dist.apache.org/repos/dist/dev/flink --depth=immediates
> {code}
> # Make a directory for the new release and copy all the artifacts (Flink
> source/binary distributions, hashes, GPG signatures and the python
> subdirectory) into that newly created directory:
> {code:bash}
> $ mkdir flink/flink-${RELEASE_VERSION}-rc${RC_NUM}
> $ mv /tools/releasing/release/*
> flink/flink-${RELEASE_VERSION}-rc${RC_NUM}
> {code}
> # Add and commit all the files.
> {code:bash}
> $ cd flink
> flink $ svn add flink-${RELEASE_VERSION}-rc${RC_NUM}
> flink $ svn commit -m "Add flink-${RELEASE_VERSION}-rc${RC_NUM}"
> {code}
> # Verify that files are present under
> [https://dist.apache.org/repos/dist/dev/flink|https://dist.apache.org/repos/dist/dev/flink].
> # Push the release tag if not done already (the following command assumes to
> be called from within the apache/flink checkout):
> {code:bash}
> $ git push refs/tags/release-${RELEASE_VERSION}-rc${RC_NUM}
> {code}
>
>
> h3. Expectations
> * Maven artifacts deployed to the staging repository of
> [repository.apache.org|https://repository.apache.org/content/repositories/]
> * Source distribution deployed to the dev repository of
> [dist.apache.org|https://dist.apache.org/repos/dist/dev/flink/]
> * Check hashes (e.g. shasum -c *.sha512)
> * Check signatures (e.g. {{{}gpg --verify
> flink-1.2.3-source-release.tar.gz.asc flink-1.2.3-source-release.tar.gz{}}})
> * {{grep}} for legal headers in each file.
> * If time allows check the NOTICE files of the modules whose dependencies
> have been changed in this release in advance, since the license issues from
> time to time pop up during voting. See [Verifying a Flink
> Release|https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Release]
> "Checking License" section.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33836) Propose a pull request for website updates
[
https://issues.apache.org/jira/browse/FLINK-33836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33836:
Affects Version/s: 1.18.0
(was: 1.17.0)
> Propose a pull request for website updates
> --
>
> Key: FLINK-33836
> URL: https://issues.apache.org/jira/browse/FLINK-33836
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.17.0
>
>
> The final step of building the candidate is to propose a website pull request
> containing the following changes:
> # update
> [apache/flink-web:_config.yml|https://github.com/apache/flink-web/blob/asf-site/_config.yml]
> ## update {{FLINK_VERSION_STABLE}} and {{FLINK_VERSION_STABLE_SHORT}} as
> required
> ## update version references in quickstarts ({{{}q/{}}} directory) as
> required
> ## (major only) add a new entry to {{flink_releases}} for the release
> binaries and sources
> ## (minor only) update the entry for the previous release in the series in
> {{flink_releases}}
> ### Please pay notice to the ids assigned to the download entries. They
> should be unique and reflect their corresponding version number.
> ## add a new entry to {{release_archive.flink}}
> # add a blog post announcing the release in _posts
> # add a organized release notes page under docs/content/release-notes and
> docs/content.zh/release-notes (like
> [https://nightlies.apache.org/flink/flink-docs-release-1.15/release-notes/flink-1.15/]).
> The page is based on the non-empty release notes collected from the issues,
> and only the issues that affect existing users should be included (e.g.,
> instead of new functionality). It should be in a separate PR since it would
> be merged to the flink project.
> (!) Don’t merge the PRs before finalizing the release.
>
>
> h3. Expectations
> * Website pull request proposed to list the
> [release|http://flink.apache.org/downloads.html]
> * (major only) Check {{docs/config.toml}} to ensure that
> ** the version constants refer to the new version
> ** the {{baseurl}} does not point to {{flink-docs-master}} but
> {{flink-docs-release-X.Y}} instead
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-33836) Propose a pull request for website updates
[
https://issues.apache.org/jira/browse/FLINK-33836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-33836:
---
Assignee: Jing Ge (was: Qingsheng Ren)
> Propose a pull request for website updates
> --
>
> Key: FLINK-33836
> URL: https://issues.apache.org/jira/browse/FLINK-33836
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.17.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.17.0
>
>
> The final step of building the candidate is to propose a website pull request
> containing the following changes:
> # update
> [apache/flink-web:_config.yml|https://github.com/apache/flink-web/blob/asf-site/_config.yml]
> ## update {{FLINK_VERSION_STABLE}} and {{FLINK_VERSION_STABLE_SHORT}} as
> required
> ## update version references in quickstarts ({{{}q/{}}} directory) as
> required
> ## (major only) add a new entry to {{flink_releases}} for the release
> binaries and sources
> ## (minor only) update the entry for the previous release in the series in
> {{flink_releases}}
> ### Please pay notice to the ids assigned to the download entries. They
> should be unique and reflect their corresponding version number.
> ## add a new entry to {{release_archive.flink}}
> # add a blog post announcing the release in _posts
> # add a organized release notes page under docs/content/release-notes and
> docs/content.zh/release-notes (like
> [https://nightlies.apache.org/flink/flink-docs-release-1.15/release-notes/flink-1.15/]).
> The page is based on the non-empty release notes collected from the issues,
> and only the issues that affect existing users should be included (e.g.,
> instead of new functionality). It should be in a separate PR since it would
> be merged to the flink project.
> (!) Don’t merge the PRs before finalizing the release.
>
>
> h3. Expectations
> * Website pull request proposed to list the
> [release|http://flink.apache.org/downloads.html]
> * (major only) Check {{docs/config.toml}} to ensure that
> ** the version constants refer to the new version
> ** the {{baseurl}} does not point to {{flink-docs-master}} but
> {{flink-docs-release-X.Y}} instead
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33836) Propose a pull request for website updates
[
https://issues.apache.org/jira/browse/FLINK-33836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33836:
Summary: Propose a pull request for website updates (was: CLONE - Propose
a pull request for website updates)
> Propose a pull request for website updates
> --
>
> Key: FLINK-33836
> URL: https://issues.apache.org/jira/browse/FLINK-33836
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.17.0
>Reporter: Jing Ge
>Assignee: Qingsheng Ren
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.17.0
>
>
> The final step of building the candidate is to propose a website pull request
> containing the following changes:
> # update
> [apache/flink-web:_config.yml|https://github.com/apache/flink-web/blob/asf-site/_config.yml]
> ## update {{FLINK_VERSION_STABLE}} and {{FLINK_VERSION_STABLE_SHORT}} as
> required
> ## update version references in quickstarts ({{{}q/{}}} directory) as
> required
> ## (major only) add a new entry to {{flink_releases}} for the release
> binaries and sources
> ## (minor only) update the entry for the previous release in the series in
> {{flink_releases}}
> ### Please pay notice to the ids assigned to the download entries. They
> should be unique and reflect their corresponding version number.
> ## add a new entry to {{release_archive.flink}}
> # add a blog post announcing the release in _posts
> # add a organized release notes page under docs/content/release-notes and
> docs/content.zh/release-notes (like
> [https://nightlies.apache.org/flink/flink-docs-release-1.15/release-notes/flink-1.15/]).
> The page is based on the non-empty release notes collected from the issues,
> and only the issues that affect existing users should be included (e.g.,
> instead of new functionality). It should be in a separate PR since it would
> be merged to the flink project.
> (!) Don’t merge the PRs before finalizing the release.
>
>
> h3. Expectations
> * Website pull request proposed to list the
> [release|http://flink.apache.org/downloads.html]
> * (major only) Check {{docs/config.toml}} to ensure that
> ** the version constants refer to the new version
> ** the {{baseurl}} does not point to {{flink-docs-master}} but
> {{flink-docs-release-X.Y}} instead
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33836) Propose a pull request for website updates
[
https://issues.apache.org/jira/browse/FLINK-33836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33836:
Fix Version/s: 1.18.1
(was: 1.17.0)
> Propose a pull request for website updates
> --
>
> Key: FLINK-33836
> URL: https://issues.apache.org/jira/browse/FLINK-33836
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.18.1
>
>
> The final step of building the candidate is to propose a website pull request
> containing the following changes:
> # update
> [apache/flink-web:_config.yml|https://github.com/apache/flink-web/blob/asf-site/_config.yml]
> ## update {{FLINK_VERSION_STABLE}} and {{FLINK_VERSION_STABLE_SHORT}} as
> required
> ## update version references in quickstarts ({{{}q/{}}} directory) as
> required
> ## (major only) add a new entry to {{flink_releases}} for the release
> binaries and sources
> ## (minor only) update the entry for the previous release in the series in
> {{flink_releases}}
> ### Please pay notice to the ids assigned to the download entries. They
> should be unique and reflect their corresponding version number.
> ## add a new entry to {{release_archive.flink}}
> # add a blog post announcing the release in _posts
> # add a organized release notes page under docs/content/release-notes and
> docs/content.zh/release-notes (like
> [https://nightlies.apache.org/flink/flink-docs-release-1.15/release-notes/flink-1.15/]).
> The page is based on the non-empty release notes collected from the issues,
> and only the issues that affect existing users should be included (e.g.,
> instead of new functionality). It should be in a separate PR since it would
> be merged to the flink project.
> (!) Don’t merge the PRs before finalizing the release.
>
>
> h3. Expectations
> * Website pull request proposed to list the
> [release|http://flink.apache.org/downloads.html]
> * (major only) Check {{docs/config.toml}} to ensure that
> ** the version constants refer to the new version
> ** the {{baseurl}} does not point to {{flink-docs-master}} but
> {{flink-docs-release-X.Y}} instead
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33835) Stage source and binary releases on dist.apache.org
[
https://issues.apache.org/jira/browse/FLINK-33835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33835:
Summary: Stage source and binary releases on dist.apache.org (was: CLONE -
Stage source and binary releases on dist.apache.org)
> Stage source and binary releases on dist.apache.org
> ---
>
> Key: FLINK-33835
> URL: https://issues.apache.org/jira/browse/FLINK-33835
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Qingsheng Ren
>Priority: Major
>
> Copy the source release to the dev repository of dist.apache.org:
> # If you have not already, check out the Flink section of the dev repository
> on dist.apache.org via Subversion. In a fresh directory:
> {code:bash}
> $ svn checkout https://dist.apache.org/repos/dist/dev/flink --depth=immediates
> {code}
> # Make a directory for the new release and copy all the artifacts (Flink
> source/binary distributions, hashes, GPG signatures and the python
> subdirectory) into that newly created directory:
> {code:bash}
> $ mkdir flink/flink-${RELEASE_VERSION}-rc${RC_NUM}
> $ mv /tools/releasing/release/*
> flink/flink-${RELEASE_VERSION}-rc${RC_NUM}
> {code}
> # Add and commit all the files.
> {code:bash}
> $ cd flink
> flink $ svn add flink-${RELEASE_VERSION}-rc${RC_NUM}
> flink $ svn commit -m "Add flink-${RELEASE_VERSION}-rc${RC_NUM}"
> {code}
> # Verify that files are present under
> [https://dist.apache.org/repos/dist/dev/flink|https://dist.apache.org/repos/dist/dev/flink].
> # Push the release tag if not done already (the following command assumes to
> be called from within the apache/flink checkout):
> {code:bash}
> $ git push refs/tags/release-${RELEASE_VERSION}-rc${RC_NUM}
> {code}
>
>
> h3. Expectations
> * Maven artifacts deployed to the staging repository of
> [repository.apache.org|https://repository.apache.org/content/repositories/]
> * Source distribution deployed to the dev repository of
> [dist.apache.org|https://dist.apache.org/repos/dist/dev/flink/]
> * Check hashes (e.g. shasum -c *.sha512)
> * Check signatures (e.g. {{{}gpg --verify
> flink-1.2.3-source-release.tar.gz.asc flink-1.2.3-source-release.tar.gz{}}})
> * {{grep}} for legal headers in each file.
> * If time allows check the NOTICE files of the modules whose dependencies
> have been changed in this release in advance, since the license issues from
> time to time pop up during voting. See [Verifying a Flink
> Release|https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Release]
> "Checking License" section.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-33834) CLONE - Build and stage Java and Python artifacts
[
https://issues.apache.org/jira/browse/FLINK-33834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-33834:
---
Assignee: Jing Ge (was: Qingsheng Ren)
> CLONE - Build and stage Java and Python artifacts
> -
>
> Key: FLINK-33834
> URL: https://issues.apache.org/jira/browse/FLINK-33834
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> # Create a local release branch ((!) this step can not be skipped for minor
> releases):
> {code:bash}
> $ cd ./tools
> tools/ $ OLD_VERSION=$CURRENT_SNAPSHOT_VERSION NEW_VERSION=$RELEASE_VERSION
> RELEASE_CANDIDATE=$RC_NUM releasing/create_release_branch.sh
> {code}
> # Tag the release commit:
> {code:bash}
> $ git tag -s ${TAG} -m "${TAG}"
> {code}
> # We now need to do several things:
> ## Create the source release archive
> ## Deploy jar artefacts to the [Apache Nexus
> Repository|https://repository.apache.org/], which is the staging area for
> deploying the jars to Maven Central
> ## Build PyFlink wheel packages
> You might want to create a directory on your local machine for collecting the
> various source and binary releases before uploading them. Creating the binary
> releases is a lengthy process but you can do this on another machine (for
> example, in the "cloud"). When doing this, you can skip signing the release
> files on the remote machine, download them to your local machine and sign
> them there.
> # Build the source release:
> {code:bash}
> tools $ RELEASE_VERSION=$RELEASE_VERSION releasing/create_source_release.sh
> {code}
> # Stage the maven artifacts:
> {code:bash}
> tools $ releasing/deploy_staging_jars.sh
> {code}
> Review all staged artifacts ([https://repository.apache.org/]). They should
> contain all relevant parts for each module, including pom.xml, jar, test jar,
> source, test source, javadoc, etc. Carefully review any new artifacts.
> # Close the staging repository on Apache Nexus. When prompted for a
> description, enter “Apache Flink, version X, release candidate Y”.
> Then, you need to build the PyFlink wheel packages (since 1.11):
> # Set up an azure pipeline in your own Azure account. You can refer to
> [Azure
> Pipelines|https://cwiki.apache.org/confluence/display/FLINK/Azure+Pipelines#AzurePipelines-Tutorial:SettingupAzurePipelinesforaforkoftheFlinkrepository]
> for more details on how to set up azure pipeline for a fork of the Flink
> repository. Note that a google cloud mirror in Europe is used for downloading
> maven artifacts, therefore it is recommended to set your [Azure organization
> region|https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/change-organization-location]
> to Europe to speed up the downloads.
> # Push the release candidate branch to your forked personal Flink
> repository, e.g.
> {code:bash}
> tools $ git push
> refs/heads/release-${RELEASE_VERSION}-rc${RC_NUM}:release-${RELEASE_VERSION}-rc${RC_NUM}
> {code}
> # Trigger the Azure Pipelines manually to build the PyFlink wheel packages
> ## Go to your Azure Pipelines Flink project → Pipelines
> ## Click the "New pipeline" button on the top right
> ## Select "GitHub" → your GitHub Flink repository → "Existing Azure
> Pipelines YAML file"
> ## Select your branch → Set path to "/azure-pipelines.yaml" → click on
> "Continue" → click on "Variables"
> ## Then click "New Variable" button, fill the name with "MODE", and the
> value with "release". Click "OK" to set the variable and the "Save" button to
> save the variables, then back on the "Review your pipeline" screen click
> "Run" to trigger the build.
> ## You should now see a build where only the "CI build (release)" is running
> # Download the PyFlink wheel packages from the build result page after the
> jobs of "build_wheels mac" and "build_wheels linux" have finished.
> ## Download the PyFlink wheel packages
> ### Open the build result page of the pipeline
> ### Go to the {{Artifacts}} page (build_wheels linux -> 1 artifact)
> ### Click {{wheel_Darwin_build_wheels mac}} and {{wheel_Linux_build_wheels
> linux}} separately to download the zip files
> ## Unzip these two zip files
> {code:bash}
> $ cd /path/to/downloaded_wheel_packages
> $ unzip wheel_Linux_build_wheels\ linux.zip
> $ unzip wheel_Darwin_build_wheels\ mac.zip{code}
> ## Create directory {{./dist}} under the directory of {{{}flink-python{}}}:
> {code:bash}
> $ cd
> $ mkdir flink-python/dist{code}
> ## Move the unzipped wheel packages to the directory of
> {{{}flink-python/dist{}}}:
> {code:java}
> $ mv /path/to/wheel_Darwin_build_wheels\ mac/* flink-python/dist/
> $ mv /path/to/wheel_Linux_build_wheels\ linux/* flink-python/dist/
> $ cd tools{code}
> Finally, we create the binary convenience release files:
> {code:b
[jira] [Created] (FLINK-33833) Build Release Candidate: 1.18.1-rc1
Jing Ge created FLINK-33833:
---
Summary: 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.17.0
Reporter: Jing Ge
Assignee: Jing Ge
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-33834) Build and stage Java and Python artifacts
[
https://issues.apache.org/jira/browse/FLINK-33834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33834:
Summary: Build and stage Java and Python artifacts (was: CLONE - Build and
stage Java and Python artifacts)
> Build and stage Java and Python artifacts
> -
>
> Key: FLINK-33834
> URL: https://issues.apache.org/jira/browse/FLINK-33834
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> # Create a local release branch ((!) this step can not be skipped for minor
> releases):
> {code:bash}
> $ cd ./tools
> tools/ $ OLD_VERSION=$CURRENT_SNAPSHOT_VERSION NEW_VERSION=$RELEASE_VERSION
> RELEASE_CANDIDATE=$RC_NUM releasing/create_release_branch.sh
> {code}
> # Tag the release commit:
> {code:bash}
> $ git tag -s ${TAG} -m "${TAG}"
> {code}
> # We now need to do several things:
> ## Create the source release archive
> ## Deploy jar artefacts to the [Apache Nexus
> Repository|https://repository.apache.org/], which is the staging area for
> deploying the jars to Maven Central
> ## Build PyFlink wheel packages
> You might want to create a directory on your local machine for collecting the
> various source and binary releases before uploading them. Creating the binary
> releases is a lengthy process but you can do this on another machine (for
> example, in the "cloud"). When doing this, you can skip signing the release
> files on the remote machine, download them to your local machine and sign
> them there.
> # Build the source release:
> {code:bash}
> tools $ RELEASE_VERSION=$RELEASE_VERSION releasing/create_source_release.sh
> {code}
> # Stage the maven artifacts:
> {code:bash}
> tools $ releasing/deploy_staging_jars.sh
> {code}
> Review all staged artifacts ([https://repository.apache.org/]). They should
> contain all relevant parts for each module, including pom.xml, jar, test jar,
> source, test source, javadoc, etc. Carefully review any new artifacts.
> # Close the staging repository on Apache Nexus. When prompted for a
> description, enter “Apache Flink, version X, release candidate Y”.
> Then, you need to build the PyFlink wheel packages (since 1.11):
> # Set up an azure pipeline in your own Azure account. You can refer to
> [Azure
> Pipelines|https://cwiki.apache.org/confluence/display/FLINK/Azure+Pipelines#AzurePipelines-Tutorial:SettingupAzurePipelinesforaforkoftheFlinkrepository]
> for more details on how to set up azure pipeline for a fork of the Flink
> repository. Note that a google cloud mirror in Europe is used for downloading
> maven artifacts, therefore it is recommended to set your [Azure organization
> region|https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/change-organization-location]
> to Europe to speed up the downloads.
> # Push the release candidate branch to your forked personal Flink
> repository, e.g.
> {code:bash}
> tools $ git push
> refs/heads/release-${RELEASE_VERSION}-rc${RC_NUM}:release-${RELEASE_VERSION}-rc${RC_NUM}
> {code}
> # Trigger the Azure Pipelines manually to build the PyFlink wheel packages
> ## Go to your Azure Pipelines Flink project → Pipelines
> ## Click the "New pipeline" button on the top right
> ## Select "GitHub" → your GitHub Flink repository → "Existing Azure
> Pipelines YAML file"
> ## Select your branch → Set path to "/azure-pipelines.yaml" → click on
> "Continue" → click on "Variables"
> ## Then click "New Variable" button, fill the name with "MODE", and the
> value with "release". Click "OK" to set the variable and the "Save" button to
> save the variables, then back on the "Review your pipeline" screen click
> "Run" to trigger the build.
> ## You should now see a build where only the "CI build (release)" is running
> # Download the PyFlink wheel packages from the build result page after the
> jobs of "build_wheels mac" and "build_wheels linux" have finished.
> ## Download the PyFlink wheel packages
> ### Open the build result page of the pipeline
> ### Go to the {{Artifacts}} page (build_wheels linux -> 1 artifact)
> ### Click {{wheel_Darwin_build_wheels mac}} and {{wheel_Linux_build_wheels
> linux}} separately to download the zip files
> ## Unzip these two zip files
> {code:bash}
> $ cd /path/to/downloaded_wheel_packages
> $ unzip wheel_Linux_build_wheels\ linux.zip
> $ unzip wheel_Darwin_build_wheels\ mac.zip{code}
> ## Create directory {{./dist}} under the directory of {{{}flink-python{}}}:
> {code:bash}
> $ cd
> $ mkdir flink-python/dist{code}
> ## Move the unzipped wheel packages to the directory of
> {{{}flink-python/dist{}}}:
> {code:java}
> $ mv /path/to/wheel_Darwin_build_wheels\ mac/* flink-python/dist/
> $ mv /path/to/wheel_Linux_build_wheels\ linux/* flink-python/dist/
> $ cd tools{code}
> Finally, we create
[jira] [Updated] (FLINK-33831) Checkout the release branch
[
https://issues.apache.org/jira/browse/FLINK-33831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33831:
Fix Version/s: 1.18.1
(was: 1.17.0)
> Checkout the release branch
> ---
>
> Key: FLINK-33831
> URL: https://issues.apache.org/jira/browse/FLINK-33831
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Fix For: 1.18.1
>
>
> If you are doing a new minor release, you need to update Flink version in the
> following repositories and the [AzureCI project
> configuration|https://dev.azure.com/apache-flink/apache-flink/]:
> * [apache/flink|https://github.com/apache/flink]
> * [apache/flink-docker|https://github.com/apache/flink-docker]
> * [apache/flink-benchmarks|https://github.com/apache/flink-benchmarks]
> Patch releases don't require the these repositories to be touched. Simply
> checkout the already existing branch for that version:
> {code:java}
> $ git checkout release-$SHORT_RELEASE_VERSION
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33831) Checkout the release branch
[
https://issues.apache.org/jira/browse/FLINK-33831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33831:
Affects Version/s: 1.18.0
(was: 1.17.0)
> Checkout the release branch
> ---
>
> Key: FLINK-33831
> URL: https://issues.apache.org/jira/browse/FLINK-33831
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Fix For: 1.17.0
>
>
> If you are doing a new minor release, you need to update Flink version in the
> following repositories and the [AzureCI project
> configuration|https://dev.azure.com/apache-flink/apache-flink/]:
> * [apache/flink|https://github.com/apache/flink]
> * [apache/flink-docker|https://github.com/apache/flink-docker]
> * [apache/flink-benchmarks|https://github.com/apache/flink-benchmarks]
> Patch releases don't require the these repositories to be touched. Simply
> checkout the already existing branch for that version:
> {code:java}
> $ git checkout release-$SHORT_RELEASE_VERSION
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33836) CLONE - Propose a pull request for website updates
Jing Ge created FLINK-33836:
---
Summary: CLONE - Propose a pull request for website updates
Key: FLINK-33836
URL: https://issues.apache.org/jira/browse/FLINK-33836
Project: Flink
Issue Type: Sub-task
Affects Versions: 1.17.0
Reporter: Jing Ge
Assignee: Qingsheng Ren
Fix For: 1.17.0
The final step of building the candidate is to propose a website pull request
containing the following changes:
# update
[apache/flink-web:_config.yml|https://github.com/apache/flink-web/blob/asf-site/_config.yml]
## update {{FLINK_VERSION_STABLE}} and {{FLINK_VERSION_STABLE_SHORT}} as
required
## update version references in quickstarts ({{{}q/{}}} directory) as required
## (major only) add a new entry to {{flink_releases}} for the release binaries
and sources
## (minor only) update the entry for the previous release in the series in
{{flink_releases}}
### Please pay notice to the ids assigned to the download entries. They should
be unique and reflect their corresponding version number.
## add a new entry to {{release_archive.flink}}
# add a blog post announcing the release in _posts
# add a organized release notes page under docs/content/release-notes and
docs/content.zh/release-notes (like
[https://nightlies.apache.org/flink/flink-docs-release-1.15/release-notes/flink-1.15/]).
The page is based on the non-empty release notes collected from the issues,
and only the issues that affect existing users should be included (e.g.,
instead of new functionality). It should be in a separate PR since it would be
merged to the flink project.
(!) Don’t merge the PRs before finalizing the release.
h3. Expectations
* Website pull request proposed to list the
[release|http://flink.apache.org/downloads.html]
* (major only) Check {{docs/config.toml}} to ensure that
** the version constants refer to the new version
** the {{baseurl}} does not point to {{flink-docs-master}} but
{{flink-docs-release-X.Y}} instead
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33837) CLONE - Vote on the release candidate
Jing Ge created FLINK-33837:
---
Summary: CLONE - Vote on the release candidate
Key: FLINK-33837
URL: https://issues.apache.org/jira/browse/FLINK-33837
Project: Flink
Issue Type: Sub-task
Affects Versions: 1.17.0
Reporter: Jing Ge
Assignee: Qingsheng Ren
Fix For: 1.17.0
Once you have built and individually reviewed the release candidate, please
share it for the community-wide review. Please review foundation-wide [voting
guidelines|http://www.apache.org/foundation/voting.html] for more information.
Start the review-and-vote thread on the dev@ mailing list. Here’s an email
template; please adjust as you see fit.
{quote}From: Release Manager
To: d...@flink.apache.org
Subject: [VOTE] Release 1.2.3, release candidate #3
Hi everyone,
Please review and vote on the release candidate #3 for the version 1.2.3, as
follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1],
* the official Apache source release and binary convenience releases to be
deployed to dist.apache.org [2], which are signed with the key with fingerprint
[3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.2.3-rc3" [5],
* website pull request listing the new release and adding announcement blog
post [6].
The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.
Thanks,
Release Manager
[1] link
[2] link
[3] [https://dist.apache.org/repos/dist/release/flink/KEYS]
[4] link
[5] link
[6] link
{quote}
*If there are any issues found in the release candidate, reply on the vote
thread to cancel the vote.* There’s no need to wait 72 hours. Proceed to the
Fix Issues step below and address the problem. However, some issues don’t
require cancellation. For example, if an issue is found in the website pull
request, just correct it on the spot and the vote can continue as-is.
For cancelling a release, the release manager needs to send an email to the
release candidate thread, stating that the release candidate is officially
cancelled. Next, all artifacts created specifically for the RC in the previous
steps need to be removed:
* Delete the staging repository in Nexus
* Remove the source / binary RC files from dist.apache.org
* Delete the source code tag in git
*If there are no issues, reply on the vote thread to close the voting.* Then,
tally the votes in a separate email. Here’s an email template; please adjust as
you see fit.
{quote}From: Release Manager
To: d...@flink.apache.org
Subject: [RESULT] [VOTE] Release 1.2.3, release candidate #3
I'm happy to announce that we have unanimously approved this release.
There are XXX approving votes, XXX of which are binding:
* approver 1
* approver 2
* approver 3
* approver 4
There are no disapproving votes.
Thanks everyone!
{quote}
h3. Expectations
* Community votes to release the proposed candidate, with at least three
approving PMC votes
Any issues that are raised till the vote is over should be either resolved or
moved into the next release (if applicable).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33835) CLONE - Stage source and binary releases on dist.apache.org
Jing Ge created FLINK-33835:
---
Summary: CLONE - Stage source and binary releases on
dist.apache.org
Key: FLINK-33835
URL: https://issues.apache.org/jira/browse/FLINK-33835
Project: Flink
Issue Type: Sub-task
Reporter: Jing Ge
Assignee: Qingsheng Ren
Copy the source release to the dev repository of dist.apache.org:
# If you have not already, check out the Flink section of the dev repository on
dist.apache.org via Subversion. In a fresh directory:
{code:bash}
$ svn checkout https://dist.apache.org/repos/dist/dev/flink --depth=immediates
{code}
# Make a directory for the new release and copy all the artifacts (Flink
source/binary distributions, hashes, GPG signatures and the python
subdirectory) into that newly created directory:
{code:bash}
$ mkdir flink/flink-${RELEASE_VERSION}-rc${RC_NUM}
$ mv /tools/releasing/release/*
flink/flink-${RELEASE_VERSION}-rc${RC_NUM}
{code}
# Add and commit all the files.
{code:bash}
$ cd flink
flink $ svn add flink-${RELEASE_VERSION}-rc${RC_NUM}
flink $ svn commit -m "Add flink-${RELEASE_VERSION}-rc${RC_NUM}"
{code}
# Verify that files are present under
[https://dist.apache.org/repos/dist/dev/flink|https://dist.apache.org/repos/dist/dev/flink].
# Push the release tag if not done already (the following command assumes to be
called from within the apache/flink checkout):
{code:bash}
$ git push refs/tags/release-${RELEASE_VERSION}-rc${RC_NUM}
{code}
h3. Expectations
* Maven artifacts deployed to the staging repository of
[repository.apache.org|https://repository.apache.org/content/repositories/]
* Source distribution deployed to the dev repository of
[dist.apache.org|https://dist.apache.org/repos/dist/dev/flink/]
* Check hashes (e.g. shasum -c *.sha512)
* Check signatures (e.g. {{{}gpg --verify
flink-1.2.3-source-release.tar.gz.asc flink-1.2.3-source-release.tar.gz{}}})
* {{grep}} for legal headers in each file.
* If time allows check the NOTICE files of the modules whose dependencies have
been changed in this release in advance, since the license issues from time to
time pop up during voting. See [Verifying a Flink
Release|https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Release]
"Checking License" section.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33834) CLONE - Build and stage Java and Python artifacts
Jing Ge created FLINK-33834:
---
Summary: CLONE - Build and stage Java and Python artifacts
Key: FLINK-33834
URL: https://issues.apache.org/jira/browse/FLINK-33834
Project: Flink
Issue Type: Sub-task
Reporter: Jing Ge
Assignee: Qingsheng Ren
# Create a local release branch ((!) this step can not be skipped for minor
releases):
{code:bash}
$ cd ./tools
tools/ $ OLD_VERSION=$CURRENT_SNAPSHOT_VERSION NEW_VERSION=$RELEASE_VERSION
RELEASE_CANDIDATE=$RC_NUM releasing/create_release_branch.sh
{code}
# Tag the release commit:
{code:bash}
$ git tag -s ${TAG} -m "${TAG}"
{code}
# We now need to do several things:
## Create the source release archive
## Deploy jar artefacts to the [Apache Nexus
Repository|https://repository.apache.org/], which is the staging area for
deploying the jars to Maven Central
## Build PyFlink wheel packages
You might want to create a directory on your local machine for collecting the
various source and binary releases before uploading them. Creating the binary
releases is a lengthy process but you can do this on another machine (for
example, in the "cloud"). When doing this, you can skip signing the release
files on the remote machine, download them to your local machine and sign them
there.
# Build the source release:
{code:bash}
tools $ RELEASE_VERSION=$RELEASE_VERSION releasing/create_source_release.sh
{code}
# Stage the maven artifacts:
{code:bash}
tools $ releasing/deploy_staging_jars.sh
{code}
Review all staged artifacts ([https://repository.apache.org/]). They should
contain all relevant parts for each module, including pom.xml, jar, test jar,
source, test source, javadoc, etc. Carefully review any new artifacts.
# Close the staging repository on Apache Nexus. When prompted for a
description, enter “Apache Flink, version X, release candidate Y”.
Then, you need to build the PyFlink wheel packages (since 1.11):
# Set up an azure pipeline in your own Azure account. You can refer to [Azure
Pipelines|https://cwiki.apache.org/confluence/display/FLINK/Azure+Pipelines#AzurePipelines-Tutorial:SettingupAzurePipelinesforaforkoftheFlinkrepository]
for more details on how to set up azure pipeline for a fork of the Flink
repository. Note that a google cloud mirror in Europe is used for downloading
maven artifacts, therefore it is recommended to set your [Azure organization
region|https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/change-organization-location]
to Europe to speed up the downloads.
# Push the release candidate branch to your forked personal Flink repository,
e.g.
{code:bash}
tools $ git push
refs/heads/release-${RELEASE_VERSION}-rc${RC_NUM}:release-${RELEASE_VERSION}-rc${RC_NUM}
{code}
# Trigger the Azure Pipelines manually to build the PyFlink wheel packages
## Go to your Azure Pipelines Flink project → Pipelines
## Click the "New pipeline" button on the top right
## Select "GitHub" → your GitHub Flink repository → "Existing Azure Pipelines
YAML file"
## Select your branch → Set path to "/azure-pipelines.yaml" → click on
"Continue" → click on "Variables"
## Then click "New Variable" button, fill the name with "MODE", and the value
with "release". Click "OK" to set the variable and the "Save" button to save
the variables, then back on the "Review your pipeline" screen click "Run" to
trigger the build.
## You should now see a build where only the "CI build (release)" is running
# Download the PyFlink wheel packages from the build result page after the
jobs of "build_wheels mac" and "build_wheels linux" have finished.
## Download the PyFlink wheel packages
### Open the build result page of the pipeline
### Go to the {{Artifacts}} page (build_wheels linux -> 1 artifact)
### Click {{wheel_Darwin_build_wheels mac}} and {{wheel_Linux_build_wheels
linux}} separately to download the zip files
## Unzip these two zip files
{code:bash}
$ cd /path/to/downloaded_wheel_packages
$ unzip wheel_Linux_build_wheels\ linux.zip
$ unzip wheel_Darwin_build_wheels\ mac.zip{code}
## Create directory {{./dist}} under the directory of {{{}flink-python{}}}:
{code:bash}
$ cd
$ mkdir flink-python/dist{code}
## Move the unzipped wheel packages to the directory of
{{{}flink-python/dist{}}}:
{code:java}
$ mv /path/to/wheel_Darwin_build_wheels\ mac/* flink-python/dist/
$ mv /path/to/wheel_Linux_build_wheels\ linux/* flink-python/dist/
$ cd tools{code}
Finally, we create the binary convenience release files:
{code:bash}
tools $ RELEASE_VERSION=$RELEASE_VERSION releasing/create_binary_release.sh
{code}
If you want to run this step in parallel on a remote machine you have to make
the release commit available there (for example by pushing to a repository).
*This is important: the commit inside the binary builds has to match the commit
of the source builds and the tagged release commit.*
When building remotely, you can ski
[jira] [Updated] (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 updated FLINK-31154:
Summary: Build Release Candidate: 1.17.0-rc1 (was: Build Release
Candidate: 1.18.0-rc1)
> 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] [Updated] (FLINK-31154) Build Release Candidate: 1.18.0-rc1
[
https://issues.apache.org/jira/browse/FLINK-31154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-31154:
Summary: Build Release Candidate: 1.18.0-rc1 (was: Build Release
Candidate: 1.18.1-rc1)
> Build Release Candidate: 1.18.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
]
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] [Updated] (FLINK-31154) Build Release Candidate: 1.18.1-rc1
[
https://issues.apache.org/jira/browse/FLINK-31154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-31154:
Summary: Build Release Candidate: 1.18.1-rc1 (was: Build Release
Candidate: 1.17.0-rc1)
> Build Release Candidate: 1.18.1-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] [Updated] (FLINK-33828) No need for patch release - Cross team testing
[
https://issues.apache.org/jira/browse/FLINK-33828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33828:
Summary: No need for patch release - Cross team testing (was: No need -
Cross team testing)
> No need for patch release - Cross team testing
> --
>
> Key: FLINK-33828
> URL: https://issues.apache.org/jira/browse/FLINK-33828
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> For user facing features that go into the release we'd like to ensure they
> can actually _be used_ by Flink users. To achieve this the release managers
> ensure that an issue for cross team testing is created in the Apache Flink
> Jira. This can and should be picked up by other community members to verify
> the functionality and usability of the feature.
> The issue should contain some entry points which enables other community
> members to test it. It should not contain documentation on how to use the
> feature as this should be part of the actual documentation. The cross team
> tests are performed after the feature freeze. Documentation should be in
> place before that. Those tests are manual tests, so do not confuse them with
> automated tests.
> To sum that up:
> * User facing features should be tested by other contributors
> * The scope is usability and sanity of the feature
> * The feature needs to be already documented
> * The contributor creates an issue containing some pointers on how to get
> started (e.g. link to the documentation, suggested targets of verification)
> * Other community members pick those issues up and provide feedback
> * Cross team testing happens right after the feature freeze
>
>
> h3. Expectations
> * Jira issues for each expected release task according to the release plan
> is created and labeled as {{{}release-testing{}}}.
> * All the created release-testing-related Jira issues are resolved and the
> corresponding blocker issues are fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33832) No need for patch release - Verify that no exclusions were erroneously added to the japicmp plugin
[
https://issues.apache.org/jira/browse/FLINK-33832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33832:
Summary: No need for patch release - Verify that no exclusions were
erroneously added to the japicmp plugin (was: CLONE - Verify that no
exclusions were erroneously added to the japicmp plugin)
> No need for patch release - Verify that no exclusions were erroneously added
> to the japicmp plugin
> --
>
> Key: FLINK-33832
> URL: https://issues.apache.org/jira/browse/FLINK-33832
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Matthias Pohl
>Priority: Major
>
> 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 (see
> [apache/flink:pom.xml:2175ff|https://github.com/apache/flink/blob/3856c49af77601cf7943a5072d8c932279ce46b4/pom.xml#L2175]
> 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)
[jira] [Assigned] (FLINK-33832) No need for patch release - Verify that no exclusions were erroneously added to the japicmp plugin
[
https://issues.apache.org/jira/browse/FLINK-33832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-33832:
---
Assignee: Jing Ge (was: Matthias Pohl)
> No need for patch release - Verify that no exclusions were erroneously added
> to the japicmp plugin
> --
>
> Key: FLINK-33832
> URL: https://issues.apache.org/jira/browse/FLINK-33832
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> 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 (see
> [apache/flink:pom.xml:2175ff|https://github.com/apache/flink/blob/3856c49af77601cf7943a5072d8c932279ce46b4/pom.xml#L2175]
> 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)
[jira] [Closed] (FLINK-33832) No need for patch release - Verify that no exclusions were erroneously added to the japicmp plugin
[
https://issues.apache.org/jira/browse/FLINK-33832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge closed FLINK-33832.
---
Resolution: Won't Fix
> No need for patch release - Verify that no exclusions were erroneously added
> to the japicmp plugin
> --
>
> Key: FLINK-33832
> URL: https://issues.apache.org/jira/browse/FLINK-33832
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> 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 (see
> [apache/flink:pom.xml:2175ff|https://github.com/apache/flink/blob/3856c49af77601cf7943a5072d8c932279ce46b4/pom.xml#L2175]
> 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)
[jira] [Assigned] (FLINK-33831) Checkout the release branch
[
https://issues.apache.org/jira/browse/FLINK-33831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-33831:
---
Assignee: Jing Ge (was: Leonard Xu)
> Checkout the release branch
> ---
>
> Key: FLINK-33831
> URL: https://issues.apache.org/jira/browse/FLINK-33831
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.17.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Fix For: 1.17.0
>
>
> If you are doing a new minor release, you need to update Flink version in the
> following repositories and the [AzureCI project
> configuration|https://dev.azure.com/apache-flink/apache-flink/]:
> * [apache/flink|https://github.com/apache/flink]
> * [apache/flink-docker|https://github.com/apache/flink-docker]
> * [apache/flink-benchmarks|https://github.com/apache/flink-benchmarks]
> Patch releases don't require the these repositories to be touched. Simply
> checkout the already existing branch for that version:
> {code:java}
> $ git checkout release-$SHORT_RELEASE_VERSION
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33831) Checkout the release branch
[
https://issues.apache.org/jira/browse/FLINK-33831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33831:
Summary: Checkout the release branch (was: CLONE - Create a release branch)
> Checkout the release branch
> ---
>
> Key: FLINK-33831
> URL: https://issues.apache.org/jira/browse/FLINK-33831
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.17.0
>Reporter: Jing Ge
>Assignee: Leonard Xu
>Priority: Major
> Fix For: 1.17.0
>
>
> If you are doing a new minor release, you need to update Flink version in the
> following repositories and the [AzureCI project
> configuration|https://dev.azure.com/apache-flink/apache-flink/]:
> * [apache/flink|https://github.com/apache/flink]
> * [apache/flink-docker|https://github.com/apache/flink-docker]
> * [apache/flink-benchmarks|https://github.com/apache/flink-benchmarks]
> Patch releases don't require the these repositories to be touched. Simply
> checkout the already existing branch for that version:
> {code:java}
> $ git checkout release-$SHORT_RELEASE_VERSION
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-33830) Select executing Release Manager
[
https://issues.apache.org/jira/browse/FLINK-33830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-33830:
---
Assignee: Jing Ge (was: Qingsheng Ren)
> Select executing Release Manager
>
>
> Key: FLINK-33830
> URL: https://issues.apache.org/jira/browse/FLINK-33830
> Project: Flink
> Issue Type: Sub-task
> Components: Release System
>Affects Versions: 1.17.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Fix For: 1.17.0
>
>
> h4. GPG Key
> You need to have a GPG key to sign the release artifacts. Please be aware of
> the ASF-wide [release signing
> guidelines|https://www.apache.org/dev/release-signing.html]. If you don’t
> have a GPG key associated with your Apache account, please create one
> according to the guidelines.
> Determine your Apache GPG Key and Key ID, as follows:
> {code:java}
> $ gpg --list-keys
> {code}
> This will list your GPG keys. One of these should reflect your Apache
> account, for example:
> {code:java}
> --
> pub 2048R/845E6689 2016-02-23
> uid Nomen Nescio
> sub 2048R/BA4D50BE 2016-02-23
> {code}
> In the example above, the key ID is the 8-digit hex string in the {{pub}}
> line: {{{}845E6689{}}}.
> Now, add your Apache GPG key to the Flink’s {{KEYS}} file in the [Apache
> Flink release KEYS
> file|https://dist.apache.org/repos/dist/release/flink/KEYS] repository at
> [dist.apache.org|http://dist.apache.org/]. Follow the instructions listed at
> the top of these files. (Note: Only PMC members have write access to the
> release repository. If you end up getting 403 errors ask on the mailing list
> for assistance.)
> Configure {{git}} to use this key when signing code by giving it your key ID,
> as follows:
> {code:java}
> $ git config --global user.signingkey 845E6689
> {code}
> You may drop the {{--global}} option if you’d prefer to use this key for the
> current repository only.
> You may wish to start {{gpg-agent}} to unlock your GPG key only once using
> your passphrase. Otherwise, you may need to enter this passphrase hundreds of
> times. The setup for {{gpg-agent}} varies based on operating system, but may
> be something like this:
> {code:bash}
> $ eval $(gpg-agent --daemon --no-grab --write-env-file $HOME/.gpg-agent-info)
> $ export GPG_TTY=$(tty)
> $ export GPG_AGENT_INFO
> {code}
> h4. Access to Apache Nexus repository
> Configure access to the [Apache Nexus
> repository|https://repository.apache.org/], which enables final deployment of
> releases to the Maven Central Repository.
> # You log in with your Apache account.
> # Confirm you have appropriate access by finding {{org.apache.flink}} under
> {{{}Staging Profiles{}}}.
> # Navigate to your {{Profile}} (top right drop-down menu of the page).
> # Choose {{User Token}} from the dropdown, then click {{{}Access User
> Token{}}}. Copy a snippet of the Maven XML configuration block.
> # Insert this snippet twice into your global Maven {{settings.xml}} file,
> typically {{{}${HOME}/.m2/settings.xml{}}}. The end result should look like
> this, where {{TOKEN_NAME}} and {{TOKEN_PASSWORD}} are your secret tokens:
> {code:xml}
>
>
>
>apache.releases.https
>TOKEN_NAME
>TOKEN_PASSWORD
>
>
>apache.snapshots.https
>TOKEN_NAME
>TOKEN_PASSWORD
>
>
>
> {code}
> h4. Website development setup
> Get ready for updating the Flink website by following the [website
> development
> instructions|https://flink.apache.org/contributing/improve-website.html].
> h4. GNU Tar Setup for Mac (Skip this step if you are not using a Mac)
> The default tar application on Mac does not support GNU archive format and
> defaults to Pax. This bloats the archive with unnecessary metadata that can
> result in additional files when decompressing (see [1.15.2-RC2 vote
> thread|https://lists.apache.org/thread/mzbgsb7y9vdp9bs00gsgscsjv2ygy58q]).
> Install gnu-tar and create a symbolic link to use in preference of the
> default tar program.
> {code:bash}
> $ brew install gnu-tar
> $ ln -s /usr/local/bin/gtar /usr/local/bin/tar
> $ which tar
> {code}
>
>
> h3. Expectations
> * Release Manager’s GPG key is published to
> [dist.apache.org|http://dist.apache.org/]
> * Release Manager’s GPG key is configured in git configuration
> * Release Manager's GPG key is configured as the default gpg key.
> * Release Manager has {{org.apache.flink}} listed under Staging Profiles in
> Nexus
> * Release Manager’s Nexus User Token is configured in settings.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33831) CLONE - Create a release branch
[
https://issues.apache.org/jira/browse/FLINK-33831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33831:
Description:
If you are doing a new minor release, you need to update Flink version in the
following repositories and the [AzureCI project
configuration|https://dev.azure.com/apache-flink/apache-flink/]:
* [apache/flink|https://github.com/apache/flink]
* [apache/flink-docker|https://github.com/apache/flink-docker]
* [apache/flink-benchmarks|https://github.com/apache/flink-benchmarks]
Patch releases don't require the these repositories to be touched. Simply
checkout the already existing branch for that version:
{code:java}
$ git checkout release-$SHORT_RELEASE_VERSION
{code}
was:
If you are doing a new minor release, you need to update Flink version in the
following repositories and the [AzureCI project
configuration|https://dev.azure.com/apache-flink/apache-flink/]:
* [apache/flink|https://github.com/apache/flink]
* [apache/flink-docker|https://github.com/apache/flink-docker]
* [apache/flink-benchmarks|https://github.com/apache/flink-benchmarks]
Patch releases don't require the these repositories to be touched. Simply
checkout the already existing branch for that version:
{code:java}
$ git checkout release-$SHORT_RELEASE_VERSION
{code}
h4. Flink repository
Create a branch for the new version that we want to release before updating the
master branch to the next development version:
{code:bash}
$ cd ./tools
tools $ releasing/create_snapshot_branch.sh
tools $ git checkout master
tools $ OLD_VERSION=$CURRENT_SNAPSHOT_VERSION
NEW_VERSION=$NEXT_SNAPSHOT_VERSION releasing/update_branch_version.sh
{code}
In the {{master}} branch, add a new value (e.g. {{v1_16("1.16")}}) to
[apache-flink:flink-annotations/src/main/java/org/apache/flink/FlinkVersion|https://github.com/apache/flink/blob/master/flink-annotations/src/main/java/org/apache/flink/FlinkVersion.java]
as the last entry:
{code:java}
// ...
v1_12("1.12"),
v1_13("1.13"),
v1_14("1.14"),
v1_15("1.15"),
v1_16("1.16");
{code}
The newly created branch and updated {{master}} branch need to be pushed to the
official repository.
h4. Flink Docker Repository
Afterwards fork off from {{dev-master}} a {{dev-x.y}} branch in the
[apache/flink-docker|https://github.com/apache/flink-docker] repository. Make
sure that
[apache/flink-docker:.github/workflows/ci.yml|https://github.com/apache/flink-docker/blob/dev-master/.github/workflows/ci.yml]
points to the correct snapshot version; for {{dev-x.y}} it should point to
{{{}x.y-SNAPSHOT{}}}, while for {{dev-master}} it should point to the most
recent snapshot version (\{[$NEXT_SNAPSHOT_VERSION}}).
After pushing the new minor release branch, as the last step you should also
update the documentation workflow to also build the documentation for the new
release branch. Check [Managing
Documentation|https://cwiki.apache.org/confluence/display/FLINK/Managing+Documentation]
on details on how to do that. You may also want to manually trigger a build to
make the changes visible as soon as possible.
h4. Flink Benchmark Repository
First of all, checkout the {{master}} branch to {{dev-x.y}} branch in
[apache/flink-benchmarks|https://github.com/apache/flink-benchmarks], so that
we can have a branch named {{dev-x.y}} which could be built on top of
(${{CURRENT_SNAPSHOT_VERSION}}).
Then, inside the repository you need to manually update the {{flink.version}}
property inside the parent *pom.xml* file. It should be pointing to the most
recent snapshot version ($NEXT_SNAPSHOT_VERSION). For example:
{code:xml}
1.18-SNAPSHOT
{code}
h4. AzureCI Project Configuration
The new release branch needs to be configured within AzureCI to make azure
aware of the new release branch. This matter can only be handled by Ververica
employees since they are owning the AzureCI setup.
h3. Expectations (Minor Version only if not stated otherwise)
* Release branch has been created and pushed
* Changes on the new release branch are picked up by [Azure
CI|https://dev.azure.com/apache-flink/apache-flink/_build?definitionId=1&_a=summary]
* {{master}} branch has the version information updated to the new version
(check pom.xml files and
*
[apache-flink:flink-annotations/src/main/java/org/apache/flink/FlinkVersion|https://github.com/apache/flink/blob/master/flink-annotations/src/main/java/org/apache/flink/FlinkVersion.java]
enum)
* New version is added to the
[apache-flink:flink-annotations/src/main/java/org/apache/flink/FlinkVersion|https://github.com/apache/flink/blob/master/flink-annotations/src/main/java/org/apache/flink/FlinkVersion.java]
enum.
* Make sure [flink-docker|https://github.com/apache/flink-docker/] has
{{dev-x.y}} branch and docker e2e tests run against this branch in the
corresponding Apache Flink release branch (see
[apache/flink:flink-end-to-end-tests/test-scripts/common_docker.sh:51|https://github.co
[jira] [Assigned] (FLINK-33829) Review Release Notes in JIRA
[ https://issues.apache.org/jira/browse/FLINK-33829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-33829: --- Assignee: Jing Ge (was: Qingsheng Ren) > Review Release Notes in JIRA > > > Key: FLINK-33829 > URL: https://issues.apache.org/jira/browse/FLINK-33829 > Project: Flink > Issue Type: Sub-task >Reporter: Jing Ge >Assignee: Jing Ge >Priority: Major > > Example for patch release: > https://flink.apache.org/2023/11/29/apache-flink-1.17.2-release-announcement/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-33830) Select executing Release Manager
[
https://issues.apache.org/jira/browse/FLINK-33830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33830:
Summary: Select executing Release Manager (was: CLONE - Select executing
Release Manager)
> Select executing Release Manager
>
>
> Key: FLINK-33830
> URL: https://issues.apache.org/jira/browse/FLINK-33830
> Project: Flink
> Issue Type: Sub-task
> Components: Release System
>Affects Versions: 1.17.0
>Reporter: Jing Ge
>Assignee: Qingsheng Ren
>Priority: Major
> Fix For: 1.17.0
>
>
> h4. GPG Key
> You need to have a GPG key to sign the release artifacts. Please be aware of
> the ASF-wide [release signing
> guidelines|https://www.apache.org/dev/release-signing.html]. If you don’t
> have a GPG key associated with your Apache account, please create one
> according to the guidelines.
> Determine your Apache GPG Key and Key ID, as follows:
> {code:java}
> $ gpg --list-keys
> {code}
> This will list your GPG keys. One of these should reflect your Apache
> account, for example:
> {code:java}
> --
> pub 2048R/845E6689 2016-02-23
> uid Nomen Nescio
> sub 2048R/BA4D50BE 2016-02-23
> {code}
> In the example above, the key ID is the 8-digit hex string in the {{pub}}
> line: {{{}845E6689{}}}.
> Now, add your Apache GPG key to the Flink’s {{KEYS}} file in the [Apache
> Flink release KEYS
> file|https://dist.apache.org/repos/dist/release/flink/KEYS] repository at
> [dist.apache.org|http://dist.apache.org/]. Follow the instructions listed at
> the top of these files. (Note: Only PMC members have write access to the
> release repository. If you end up getting 403 errors ask on the mailing list
> for assistance.)
> Configure {{git}} to use this key when signing code by giving it your key ID,
> as follows:
> {code:java}
> $ git config --global user.signingkey 845E6689
> {code}
> You may drop the {{--global}} option if you’d prefer to use this key for the
> current repository only.
> You may wish to start {{gpg-agent}} to unlock your GPG key only once using
> your passphrase. Otherwise, you may need to enter this passphrase hundreds of
> times. The setup for {{gpg-agent}} varies based on operating system, but may
> be something like this:
> {code:bash}
> $ eval $(gpg-agent --daemon --no-grab --write-env-file $HOME/.gpg-agent-info)
> $ export GPG_TTY=$(tty)
> $ export GPG_AGENT_INFO
> {code}
> h4. Access to Apache Nexus repository
> Configure access to the [Apache Nexus
> repository|https://repository.apache.org/], which enables final deployment of
> releases to the Maven Central Repository.
> # You log in with your Apache account.
> # Confirm you have appropriate access by finding {{org.apache.flink}} under
> {{{}Staging Profiles{}}}.
> # Navigate to your {{Profile}} (top right drop-down menu of the page).
> # Choose {{User Token}} from the dropdown, then click {{{}Access User
> Token{}}}. Copy a snippet of the Maven XML configuration block.
> # Insert this snippet twice into your global Maven {{settings.xml}} file,
> typically {{{}${HOME}/.m2/settings.xml{}}}. The end result should look like
> this, where {{TOKEN_NAME}} and {{TOKEN_PASSWORD}} are your secret tokens:
> {code:xml}
>
>
>
>apache.releases.https
>TOKEN_NAME
>TOKEN_PASSWORD
>
>
>apache.snapshots.https
>TOKEN_NAME
>TOKEN_PASSWORD
>
>
>
> {code}
> h4. Website development setup
> Get ready for updating the Flink website by following the [website
> development
> instructions|https://flink.apache.org/contributing/improve-website.html].
> h4. GNU Tar Setup for Mac (Skip this step if you are not using a Mac)
> The default tar application on Mac does not support GNU archive format and
> defaults to Pax. This bloats the archive with unnecessary metadata that can
> result in additional files when decompressing (see [1.15.2-RC2 vote
> thread|https://lists.apache.org/thread/mzbgsb7y9vdp9bs00gsgscsjv2ygy58q]).
> Install gnu-tar and create a symbolic link to use in preference of the
> default tar program.
> {code:bash}
> $ brew install gnu-tar
> $ ln -s /usr/local/bin/gtar /usr/local/bin/tar
> $ which tar
> {code}
>
>
> h3. Expectations
> * Release Manager’s GPG key is published to
> [dist.apache.org|http://dist.apache.org/]
> * Release Manager’s GPG key is configured in git configuration
> * Release Manager's GPG key is configured as the default gpg key.
> * Release Manager has {{org.apache.flink}} listed under Staging Profiles in
> Nexus
> * Release Manager’s Nexus User Token is configured in settings.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33829) Review Release Notes in JIRA
[ https://issues.apache.org/jira/browse/FLINK-33829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge updated FLINK-33829: Summary: Review Release Notes in JIRA (was: CLONE - Review Release Notes in JIRA) > Review Release Notes in JIRA > > > Key: FLINK-33829 > URL: https://issues.apache.org/jira/browse/FLINK-33829 > Project: Flink > Issue Type: Sub-task >Reporter: Jing Ge >Assignee: Qingsheng Ren >Priority: Major > > Example for patch release: > https://flink.apache.org/2023/11/29/apache-flink-1.17.2-release-announcement/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-33829) CLONE - Review Release Notes in JIRA
[
https://issues.apache.org/jira/browse/FLINK-33829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33829:
Description:
Example for patch release:
https://flink.apache.org/2023/11/29/apache-flink-1.17.2-release-announcement/
was:
JIRA automatically generates Release Notes based on the {{Fix Version}} field
applied to issues. Release Notes are intended for Flink users (not Flink
committers/contributors). You should ensure that Release Notes are informative
and useful.
Open the release notes from the version status page by choosing the release
underway and clicking Release Notes.
You should verify that the issues listed automatically by JIRA are appropriate
to appear in the Release Notes. Specifically, issues should:
* Be appropriately classified as {{{}Bug{}}}, {{{}New Feature{}}},
{{{}Improvement{}}}, etc.
* Represent noteworthy user-facing changes, such as new functionality,
backward-incompatible API changes, or performance improvements.
* Have occurred since the previous release; an issue that was introduced and
fixed between releases should not appear in the Release Notes.
* Have an issue title that makes sense when read on its own.
Adjust any of the above properties to the improve clarity and presentation of
the Release Notes.
Ensure that the JIRA release notes are also included in the release notes of
the documentation (see section "Review and update documentation").
h4. Content of Release Notes field from JIRA tickets
To get the list of "release notes" field from JIRA, you can ran the following
script using JIRA REST API (notes the maxResults limits the number of entries):
{code:bash}
curl -s
https://issues.apache.org/jira//rest/api/2/search?maxResults=200&jql=project%20%3D%20FLINK%20AND%20%22Release%20Note%22%20is%20not%20EMPTY%20and%20fixVersion%20%3D%20${RELEASE_VERSION}
| jq '.issues[]|.key,.fields.summary,.fields.customfield_12310192' | paste - -
-
{code}
{{jq}} is present in most Linux distributions and on MacOS can be installed
via brew.
h3. Expectations
* Release Notes in JIRA have been audited and adjusted
> CLONE - Review Release Notes in JIRA
>
>
> Key: FLINK-33829
> URL: https://issues.apache.org/jira/browse/FLINK-33829
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Qingsheng Ren
>Priority: Major
>
> Example for patch release:
> https://flink.apache.org/2023/11/29/apache-flink-1.17.2-release-announcement/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (FLINK-33828) No need - Cross team testing
[
https://issues.apache.org/jira/browse/FLINK-33828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge closed FLINK-33828.
---
Assignee: Jing Ge (was: Qingsheng Ren)
Resolution: Won't Fix
> No need - Cross team testing
>
>
> Key: FLINK-33828
> URL: https://issues.apache.org/jira/browse/FLINK-33828
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>
> For user facing features that go into the release we'd like to ensure they
> can actually _be used_ by Flink users. To achieve this the release managers
> ensure that an issue for cross team testing is created in the Apache Flink
> Jira. This can and should be picked up by other community members to verify
> the functionality and usability of the feature.
> The issue should contain some entry points which enables other community
> members to test it. It should not contain documentation on how to use the
> feature as this should be part of the actual documentation. The cross team
> tests are performed after the feature freeze. Documentation should be in
> place before that. Those tests are manual tests, so do not confuse them with
> automated tests.
> To sum that up:
> * User facing features should be tested by other contributors
> * The scope is usability and sanity of the feature
> * The feature needs to be already documented
> * The contributor creates an issue containing some pointers on how to get
> started (e.g. link to the documentation, suggested targets of verification)
> * Other community members pick those issues up and provide feedback
> * Cross team testing happens right after the feature freeze
>
>
> h3. Expectations
> * Jira issues for each expected release task according to the release plan
> is created and labeled as {{{}release-testing{}}}.
> * All the created release-testing-related Jira issues are resolved and the
> corresponding blocker issues are fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33828) No need - Cross team testing
[
https://issues.apache.org/jira/browse/FLINK-33828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33828:
Summary: No need - Cross team testing (was: CLONE - Cross team testing)
> No need - Cross team testing
>
>
> Key: FLINK-33828
> URL: https://issues.apache.org/jira/browse/FLINK-33828
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Qingsheng Ren
>Priority: Major
>
> For user facing features that go into the release we'd like to ensure they
> can actually _be used_ by Flink users. To achieve this the release managers
> ensure that an issue for cross team testing is created in the Apache Flink
> Jira. This can and should be picked up by other community members to verify
> the functionality and usability of the feature.
> The issue should contain some entry points which enables other community
> members to test it. It should not contain documentation on how to use the
> feature as this should be part of the actual documentation. The cross team
> tests are performed after the feature freeze. Documentation should be in
> place before that. Those tests are manual tests, so do not confuse them with
> automated tests.
> To sum that up:
> * User facing features should be tested by other contributors
> * The scope is usability and sanity of the feature
> * The feature needs to be already documented
> * The contributor creates an issue containing some pointers on how to get
> started (e.g. link to the documentation, suggested targets of verification)
> * Other community members pick those issues up and provide feedback
> * Cross team testing happens right after the feature freeze
>
>
> h3. Expectations
> * Jira issues for each expected release task according to the release plan
> is created and labeled as {{{}release-testing{}}}.
> * All the created release-testing-related Jira issues are resolved and the
> corresponding blocker issues are fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33827) Review and update documentation
[
https://issues.apache.org/jira/browse/FLINK-33827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33827:
Description:
There are a few pages in the documentation that need to be reviewed and updated
for each patch release.
h3. Expectations
* (minor only) The documentation for the new major release is visible under
[https://nightlies.apache.org/flink/flink-docs-release-$SHORT_RELEASE_VERSION]
(after at least one [doc
build|https://github.com/apache/flink/actions/workflows/docs.yml] succeeded).
* (minor only) The documentation for the new major release does not contain
"-SNAPSHOT" in its version title, and all links refer to the corresponding
version docs instead of {{{}master{}}}.
was:
There are a few pages in the documentation that need to be reviewed and updated
for each minor release.
h3. Expectations
* (minor only) The documentation for the new major release is visible under
[https://nightlies.apache.org/flink/flink-docs-release-$SHORT_RELEASE_VERSION]
(after at least one [doc
build|https://github.com/apache/flink/actions/workflows/docs.yml] succeeded).
* (minor only) The documentation for the new major release does not contain
"-SNAPSHOT" in its version title, and all links refer to the corresponding
version docs instead of {{{}master{}}}.
> Review and update documentation
> ---
>
> Key: FLINK-33827
> URL: https://issues.apache.org/jira/browse/FLINK-33827
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.17.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.17.0
>
>
> There are a few pages in the documentation that need to be reviewed and
> updated for each patch release.
> h3. Expectations
> * (minor only) The documentation for the new major release is visible under
> [https://nightlies.apache.org/flink/flink-docs-release-$SHORT_RELEASE_VERSION]
> (after at least one [doc
> build|https://github.com/apache/flink/actions/workflows/docs.yml] succeeded).
> * (minor only) The documentation for the new major release does not contain
> "-SNAPSHOT" in its version title, and all links refer to the corresponding
> version docs instead of {{{}master{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33827) Review and update documentation
[
https://issues.apache.org/jira/browse/FLINK-33827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33827:
Summary: Review and update documentation (was: CLONE - Review and update
documentation)
> Review and update documentation
> ---
>
> Key: FLINK-33827
> URL: https://issues.apache.org/jira/browse/FLINK-33827
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.17.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.17.0
>
>
> There are a few pages in the documentation that need to be reviewed and
> updated for each minor release.
> h3. Expectations
> * (minor only) The documentation for the new major release is visible under
> [https://nightlies.apache.org/flink/flink-docs-release-$SHORT_RELEASE_VERSION]
> (after at least one [doc
> build|https://github.com/apache/flink/actions/workflows/docs.yml] succeeded).
> * (minor only) The documentation for the new major release does not contain
> "-SNAPSHOT" in its version title, and all links refer to the corresponding
> version docs instead of {{{}master{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33826) Triage release-blocking issues in JIRA
[ https://issues.apache.org/jira/browse/FLINK-33826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge updated FLINK-33826: Summary: Triage release-blocking issues in JIRA (was: CLONE - Triage release-blocking issues in JIRA) > Triage release-blocking issues in JIRA > -- > > Key: FLINK-33826 > URL: https://issues.apache.org/jira/browse/FLINK-33826 > Project: Flink > Issue Type: Sub-task >Reporter: Jing Ge >Assignee: Jing Ge >Priority: Major > > https://issues.apache.org/jira/projects/FLINK/versions/12353640 > There could be outstanding release-blocking issues, which should be triaged > before proceeding to build a release candidate. We track them by assigning a > specific Fix version field even before the issue resolved. > The list of release-blocking issues is available at the version status page. > Triage each unresolved issue with one of the following resolutions: > * If the issue has been resolved and JIRA was not updated, resolve it > accordingly. > * If the issue has not been resolved and it is acceptable to defer this > until the next release, update the Fix Version field to the new version you > just created. Please consider discussing this with stakeholders and the dev@ > mailing list, as appropriate. > ** When using "Bulk Change" functionality of Jira > *** First, add the newly created version to Fix Version for all unresolved > tickets that have old the old version among its Fix Versions. > *** Afterwards, remove the old version from the Fix Version. > * If the issue has not been resolved and it is not acceptable to release > until it is fixed, the release cannot proceed. Instead, work with the Flink > community to resolve the issue. > > > h3. Expectations > * There are no release blocking JIRA issues -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-33825) Create a new version in JIRA
[
https://issues.apache.org/jira/browse/FLINK-33825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33825:
Summary: Create a new version in JIRA (was: CLONE - Create a new version
in JIRA)
> Create a new version in JIRA
>
>
> Key: FLINK-33825
> URL: https://issues.apache.org/jira/browse/FLINK-33825
> Project: Flink
> Issue Type: Sub-task
>Reporter: Jing Ge
>Priority: Major
>
> When contributors resolve an issue in JIRA, they are tagging it with a
> release that will contain their changes. With the release currently underway,
> new issues should be resolved against a subsequent future release. Therefore,
> you should create a release item for this subsequent release, as follows:
> # In JIRA, navigate to the [Flink > Administration >
> Versions|https://issues.apache.org/jira/plugins/servlet/project-config/FLINK/versions].
> # Add a new release: choose the next minor version number compared to the
> one currently underway, select today’s date as the Start Date, and choose Add.
> (Note: Only PMC members have access to the project administration. If you do
> not have access, ask on the mailing list for assistance.)
>
>
> h3. Expectations
> * The new version should be listed in the dropdown menu of {{fixVersion}} or
> {{affectedVersion}} under "unreleased versions" when creating a new Jira
> issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FLINK-33827) CLONE - Review and update documentation
[
https://issues.apache.org/jira/browse/FLINK-33827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge reassigned FLINK-33827:
---
Assignee: Jing Ge (was: Qingsheng Ren)
> CLONE - Review and update documentation
> ---
>
> Key: FLINK-33827
> URL: https://issues.apache.org/jira/browse/FLINK-33827
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.17.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.17.0
>
>
> There are a few pages in the documentation that need to be reviewed and
> updated for each minor release.
> h3. Expectations
> * (minor only) The documentation for the new major release is visible under
> [https://nightlies.apache.org/flink/flink-docs-release-$SHORT_RELEASE_VERSION]
> (after at least one [doc
> build|https://github.com/apache/flink/actions/workflows/docs.yml] succeeded).
> * (minor only) The documentation for the new major release does not contain
> "-SNAPSHOT" in its version title, and all links refer to the corresponding
> version docs instead of {{{}master{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33827) CLONE - Review and update documentation
[
https://issues.apache.org/jira/browse/FLINK-33827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33827:
Description:
There are a few pages in the documentation that need to be reviewed and updated
for each minor release.
h3. Expectations
* (minor only) The documentation for the new major release is visible under
[https://nightlies.apache.org/flink/flink-docs-release-$SHORT_RELEASE_VERSION]
(after at least one [doc
build|https://github.com/apache/flink/actions/workflows/docs.yml] succeeded).
* (minor only) The documentation for the new major release does not contain
"-SNAPSHOT" in its version title, and all links refer to the corresponding
version docs instead of {{{}master{}}}.
was:
There are a few pages in the documentation that need to be reviewed and updated
for each release.
* Ensure that there exists a release notes page for each non-bugfix release
(e.g., 1.5.0) in {{{}./docs/release-notes/{}}}, that it is up-to-date, and
linked from the start page of the documentation.
* Upgrading Applications and Flink Versions:
[https://ci.apache.org/projects/flink/flink-docs-master/ops/upgrading.html]
* ...
h3. Expectations
* Update upgrade compatibility table
([apache-flink:./docs/content/docs/ops/upgrading.md|https://github.com/apache/flink/blob/master/docs/content/docs/ops/upgrading.md#compatibility-table]
and
[apache-flink:./docs/content.zh/docs/ops/upgrading.md|https://github.com/apache/flink/blob/master/docs/content.zh/docs/ops/upgrading.md#compatibility-table]).
* Update [Release Overview in
Confluence|https://cwiki.apache.org/confluence/display/FLINK/Release+Management+and+Feature+Plan]
* (minor only) The documentation for the new major release is visible under
[https://nightlies.apache.org/flink/flink-docs-release-$SHORT_RELEASE_VERSION]
(after at least one [doc
build|https://github.com/apache/flink/actions/workflows/docs.yml] succeeded).
* (minor only) The documentation for the new major release does not contain
"-SNAPSHOT" in its version title, and all links refer to the corresponding
version docs instead of {{{}master{}}}.
> CLONE - Review and update documentation
> ---
>
> Key: FLINK-33827
> URL: https://issues.apache.org/jira/browse/FLINK-33827
> Project: Flink
> Issue Type: Sub-task
>Affects Versions: 1.17.0
>Reporter: Jing Ge
>Assignee: Qingsheng Ren
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.17.0
>
>
> There are a few pages in the documentation that need to be reviewed and
> updated for each minor release.
> h3. Expectations
> * (minor only) The documentation for the new major release is visible under
> [https://nightlies.apache.org/flink/flink-docs-release-$SHORT_RELEASE_VERSION]
> (after at least one [doc
> build|https://github.com/apache/flink/actions/workflows/docs.yml] succeeded).
> * (minor only) The documentation for the new major release does not contain
> "-SNAPSHOT" in its version title, and all links refer to the corresponding
> version docs instead of {{{}master{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33826) CLONE - Triage release-blocking issues in JIRA
[ https://issues.apache.org/jira/browse/FLINK-33826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge updated FLINK-33826: Description: https://issues.apache.org/jira/projects/FLINK/versions/12353640 There could be outstanding release-blocking issues, which should be triaged before proceeding to build a release candidate. We track them by assigning a specific Fix version field even before the issue resolved. The list of release-blocking issues is available at the version status page. Triage each unresolved issue with one of the following resolutions: * If the issue has been resolved and JIRA was not updated, resolve it accordingly. * If the issue has not been resolved and it is acceptable to defer this until the next release, update the Fix Version field to the new version you just created. Please consider discussing this with stakeholders and the dev@ mailing list, as appropriate. ** When using "Bulk Change" functionality of Jira *** First, add the newly created version to Fix Version for all unresolved tickets that have old the old version among its Fix Versions. *** Afterwards, remove the old version from the Fix Version. * If the issue has not been resolved and it is not acceptable to release until it is fixed, the release cannot proceed. Instead, work with the Flink community to resolve the issue. h3. Expectations * There are no release blocking JIRA issues was: There could be outstanding release-blocking issues, which should be triaged before proceeding to build a release candidate. We track them by assigning a specific Fix version field even before the issue resolved. The list of release-blocking issues is available at the version status page. Triage each unresolved issue with one of the following resolutions: * If the issue has been resolved and JIRA was not updated, resolve it accordingly. * If the issue has not been resolved and it is acceptable to defer this until the next release, update the Fix Version field to the new version you just created. Please consider discussing this with stakeholders and the dev@ mailing list, as appropriate. ** When using "Bulk Change" functionality of Jira *** First, add the newly created version to Fix Version for all unresolved tickets that have old the old version among its Fix Versions. *** Afterwards, remove the old version from the Fix Version. * If the issue has not been resolved and it is not acceptable to release until it is fixed, the release cannot proceed. Instead, work with the Flink community to resolve the issue. h3. Expectations * There are no release blocking JIRA issues > CLONE - Triage release-blocking issues in JIRA > -- > > Key: FLINK-33826 > URL: https://issues.apache.org/jira/browse/FLINK-33826 > Project: Flink > Issue Type: Sub-task >Reporter: Jing Ge >Assignee: Jing Ge >Priority: Major > > https://issues.apache.org/jira/projects/FLINK/versions/12353640 > There could be outstanding release-blocking issues, which should be triaged > before proceeding to build a release candidate. We track them by assigning a > specific Fix version field even before the issue resolved. > The list of release-blocking issues is available at the version status page. > Triage each unresolved issue with one of the following resolutions: > * If the issue has been resolved and JIRA was not updated, resolve it > accordingly. > * If the issue has not been resolved and it is acceptable to defer this > until the next release, update the Fix Version field to the new version you > just created. Please consider discussing this with stakeholders and the dev@ > mailing list, as appropriate. > ** When using "Bulk Change" functionality of Jira > *** First, add the newly created version to Fix Version for all unresolved > tickets that have old the old version among its Fix Versions. > *** Afterwards, remove the old version from the Fix Version. > * If the issue has not been resolved and it is not acceptable to release > until it is fixed, the release cannot proceed. Instead, work with the Flink > community to resolve the issue. > > > h3. Expectations > * There are no release blocking JIRA issues -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [FLINK-33603][Filesystem] Bundle Guava for GCS connector [flink]
JingGe commented on PR #23920: URL: https://github.com/apache/flink/pull/23920#issuecomment-1855980170 please see my comment in the original PR: https://github.com/apache/flink/pull/23489#issuecomment-1854677694 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-31049] [flink-connector-kafka]Add support for Kafka record headers to KafkaSink [flink-connector-kafka]
AlexAxeman commented on PR #18: URL: https://github.com/apache/flink-connector-kafka/pull/18#issuecomment-1855945984 @tzulitai Do you know what happened with this change? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-33500][Runtime] Run storing the JobGraph an asynchronous operation [flink]
zhengzhili333 commented on code in PR #23880:
URL: https://github.com/apache/flink/pull/23880#discussion_r1426783965
##
flink-runtime/src/main/java/org/apache/flink/runtime/jobmanager/JobGraphWriter.java:
##
@@ -37,6 +38,18 @@ public interface JobGraphWriter extends
LocallyCleanableResource, GloballyCleana
*/
void putJobGraph(JobGraph jobGraph) throws Exception;
+/**
+ * Adds the {@link JobGraph} instance and have write operations performed
asynchronously in
+ * ioExecutor of Dispatcher
+ *
+ * @param jobGraph
+ * @param ioExecutor
+ * @return
+ * @throws Exception
+ */
+CompletableFuture putJobGraphAsync(JobGraph jobGraph,
Optional ioExecutor)
Review Comment:
Yeah, you're right.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] [hotfix] Test connector against Flink 1.16.2, 1.17.1, 1.18.0 instead of Flink SNAPSHOT version [flink-connector-mongodb]
boring-cyborg[bot] commented on PR #20: URL: https://github.com/apache/flink-connector-mongodb/pull/20#issuecomment-1855933326 Thanks for opening this pull request! Please check out our contributing guidelines. (https://flink.apache.org/contributing/how-to-contribute.html) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [hotfix] Test connector against Flink 1.16.2, 1.17.1, 1.18.0 instead of Flink SNAPSHOT version [flink-connector-mongodb]
ruanhang1993 opened a new pull request, #20: URL: https://github.com/apache/flink-connector-mongodb/pull/20 This PR change the ci to use the release version 1.16.2, 1.17.1, 1.18.0 instead of Flink SNAPSHOT version. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-33795] Add new config to forbid autoscaling in certain periods of a day [flink-kubernetes-operator]
flashJd commented on code in PR #728:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/728#discussion_r1426763317
##
flink-autoscaler/src/main/java/org/apache/flink/autoscaler/config/AutoScalerOptions.java:
##
@@ -72,6 +72,15 @@ private static ConfigOptions.OptionBuilder
autoScalerConfig(String key) {
.withDescription(
"Stabilization period in which no new scaling will
be executed");
+public static final ConfigOption> FORBID_PERIOD =
+autoScalerConfig("forbid.periods")
+.stringType()
+.asList()
+.defaultValues()
+
.withDeprecatedKeys(deprecatedOperatorConfigKey("forbid.periods"))
+.withDescription(
+"A (semicolon-separated) list of certain times of
the day during which autoscaling is forbidden,
10:00:00-11:00:00;21:30:00-22:30:00 for example");
Review Comment:
Quartz's DailyCalendar along with CronCalendar allows `daily excluded,
days of the week/month excluded, etc.`
I've updated the config and implemented it, looking forward for the review.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] [FLINK-33603][Filesystem] Bundle Guava for GCS connector [flink]
snuyanzin commented on code in PR #23920: URL: https://github.com/apache/flink/pull/23920#discussion_r1426753864 ## flink-filesystems/flink-gs-fs-hadoop/src/main/resources/META-INF/NOTICE: ## @@ -32,6 +32,7 @@ This project bundles the following dependencies under the Apache Software Licens - com.google.flogger:flogger-system-backend:0.7.1 - com.google.flogger:flogger:0.7.1 - com.google.flogger:google-extensions:0.7.1 +- com.google.guava:guava:31.1-jre Review Comment: is it ok to have guava 31.1 here if current google-cloud-storage depends on 32.1.2 ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-33795] Add new config to forbid autoscaling in certain periods of a day [flink-kubernetes-operator]
flashJd commented on code in PR #728:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/728#discussion_r1426755281
##
flink-autoscaler/src/test/java/org/apache/flink/autoscaler/MetricsCollectionAndEvaluationTest.java:
##
@@ -599,6 +602,73 @@ public void testMetricCollectionDuringStabilization()
throws Exception {
assertEquals(2, stateStore.getCollectedMetrics(context).size());
}
+@Test
+public void testMetricCollectionDuringForbidden() throws Exception {
Review Comment:
I want to test this config along with config STABILIZATION_INTERVAL and
METRICS_WINDOW, so put it here
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] [FLINK-33603][Filesystem] Bundle Guava for GCS connector [flink]
snuyanzin commented on code in PR #23920: URL: https://github.com/apache/flink/pull/23920#discussion_r1426753864 ## flink-filesystems/flink-gs-fs-hadoop/src/main/resources/META-INF/NOTICE: ## @@ -32,6 +32,7 @@ This project bundles the following dependencies under the Apache Software Licens - com.google.flogger:flogger-system-backend:0.7.1 - com.google.flogger:flogger:0.7.1 - com.google.flogger:google-extensions:0.7.1 +- com.google.guava:guava:31.1-jre Review Comment: is it ok to hava guava 31.1 here if current google-cloud-storage depends on 32.1.2 ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-33795] Add new config to forbid autoscaling in certain periods of a day [flink-kubernetes-operator]
flashJd commented on code in PR #728:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/728#discussion_r1426752508
##
flink-autoscaler/src/main/java/org/apache/flink/autoscaler/config/AutoScalerOptions.java:
##
@@ -72,6 +72,15 @@ private static ConfigOptions.OptionBuilder
autoScalerConfig(String key) {
.withDescription(
"Stabilization period in which no new scaling will
be executed");
+public static final ConfigOption> FORBID_PERIOD =
+autoScalerConfig("forbid.periods")
+.stringType()
+.asList()
+.defaultValues()
+
.withDeprecatedKeys(deprecatedOperatorConfigKey("forbid.periods"))
Review Comment:
deleted
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] [FLINK-33764] Track Heap usage and GC pressure to avoid unnecessary scaling [flink-kubernetes-operator]
mxm commented on code in PR #726:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/726#discussion_r1426749088
##
flink-autoscaler/src/main/java/org/apache/flink/autoscaler/config/AutoScalerOptions.java:
##
@@ -219,6 +219,22 @@ private static ConfigOptions.OptionBuilder
autoScalerConfig(String key) {
.withDescription(
"Processing rate increase threshold for detecting
ineffective scaling threshold. 0.1 means if we do not accomplish at least 10%
of the desired capacity increase with scaling, the action is marked
ineffective.");
+public static final ConfigOption GC_PRESSURE_THRESHOLD =
+autoScalerConfig("memory.gc-pressure.threshold")
+.doubleType()
+.defaultValue(0.3)
+
.withFallbackKeys(oldOperatorConfigKey("memory.gc-pressure.threshold"))
+.withDescription(
+"Max allowed GC pressure (percentage spent garbage
collecting) during scaling operations. Autoscaling will be paused if the GC
pressure exceeds this limit.");
+
+public static final ConfigOption HEAP_USAGE_THRESHOLD =
+autoScalerConfig("memory.heap-usage.threshold")
+.doubleType()
+.defaultValue(1.)
+
.withFallbackKeys(oldOperatorConfigKey("memory.heap-usage.threshold"))
Review Comment:
I agree, we should support the old-style config namespace until the next
major release. The overhead of this is very low and our users do not have to
worry about using the right prefix for their configuration. As things stand,
even if we removed the old namespace, we would have to add a mapping in the
operator (either public our in our fork) because it is not feasible to go to
every user to ask them to change their configs.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] [FLINK-33795] Add new config to forbid autoscaling in certain periods of a day [flink-kubernetes-operator]
flashJd commented on code in PR #728:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/728#discussion_r1426748818
##
flink-autoscaler/src/main/java/org/apache/flink/autoscaler/JobAutoScalerImpl.java:
##
@@ -96,6 +97,13 @@ public void scale(Context ctx) throws Exception {
return;
}
+if (!AutoScalerUtils.verifyForbidPeriods(ctx.getConfiguration())) {
Review Comment:
removed to `DefaultValidator`
##
flink-autoscaler/src/main/java/org/apache/flink/autoscaler/ScalingMetricCollector.java:
##
@@ -114,6 +115,7 @@ public CollectedMetricHistory updateMetrics(
var topology = getJobTopology(ctx, stateStore, jobDetailsInfo);
var stableTime =
jobUpdateTs.plus(conf.get(AutoScalerOptions.STABILIZATION_INTERVAL));
final boolean isStabilizing = now.isBefore(stableTime);
+final boolean isForbidding = AutoScalerUtils.inForbidPeriod(conf, now);
Review Comment:
fixed
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] [FLINK-20772][State] Make TtlValueState#update follow the description of interface about null values [flink]
Zakelly commented on PR #23928: URL: https://github.com/apache/flink/pull/23928#issuecomment-1855894096 @masteryhx Would you please to take a look? Thanks -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-33795] Add new config to forbid autoscaling in certain periods of a day [flink-kubernetes-operator]
flashJd commented on code in PR #728:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/728#discussion_r1426747605
##
flink-autoscaler/src/test/java/org/apache/flink/autoscaler/utils/AutoScalerUtilsTest.java:
##
@@ -56,4 +60,30 @@ public void testVertexExclusion() {
Set.of(v1.toString(), v2.toString(), v3.toString()),
new HashSet<>(conf.get(AutoScalerOptions.VERTEX_EXCLUDE_IDS)));
}
+
+@Test
+public void testForbidPeriods() {
Review Comment:
renamed to `testExcludedPeriods()`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] [FLINK-33764] Track Heap usage and GC pressure to avoid unnecessary scaling [flink-kubernetes-operator]
gyfora commented on code in PR #726:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/726#discussion_r1426736930
##
flink-autoscaler/src/main/java/org/apache/flink/autoscaler/config/AutoScalerOptions.java:
##
@@ -219,6 +219,22 @@ private static ConfigOptions.OptionBuilder
autoScalerConfig(String key) {
.withDescription(
"Processing rate increase threshold for detecting
ineffective scaling threshold. 0.1 means if we do not accomplish at least 10%
of the desired capacity increase with scaling, the action is marked
ineffective.");
+public static final ConfigOption GC_PRESSURE_THRESHOLD =
+autoScalerConfig("memory.gc-pressure.threshold")
+.doubleType()
+.defaultValue(0.3)
+
.withFallbackKeys(oldOperatorConfigKey("memory.gc-pressure.threshold"))
+.withDescription(
+"Max allowed GC pressure (percentage spent garbage
collecting) during scaling operations. Autoscaling will be paused if the GC
pressure exceeds this limit.");
+
+public static final ConfigOption HEAP_USAGE_THRESHOLD =
+autoScalerConfig("memory.heap-usage.threshold")
+.doubleType()
+.defaultValue(1.)
+
.withFallbackKeys(oldOperatorConfigKey("memory.heap-usage.threshold"))
Review Comment:
After a brief discussion with @mxm offline, we feel that it's easiest and
harmless to keep the fallback keys consistent for all options. We may be able
to remove these at a future point (a new major version of the operator) but
it's simply better to have a consistent fallback syntax for operator users.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] [FLINK-31049] [flink-connector-kafka]Add support for Kafka record headers to KafkaSink [flink-connector-kafka]
Sandrock431 commented on PR #18: URL: https://github.com/apache/flink-connector-kafka/pull/18#issuecomment-1855859711 We're eagerly awaiting this change as well, and it's not in `3.0.2-1.18` either. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
