flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Metzger <rmetz...@apache.org>
Subject Re: 0.7.1 maintenance release
Date Mon, 01 Dec 2014 15:45:53 GMT
If the bugfix release is going to include almost all commits of the current
0.8-SNAPSHOT version, we should consider releasing it as Flink 0.8.0.

The amount of required work for making a bugfix or a major release is
basically the same.

On Mon, Dec 1, 2014 at 3:57 PM, Stephan Ewen <sewen@apache.org> wrote:

> Would it be simpler to list what we not include? I think most of the stuff
> added since then is fixes, not fundamental features. I would include almost
> all of it, also the closure cleaner, the type fixes, ...
>
> On Mon, Dec 1, 2014 at 1:59 PM, Till Rohrmann <till.rohrmann@gmail.com>
> wrote:
>
> > If we include the commit
> >
> > [runtime] CaseClassSerializer correctly treated as stateful
> > f66892d46d80d453a55fd0ae14095ee06275a55d
> >
> > then we also have to include
> >
> > 3d242fd7aea6add18465d628a258be11def2d0af
> >
> > because the ScalaCsvInputFormat using the CaseClassSerializer won't work
> > properly anymore with the CaseClassSerializer set to be stateful.
> >
> >
> > On Mon, Dec 1, 2014 at 12:50 PM, Ufuk Celebi <uce@apache.org> wrote:
> >
> > > On Mon, Dec 1, 2014 at 12:15 PM, Robert Metzger <rmetzger@apache.org>
> > > wrote:
> > >
> > > > I would not include issues that cause bad performance, fix testcases
> or
> > > > code-style. I would rather prefer to aim for a 0.8 release soon
> (maybe
> > a
> > > > Christmas or new year release ;) )
> > > >
> > >
> > >
> > > Is there a performance-critical commit, which would be *more* work to
> > back
> > > port than the other commits? If not, I don't see any reason to exclude
> > > them.
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message