Thank you Gordon!

Help spread the word here:
https://twitter.com/ApacheFlink/status/1097416946688102401



On Mon, Feb 18, 2019 at 7:41 AM Dian Fu <dian0511...@gmail.com> wrote:

> Great job. It's great to have a more stable 1.7 release available. Thanks
> @Gordon for making it happen.
>
> Regards,
> Dian
>
> 在 2019年2月18日,下午2:26,vino yang <yanghua1...@gmail.com> 写道:
>
> Great job! Thanks for being the release manager @Gordon.
>
> Best,
> Vino
>
> Hequn Cheng <chenghe...@gmail.com> 于2019年2月18日周一 下午2:16写道:
>
>> Thanks a lot for the great release @Gordon.
>> Also thanks for the work by the whole community. :-)
>>
>> Best, Hequn
>>
>>
>> On Mon, Feb 18, 2019 at 2:12 PM jincheng sun <sunjincheng...@gmail.com>
>> wrote:
>>
>> > Thanks a lot for being our release manager Gordon <tzuli...@apache.org
>> >,
>> > Great job!
>> >  And also a big thanks to the community for making this release
>> possible.
>> >
>> > Cheers,
>> > Jincheng
>> >
>> >
>> > Tzu-Li (Gordon) Tai <tzuli...@apache.org> 于2019年2月18日周一 上午10:29写道:
>> >
>> >> Hi,
>> >>
>> >> The Apache Flink community is very happy to announce the release of
>> >> Apache Flink 1.7.2, which is the second bugfix release for the Apache
>> >> Flink 1.7 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
>> >> <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/2019/02/15/release-1.7.2.html
>> >>
>> >> The full release notes are available in Jira:
>> >>
>> >>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12344632
>> >>
>> >> We would like to thank all contributors of the Apache Flink community
>> >> who made this release possible!
>> >>
>> >> Regards,
>> >> Gordon
>> >>
>> >
>>
>
>

Reply via email to