>From the list [1], not many of the JIRAs have been fixed. I think it would be nice to put the RC for 1.3.1 out this week, given that multiple users have complained about some issues in the 1.3.0 release.
[1] https://issues.apache.org/jira/issues/?jql=labels%20%3D%20flink-rel-1.3.1-blockers On Tue, Jun 6, 2017 at 10:58 AM, Tzu-Li (Gordon) Tai <tzuli...@apache.org> wrote: > After an offline discussion with Till, we decided to not include > FLINK-6763 and FLINK-6764 as blockers for 1.3.1, and only merge them for > 1.4.0 since they change serialization formats for checkpoints. > > In turn, I’ve included https://issues.apache.org/jira/browse/FLINK-6804 as > a 1.3.1 blocker. > > > On 2 June 2017 at 5:27:18 PM, Nico Kruber (n...@data-artisans.com) wrote: > > while fixing build issues - what about FLINK-6654? > > On Friday, 2 June 2017 11:05:34 CEST Robert Metzger wrote: > > Hi devs, > > > > I would like to release Apache Flink 1.3.1 with the following fixes: > > > > - FLINK-6812 Elasticsearch 5 release artifacts not published to Maven > > central > > - FLINK-6783 Wrongly extracted TypeInformations for > > WindowedStream::aggregate > > - FLINK-6780 ExternalTableSource should add time attributes in the row > type > > - FLINK-6775 StateDescriptor cannot be shared by multiple subtasks > > - FLINK-6763 Inefficient PojoSerializerConfigSnapshot serialization > format > > - FLINK-6764 Deduplicate stateless TypeSerializers when serializing > > composite TypeSerializers > > > > Is there anything else that we need to wait for before we vote on the > first > > RC? > > > > > > Regards, > > Robert > >
