Release Flink 0.10

[Kostas Tzoumas-2]

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

[mxm]

Hi Kostas,

I think it makes sense to cancel the proposed 0.10-milestone release.
We are not far away from completing all essential features of the 0.10
release. After we manage to complete those, we can test and release
0.10.

The 0.10 release will be a major step towards the 1.0 release and,
therefore, all new features of 0.10 should get enough exposure until
we release 1.0.

Cheers,
Max

On Tue, Sep 29, 2015 at 11:26 AM, Kostas Tzoumas <[hidden email]> 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

[Fabian Hueske-2]

+1 for moving directly to 0.10.

2015-09-29 11:40 GMT+02:00 Maximilian Michels <[hidden email]>:

> Hi Kostas,
>
> I think it makes sense to cancel the proposed 0.10-milestone release.
> We are not far away from completing all essential features of the 0.10
> release. After we manage to complete those, we can test and release
> 0.10.
>
> The 0.10 release will be a major step towards the 1.0 release and,
> therefore, all new features of 0.10 should get enough exposure until
> we release 1.0.
>
> Cheers,
> Max
>
> On Tue, Sep 29, 2015 at 11:26 AM, Kostas Tzoumas <[hidden email]>
> 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
>

[Stephan Ewen]

+1 here as well

On Tue, Sep 29, 2015 at 12:03 PM, Fabian Hueske <[hidden email]> wrote:

> +1 for moving directly to 0.10.
>
> 2015-09-29 11:40 GMT+02:00 Maximilian Michels <[hidden email]>:
>
> > Hi Kostas,
> >
> > I think it makes sense to cancel the proposed 0.10-milestone release.
> > We are not far away from completing all essential features of the 0.10
> > release. After we manage to complete those, we can test and release
> > 0.10.
> >
> > The 0.10 release will be a major step towards the 1.0 release and,
> > therefore, all new features of 0.10 should get enough exposure until
> > we release 1.0.
> >
> > Cheers,
> > Max
> >
> > On Tue, Sep 29, 2015 at 11:26 AM, Kostas Tzoumas <[hidden email]>
> > 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
> >
>

[Till Rohrmann]

+1 for 0.10

On Tue, Sep 29, 2015 at 12:12 PM, Stephan Ewen <[hidden email]> wrote:

> +1 here as well
>
> On Tue, Sep 29, 2015 at 12:03 PM, Fabian Hueske <[hidden email]> wrote:
>
> > +1 for moving directly to 0.10.
> >
> > 2015-09-29 11:40 GMT+02:00 Maximilian Michels <[hidden email]>:
> >
> > > Hi Kostas,
> > >
> > > I think it makes sense to cancel the proposed 0.10-milestone release.
> > > We are not far away from completing all essential features of the 0.10
> > > release. After we manage to complete those, we can test and release
> > > 0.10.
> > >
> > > The 0.10 release will be a major step towards the 1.0 release and,
> > > therefore, all new features of 0.10 should get enough exposure until
> > > we release 1.0.
> > >
> > > Cheers,
> > > Max
> > >
> > > On Tue, Sep 29, 2015 at 11:26 AM, Kostas Tzoumas <[hidden email]>
> > > 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
> > >
> >
>

[Aljoscha Krettek-2]

+1, seems to be a very sane thing to do

On Tue, 29 Sep 2015 at 12:20 Till Rohrmann <[hidden email]> wrote:

