flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Márton Balassi <balassi.mar...@gmail.com>
Subject Re: 0.7.1 maintenance release
Date Wed, 03 Dec 2014 09:28:47 GMT
It is a bit unclear for me how to proceed with this issue. If I understand
it correctly the votes were more for a smaller bugfix release than for
adding most of the code since 0.7.0, but correct me if I'm wrong.

Robert and Till assembled the following list fot commits to be included

[FLINK-1154] Quickfix to kill TaskManagers in YARN mode.
[runtime] CaseClassSerializer correctly treated as stateful
[runtime] Quick fix for error with unsupported ship strategy
[FLINK-1265] Fix user classloader bug for registerInputOutput() method
[FLINK-1252] Add support for serializing Date and Enums in the Java API
[FLINK-1251] Enums are now handled properly by the collection input format
[FLINK-1254] [compiler] Fix compiler bug for pipeline breaker placement
[streaming] StreamExecutionEnvironment rework + user class loader fix for
cluster deployment 6867f9b93ec1ad9a627450c4fbd0b5ff98ef6148
[FLINK-1235] Compiler accepts iterations referenced from the static path of
other iterations 21b1b975ccb50e1831172894bde96c6d3269dc57
Removed TypeSerializerFactory from ScalaCsvInputFormat. The TypeSerializer
is now serialized directly. 3d242fd7aea6add18465d628a258be11def2d0af

And of course the doc fixes that are alredy on the release-0.7 branch. I'd
like to push these to the release-0.7 branch and fork release-0.7.1 from it



On Mon, Dec 1, 2014 at 5:35 PM, Fabian Hueske <fhueske@apache.org> wrote:

> I agree with Ufuk.
> +1 for putting this out as a minor release (0.7.1).
> 2014-12-01 17:27 GMT+01:00 Ufuk Celebi <uce@apache.org>:
> > On Mon, Dec 1, 2014 at 4:45 PM, Robert Metzger <rmetzger@apache.org>
> > wrote:
> >
> > > 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.
> > >
> >
> > I think it is reasonable to have new major versions for new major
> features.
> > Since we don't have any new major features, we should stick to 0.7.1.
> >
> >
> > The amount of required work for making a bugfix or a major release is
> > > basically the same.
> > >
> >
> > I would actually say that a bugfix release requires more work. ;-)
> >

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