The list from Kostas also contained the new JobManager front end. Do we want to enable it by default in the 0.10 release?
Are we going to keep the old interface, or are we removing it? I'm voting for enabling the new one by default and keeping the old one for the next release. What do you think? On Tue, Sep 29, 2015 at 8:41 PM, Henry Saputra <henry.sapu...@gmail.com> wrote: > Oops, I meant Spargel [1] =) > > [1] > https://ci.apache.org/projects/flink/flink-docs-master/libs/spargel_guide.html > > On Tue, Sep 29, 2015 at 7:59 AM, Henry Saputra <henry.sapu...@gmail.com> > wrote: > > +1 to the idea. > > > > I also think we need to remove Pregel if Gelly wants to graduate. It > already > > deprecated in 0.9. > > > > - Henry > > > > > > On Tuesday, September 29, 2015, Kostas Tzoumas <ktzou...@apache.org> > wrote: > >> > >> Hi everyone, > >> > >> I would like to propose to cancel the 0.10-milestone release and go > >> directly for a 0.10 release as soon as possible. > >> > >> My opinion would be to focus this release on: > >> - Graduating the streaming API out of staging (depends on some open pull > >> requests) > >> - Master high availability > >> - New monitoring framework > >> - Graduating Gelly out of staging > >> > >> Flink 1.0 will probably come after 0.10, which gives us time to fix open > >> issues and freeze APIs. > >> > >> What do you think? > >> > >> Best, > >> Kostas >
