-
Notifications
You must be signed in to change notification settings - Fork 303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Apache Flink release 1.8.3 #285
Conversation
cd43ae3
to
9050e36
Compare
_posts/2019-11-27-release-1.8.3.md
Outdated
|
||
The Apache Flink community released the third bugfix version of the Apache Flink 1.8 series. | ||
|
||
This release includes 23 fixes and minor improvements for Flink 1.8.2. The list below includes a detailed list of all fixes and improvements. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They are 42 fixes and improvements included in this release according to the release note.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch!
9050e36
to
8bf2732
Compare
@dianfu Thanks, I have updated the PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will you need someone to generate the website?
<h2> Bug | ||
</h2> | ||
<ul> | ||
<li>[<a href='https://issues.apache.org/jira/browse/FLINK-12342'>FLINK-12342</a>] - Yarn Resource Manager Acquires Too Many Containers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I went over the release notes and updated a few JIRA titles and categories; so this needs to be updated beyond FLINK-14995
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for the update and fixing the license problem. I will update this PR once FLINK-14995 is addressed.
I originally planned to generate during merge, but I think we can generate the website and add an additional commit in this PR. It will be more friendly for the reviewers. What do you think? |
8bf2732
to
f0caa3b
Compare
Update the PR according to RC2. Changes mainly include:
@zentol @dianfu Would be great if you can take a look. Thanks. |
f0caa3b
to
79e44d0
Compare
Update the PR according to RC3. Changes mainly include:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR @hequn8128
I just left some reminder.
Best,
Jincheng
- | ||
version_short: 1.8 | ||
version_long: 1.8.3 | ||
release_date: 2019-11-27 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just reminder: Update the date when merging. :)
--- | ||
layout: post | ||
title: "Apache Flink 1.8.3 Released" | ||
date: 2019-11-27 12:00:00 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just reminder: Update the date when merging. :)
<article> | ||
<h2 class="blog-title"><a href="/news/2019/11/27/release-1.8.3.html">Apache Flink 1.8.3 Released</a></h2> | ||
|
||
<p>27 Nov 2019 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just reminder: Update the date when merging. :)
@sunjincheng121 Thanks a lot for the review. You are right, we should update the time during merging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for creating this PR @hequn8128. The release blog post looks good to me. +1 for merging once 1.8.3
has been released.
@tillrohrmann Thank you for the reminder. I will adjust the date, regenerate the docs and merge it after the release. |
Thanks @hequn8128 for preparing this PR. It looks good to me. Just a suggestion: it would be bettter to exclude the generated file (files under Once 1.8.3 is released, you can rebuild website and append a commit for the generated files on this commit and merge them. |
@wuchong Thanks for the review. I was thinking that adding the generated files can let reviewers check whether there is anything that has been missed. Especially this is my first time to do a release. But I think your point also makes sense as it can avoid the conflict. |
Adds release announcement and download link for 1.8.3
Dates on announcements are still TBD and should be updated accordingly once release happens.