Sorry Chesnay, we have discussed when will remove 1.6.3 files, when we
added the 1.6.4 files. Just like Robert mentioned above!
Anyway thanks for your reminder @Chesnay Schepler <ches...@apache.org>!
And thanks for your big help @Robert Metzger <rmetz...@apache.org>!

Best,
Jincheng

Robert Metzger <rmetz...@apache.org> 于2019年2月27日周三 下午8:48写道:

> Sorry, this was somewhere on my TODO list to remove.
>
> We added the 1.6.4 files on Friday afternoon, but announced the
> release/updated the website on Monday morning. That's why I didn't want
> remove the files before the links have been updated.
>
> On Wed, Feb 27, 2019 at 10:57 AM Chesnay Schepler <ches...@apache.org>
> wrote:
>
> > Note that for future releases the files for the previous version (in
> > this case 1.6.3) should also be removed once the website was updated.
> >
> > I have taken care of this already.
> >
> > On 26.02.2019 05:12, Thomas Weise wrote:
> > > Jincheng, thanks for running the release!
> > >
> > > Please also send the announcement to user@ and annou...@apache.org
> > (using
> > > your @apache.org address)
> > >
> > >
> > > On Mon, Feb 25, 2019 at 4:26 AM Till Rohrmann <trohrm...@apache.org>
> > wrote:
> > >
> > >> Thanks Jincheng for being our release manager. Great job!
> > >>
> > >> On Mon, Feb 25, 2019 at 10:48 AM Fabian Hueske <fhue...@gmail.com>
> > wrote:
> > >>
> > >>> Thanks Jincheng for being the release manager!
> > >>>
> > >>> Am Mo., 25. Feb. 2019 um 09:49 Uhr schrieb Robert Metzger <
> > >>> rmetz...@apache.org>:
> > >>>
> > >>>> Thank you Jincheng for running this release!
> > >>>> I've also tweeted about it from @ApacheFlink:
> > >>>> https://twitter.com/ApacheFlink/status/1099954183741022208
> > >>>>
> > >>>> On Mon, Feb 25, 2019 at 4:04 AM Jark Wu <imj...@gmail.com> wrote:
> > >>>>
> > >>>>> Thanks for being the release manager Jingcheng.
> > >>>>> The 1.6.4 release contains a couple of important fixes.
> > >>>>> Thank you and the community for all the hard work which made this
> > >>> release
> > >>>>> possible.
> > >>>>>
> > >>>>> Best,
> > >>>>> Jark
> > >>>>>
> > >>>>> On Mon, 25 Feb 2019 at 10:09, vino yang <yanghua1...@gmail.com>
> > >> wrote:
> > >>>>>> @jincheng sun <sunjincheng...@gmail.com>  Thanks for being the
> > >>> release
> > >>>>>> manager. Great work!
> > >>>>>> Glad to see Flink 1.6.4!
> > >>>>>>
> > >>>>>> Best,
> > >>>>>> Vino
> > >>>>>>
> > >>>>>> Hequn Cheng <chenghe...@gmail.com> 于2019年2月25日周一 上午9:51写道:
> > >>>>>>
> > >>>>>>> Thanks Jincheng for managing the release and everybody who
> > >>>> contributed!
> > >>>>>>> Best, Hequn
> > >>>>>>>
> > >>>>>>> On Mon, Feb 25, 2019 at 9:46 AM jincheng sun <
> > >>>> sunjincheng...@gmail.com
> > >>>>>>> wrote:
> > >>>>>>>
> > >>>>>>>> Hi,
> > >>>>>>>>
> > >>>>>>>> The Apache Flink community is very happy to announce the
> > >> release
> > >>> of
> > >>>>>>>> Apache Flink 1.6.4, which is the fourth bugfix release for the
> > >>>> Apache
> > >>>>>>>> Flink 1.6 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/25/release-1.6.4.html
> > >>>>>>>>
> > >>>>>>>> The full release notes are available in Jira:
> > >>>>>>>>
> > >>>>>>>>
> > >>
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344627&styleName=Html&projectId=12315522
> > >>>>>>>> We would like to thank all contributors of the Apache Flink
> > >>>> community
> > >>>>>>>> who made this release possible!
> > >>>>>>>>
> > >>>>>>>> Special thanks to @Robert for his tremendous help during the
> > >>>>> release!!
> > >>>>>>>> Regards,
> > >>>>>>>> Jincheng
> > >>>>>>>>
> >
> >
>

Reply via email to