Thank you to all who contributed, and, of course, especially to the release
manager!

On Fri, Dec 28, 2018 at 10:12 AM Till Rohrmann <trohrm...@apache.org> wrote:

> Thanks a lot for being our release manager Thomas. Great work! Also thanks
> to the community for making this release possible.
>
> Cheers,
> Till
>
> On Thu, Dec 27, 2018 at 2:58 AM Jeff Zhang <zjf...@gmail.com> wrote:
>
>> Thanks Thomas. It's nice to have a more stable flink 1.5.x
>>
>> vino yang <yanghua1...@gmail.com> 于2018年12月27日周四 上午9:43写道:
>>
>>> Thomas, thanks for being a release manager.
>>> And Thanks for the whole community.
>>> I think the release of Flink 1.5.6 makes sense for many users who are
>>> currently unable to upgrade major versions.
>>>
>>> Best,
>>> Vino
>>>
>>> jincheng sun <sunjincheng...@gmail.com> 于2018年12月27日周四 上午8:00写道:
>>>
>>>> Thanks a lot for being our release manager Thomas.
>>>> Thanks a lot for made this release possible!
>>>>
>>>> Cheers,
>>>> Jincheng
>>>>
>>>> Thomas Weise <t...@apache.org> 于2018年12月27日周四 上午4:03写道:
>>>>
>>>>> The Apache Flink community is very happy to announce the release of
>>>>> Apache
>>>>> Flink 1.5.6, which is the final bugfix release for the Apache Flink 1.5
>>>>> 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:
>>>>> https://flink.apache.org/news/2018/12/22/release-1.5.6.html
>>>>>
>>>>> The full release notes are available in Jira:
>>>>>
>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12344315
>>>>>
>>>>> We would like to thank all contributors of the Apache Flink community
>>>>> who
>>>>> made this release possible!
>>>>>
>>>>> Regards,
>>>>> Thomas
>>>>>
>>>>
>>
>> --
>> Best Regards
>>
>> Jeff Zhang
>>
>

Reply via email to