> +1 for 0.10
>
> On Tue, Sep 29, 2015 at 12:12 PM, Stephan Ewen <[hidden email]> wrote:
>
> > +1 here as well
> >
> > On Tue, Sep 29, 2015 at 12:03 PM, Fabian Hueske <[hidden email]>
> wrote:
> >
> > > +1 for moving directly to 0.10.
> > >
> > > 2015-09-29 11:40 GMT+02:00 Maximilian Michels <[hidden email]>:
> > >
> > > > Hi Kostas,
> > > >
> > > > I think it makes sense to cancel the proposed 0.10-milestone release.
> > > > We are not far away from completing all essential features of the
> 0.10
> > > > release. After we manage to complete those, we can test and release
> > > > 0.10.
> > > >
> > > > The 0.10 release will be a major step towards the 1.0 release and,
> > > > therefore, all new features of 0.10 should get enough exposure until
> > > > we release 1.0.
> > > >
> > > > Cheers,
> > > > Max
> > > >
> > > > On Tue, Sep 29, 2015 at 11:26 AM, Kostas Tzoumas <
> [hidden email]>
> > > > 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
> > > >
> > >
> >
>

[Vasiliki Kalavri]

+1 makes sense to me too.

On 29 September 2015 at 12:25, Aljoscha Krettek <[hidden email]> wrote:

> +1, seems to be a very sane thing to do
>
> On Tue, 29 Sep 2015 at 12:20 Till Rohrmann <[hidden email]> wrote:
>
> > +1 for 0.10
> >
> > On Tue, Sep 29, 2015 at 12:12 PM, Stephan Ewen <[hidden email]> wrote:
> >
> > > +1 here as well
> > >
> > > On Tue, Sep 29, 2015 at 12:03 PM, Fabian Hueske <[hidden email]>
> > wrote:
> > >
> > > > +1 for moving directly to 0.10.
> > > >
> > > > 2015-09-29 11:40 GMT+02:00 Maximilian Michels <[hidden email]>:
> > > >
> > > > > Hi Kostas,
> > > > >
> > > > > I think it makes sense to cancel the proposed 0.10-milestone
> release.
> > > > > We are not far away from completing all essential features of the
> > 0.10
> > > > > release. After we manage to complete those, we can test and release
> > > > > 0.10.
> > > > >
> > > > > The 0.10 release will be a major step towards the 1.0 release and,
> > > > > therefore, all new features of 0.10 should get enough exposure
> until
> > > > > we release 1.0.
> > > > >
> > > > > Cheers,
> > > > > Max
> > > > >
> > > > > On Tue, Sep 29, 2015 at 11:26 AM, Kostas Tzoumas <
> > [hidden email]>
> > > > > 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
> > > > >
> > > >
> > >
> >
>

[Henry Saputra]

+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 <[hidden email]> 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
>

[Henry Saputra]

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 <[hidden email]> 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 <[hidden email]> 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

[Robert Metzger]

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 <[hidden email]>
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 <[hidden email]>
> 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 <[hidden email]>
> 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
>

[Stephan Ewen]

I would actually like to remove the old one, but I am okay with keeping it
and activating the new one by default

On Fri, Oct 2, 2015 at 3:49 PM, Robert Metzger <[hidden email]> wrote:

> 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 <[hidden email]>
> 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 <[hidden email]>
> > 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 <[hidden email]>
> > 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
> >
>

[Robert Metzger]

The new one does not have access to the JobManager log file.
Also, the graphs for the TaskManagers are missing.


On Fri, Oct 2, 2015 at 3:51 PM, Stephan Ewen <[hidden email]> wrote:

> I would actually like to remove the old one, but I am okay with keeping it
> and activating the new one by default
>
> On Fri, Oct 2, 2015 at 3:49 PM, Robert Metzger <[hidden email]>
> wrote:
>
> > 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 <[hidden email]>
> > 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 <
> [hidden email]>
> > > 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 <[hidden email]>
> > > 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
> > >
> >
>

[Henry Saputra]

Robert, how hard it is to move these missing features to the new front end?

I prefer to remove the old one to prevent another duplicate things in Flink.

- Henry

On Fri, Oct 2, 2015 at 6:53 AM, Robert Metzger <[hidden email]> wrote:

