I've published the announcement: http://flink.apache.org/news/2015/06/24/announcing-apache-flink-0.9.0-release.html
Let me know if anything is not right. Otherwise, please spread the word! Cheers, Max On Wed, Jun 24, 2015 at 1:59 PM, Maximilian Michels <m...@apache.org> wrote: > Thanks for your feedback. We managed to improve the initial document quite > a bit. The thing about the known issues is that it might give a false > impression to people reading the release announcement because the real > issues we are working on, can hardly be summarized by a couple of JIRA > issues. Of course we will fix those JIRA issues (and I made sure this is > reflected in JIRA) but the right place for keeping track of them IMHO is > not the release announcement. With that in mind, I have removed the known > issues section. > > I'm converting the document to markdown now to publish it. The website is > already set up for the 0.9.0. > > On Wed, Jun 24, 2015 at 1:39 PM, Vasiliki Kalavri < > vasilikikala...@gmail.com> wrote: > >> Hi, >> >> thank you Max for the nice document! >> Can we please add FLINK-2271 to the list of known issues? >> >> -Vasia. >> >> On 24 June 2015 at 13:08, Stephan Ewen <se...@apache.org> wrote: >> >> > I like the announcement now. >> > >> > Would like to add a note to Gelly and Flink ML that these are early >> > versions of the libraries, that they are subject to changes and not yet >> > performance optimized. >> > >> > On Wed, Jun 24, 2015 at 1:07 PM, Stephan Ewen <se...@apache.org> wrote: >> > >> > > I reworked the text on streaming fault tolerance. >> > > >> > > I think the release announcement needs to be about the core >> > > points/improvements, rather than have many exact details. We post a >> link >> > > for details for those interested in the details. >> > > >> > > >> > > On Wed, Jun 24, 2015 at 11:32 AM, Aljoscha Krettek < >> aljos...@apache.org> >> > > wrote: >> > > >> > >> I fixed a typo in the state checkpoint text: "In case *of *recovery". >> > >> >> > >> On Wed, 24 Jun 2015 at 10:34 Maximilian Michels <m...@apache.org> >> wrote: >> > >> >> > >> > Thanks for your contributions. Now that the release artifacts are >> > >> published >> > >> > on the Maven repositories, I would like to get out the release >> > >> > announcement. If nobody has anything to add, I will do a final pass >> > and >> > >> > publish the announcement. >> > >> > >> > >> > On Tue, Jun 23, 2015 at 3:22 PM, Stephan Ewen <se...@apache.org> >> > wrote: >> > >> > >> > >> > > I also like a separate paragraph about it :-) >> > >> > > >> > >> > > On Tue, Jun 23, 2015 at 3:20 PM, Robert Metzger < >> > rmetz...@apache.org> >> > >> > > wrote: >> > >> > > >> > >> > > > I would add a separate paragraph about it! >> > >> > > > >> > >> > > > On Tue, Jun 23, 2015 at 2:21 PM, Timo Walther < >> twal...@apache.org >> > > >> > >> > > wrote: >> > >> > > > >> > >> > > > > Is the static code analysis thing worth it to write a >> paragraph >> > >> about >> > >> > > it >> > >> > > > > or is better located in the "More Improvements and Fixes" >> > section? >> > >> > > > > >> > >> > > > > >> > >> > > > > On 23.06.2015 14:13, Márton Balassi wrote: >> > >> > > > > >> > >> > > > >> Thanks, Max. I would like to present the streaming stuff a >> bit >> > >> > > > >> differently, >> > >> > > > >> updating it. >> > >> > > > >> >> > >> > > > >> On Tue, Jun 23, 2015 at 1:59 PM, Maximilian Michels < >> > >> m...@apache.org >> > >> > > >> > >> > > > >> wrote: >> > >> > > > >> >> > >> > > > >> Hi everyone, >> > >> > > > >>> >> > >> > > > >>> With the vote now being passed, we should think about the >> > >> release >> > >> > > > >>> announcement. I've created a document which basically >> contains >> > >> the >> > >> > > > >>> milestone release announcement with a few changes. >> > >> > > > >>> >> > >> > > > >>> >> > >> > > > >>> >> > >> > > > >>> >> > >> > > > >> > >> > > >> > >> > >> > >> >> > >> https://docs.google.com/document/d/1s5H0q961Ucvu6fR56RleY4oN4YFqmeGkN77XPPsco3k/edit#heading=h.5fiopdwccz0x >> > >> > > > >>> >> > >> > > > >>> Please feel free to make your comments and adjustments. >> > >> > > > >>> >> > >> > > > >>> Best, >> > >> > > > >>> Max >> > >> > > > >>> >> > >> > > > >>> >> > >> > > > > >> > >> > > > >> > >> > > >> > >> > >> > >> >> > > >> > > >> > >> > >
