+1.

I think adding the TypeHints pull request to the release is a good idea.
This allows us to give users a workaround if the type extraction is not
working.

I'll have a look at the Hbase hadoop1 support.

On Wed, Dec 10, 2014 at 7:35 PM, Stephan Ewen <se...@apache.org> wrote:

> Hi everyone!
>
> I would suggest to fork a 0.8 release branch very soon, to not stall the
> development of features that go into 0.9. The new Akka based coordination
> and the network stack extensions are required for many new features which
> are in the pipeline.
>
> How about we merge the below listed pull requests into the master, and then
> branch the 0.8 release branch off and bump the master version to
> 0.9-SNAPSHOT.
>
> After we have forked the release branch, Marton (as release manager) would
> create release candidates and collect status of the tests and patches. We
> can fix bugs on the release branch and cherry-pick the patches to the
> 0.9-SNAPSHOT branch.
>
> ----------------------------------------------
> Important Pull Requests to merge:
> ----------------------------------------------
>
> [FLINK-1287] LocalizableSplitAssigner prefers splits with less degrees of
> freedom
>
> Fixed java quickstart example
>
> [FLINK-998] Close TCP connections after destroying logical channels
>
> [FLINK-1302] Make JDBCInputFormat implement the NonParallelInput interface
>
> [FLINK-1305] [FLINK-1304] Test for HadoopInputWrapper and NullWritable
> support
>
> Upgraded HBase addon to HBase 0.98.x and new Tuple APIs + fix of
> ExecutionEnvironment
> (this is partially merged, there are a few POM entries missing for Hadoop 1
> support)
>
>
> ----------------------------------------------
> Optional Pull Requests to merge:
> ----------------------------------------------
>
> Add support for Subclasses, Interfaces, Abstract Classes as POJOs
>
> [FLINK-1245] Introduce TypeHints for Java API operators
>
> enable CSV Reader to ignore invalid lines like an empty line at the end and
> comments - FLINK-1208
>
>
> Please veto the important pull requests (if they should not go in) and +1
> or -1 the optional ones, as you deem fitting.
>
>
> Greetings,
> Stephan
>

Reply via email to