> The new one does not have access to the JobManager log file.
> Also, the graphs for the TaskManagers are missing.
>
>
> On Fri, Oct 2, 2015 at 3:51 PM, Stephan Ewen <[hidden email]> wrote:
>
>> I would actually like to remove the old one, but I am okay with keeping it
>> and activating the new one by default
>>
>> On Fri, Oct 2, 2015 at 3:49 PM, Robert Metzger <[hidden email]>
>> wrote:
>>
>> > 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 <[hidden email]>
>> > 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 <
>> [hidden email]>
>> > > 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 <[hidden email]>
>> > > 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
>> > >
>> >
>>

[Robert Metzger]

Its not very hard to move the features to the new interface. I think the
main issue is time ;)
For the log file access, somebody has the JIRA assigned, but I don't know
when its done. Maybe the missing features make it to the master in time,
but I doubt it.
There are other issues with the new web interface, such as hard-coded
values, not very many tests, no user exposure yet, ...

On Fri, Oct 2, 2015 at 7:47 PM, Henry Saputra <[hidden email]>
wrote:

> Robert, how hard it is to move these missing features to the new front end?
>
> I prefer to remove the old one to prevent another duplicate things in
> Flink.
>
> - Henry
>
> On Fri, Oct 2, 2015 at 6:53 AM, Robert Metzger <[hidden email]>
> wrote:
> > The new one does not have access to the JobManager log file.
> > Also, the graphs for the TaskManagers are missing.
> >
> >
> > On Fri, Oct 2, 2015 at 3:51 PM, Stephan Ewen <[hidden email]> wrote:
> >
> >> I would actually like to remove the old one, but I am okay with keeping
> it
> >> and activating the new one by default
> >>
> >> On Fri, Oct 2, 2015 at 3:49 PM, Robert Metzger <[hidden email]>
> >> wrote:
> >>
> >> > 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 <
> [hidden email]>
> >> > 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 <
> >> [hidden email]>
> >> > > 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 <
> [hidden email]>
> >> > > 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
> >> > >
> >> >
> >>
>

[Ufuk Celebi-2]

I would like to remove it as well. I doubt that a lot of people will really
switch back to the old one. So we won't gain a lot by keeping it around imo.

On Sunday, October 4, 2015, Robert Metzger <[hidden email]> wrote:

> Its not very hard to move the features to the new interface. I think the
> main issue is time ;)
> For the log file access, somebody has the JIRA assigned, but I don't know
> when its done. Maybe the missing features make it to the master in time,
> but I doubt it.
> There are other issues with the new web interface, such as hard-coded
> values, not very many tests, no user exposure yet, ...
>
> On Fri, Oct 2, 2015 at 7:47 PM, Henry Saputra <[hidden email]
> <javascript:;>>
> wrote:
>
> > Robert, how hard it is to move these missing features to the new front
> end?
> >
> > I prefer to remove the old one to prevent another duplicate things in
> > Flink.
> >
> > - Henry
> >
> > On Fri, Oct 2, 2015 at 6:53 AM, Robert Metzger <[hidden email]
> <javascript:;>>
> > wrote:
> > > The new one does not have access to the JobManager log file.
> > > Also, the graphs for the TaskManagers are missing.
> > >
> > >
> > > On Fri, Oct 2, 2015 at 3:51 PM, Stephan Ewen <[hidden email]
> <javascript:;>> wrote:
> > >
> > >> I would actually like to remove the old one, but I am okay with
> keeping
> > it
> > >> and activating the new one by default
> > >>
> > >> On Fri, Oct 2, 2015 at 3:49 PM, Robert Metzger <[hidden email]
> <javascript:;>>
> > >> wrote:
> > >>
> > >> > 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 <
> > [hidden email] <javascript:;>>
> > >> > 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 <
> > >> [hidden email] <javascript:;>>
> > >> > > 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 <
> > [hidden email] <javascript:;>>
> > >> > > 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
> > >> > >
> > >> >
> > >>
> >
>