RC1 creation is in progress ...

On Mon, Jan 23, 2017 at 10:33 AM, Robert Metzger <rmetz...@apache.org>
wrote:

> Hi all,
>
> I would like to do a proper voting RC1 early this week.
> From the issues mentioned here, most of them have pull requests or were
> changed to a lower priority.
> Once we've merged all outstanding PRs, I'll create the next RC.
>
> Regards,
> Robert
>
>
> On Mon, Jan 16, 2017 at 12:13 PM, Fabian Hueske <fhue...@gmail.com> wrote:
>
>> A user reported that outer joins on the Table API and SQL compute wrong
>> results:
>>
>> https://issues.apache.org/jira/browse/FLINK-5498
>>
>> 2017-01-15 20:23 GMT+01:00 Till Rohrmann <trohrm...@apache.org>:
>>
>> > I found two problematic issues with Mesos HA mode which breaks it:
>> >
>> > https://issues.apache.org/jira/browse/FLINK-5495
>> > https://issues.apache.org/jira/browse/FLINK-5496
>> >
>> > On Fri, Jan 13, 2017 at 11:29 AM, Fabian Hueske <fhue...@gmail.com>
>> wrote:
>> >
>> > > I tested the Table API / SQL a bit.
>> > >
>> > > I implemented a windowed aggregation with the streaming Table API and
>> it
>> > > produced the same results as a DataStream API implementation.
>> > > Joining a stream with a TableFunction also seemed to work well.
>> > > Moreover, I checked the results of a bunch of TPC-H queries (batch
>> SQL)
>> > > and all produced correct results.
>> > >
>> > >
>> > >
>> > > 2017-01-12 17:45 GMT+01:00 Till Rohrmann <trohrm...@apache.org>:
>> > >
>> > >> I'm wondering whether we should not depend the webserver encryption
>> on
>> > the
>> > >> global encryption activation and activating it instead per default.
>> > >>
>> > >> On Thu, Jan 12, 2017 at 4:54 PM, Chesnay Schepler <
>> ches...@apache.org>
>> > >> wrote:
>> > >>
>> > >> > FLINK-5470 is a duplicate of FLINK-5298 for which there is also an
>> > open
>> > >> PR.
>> > >> >
>> > >> > FLINK-5472 is imo invalid since the webserver does support https,
>> you
>> > >> just
>> > >> > have to enable it as per the security documentation.
>> > >> >
>> > >> >
>> > >> > On 12.01.2017 16:20, Till Rohrmann wrote:
>> > >> >
>> > >> > I also found an issue:
>> > >> >
>> > >> > https://issues.apache.org/jira/browse/FLINK-5470
>> > >> >
>> > >> > I also noticed that Flink's webserver does not support https
>> requests.
>> > >> It
>> > >> > might be worthwhile to add it, though.
>> > >> >
>> > >> > https://issues.apache.org/jira/browse/FLINK-5472
>> > >> >
>> > >> > On Thu, Jan 12, 2017 at 11:24 AM, Robert Metzger <
>> rmetz...@apache.org
>> > >
>> > >> > wrote:
>> > >> >
>> > >> >> I also found a bunch of issues
>> > >> >>
>> > >> >> https://issues.apache.org/jira/browse/FLINK-5465
>> > >> >> https://issues.apache.org/jira/browse/FLINK-5462
>> > >> >> https://issues.apache.org/jira/browse/FLINK-5464
>> > >> >> https://issues.apache.org/jira/browse/FLINK-5463
>> > >> >>
>> > >> >>
>> > >> >> On Thu, Jan 12, 2017 at 9:56 AM, Fabian Hueske < <
>> fhue...@gmail.com>
>> > >> >> fhue...@gmail.com> wrote:
>> > >> >>
>> > >> >> > I have another bugfix for 1.2.:
>> > >> >> >
>> > >> >> > https://issues.apache.org/jira/browse/FLINK-2662 (pending PR)
>> > >> >> >
>> > >> >> > 2017-01-10 15:16 GMT+01:00 Robert Metzger < <
>> rmetz...@apache.org>
>> > >> >> rmetz...@apache.org>:
>> > >> >> >
>> > >> >> > > Hi,
>> > >> >> > >
>> > >> >> > > this depends a lot on the number of issues we find during the
>> > >> testing.
>> > >> >> > >
>> > >> >> > >
>> > >> >> > > These are the issues I found so far:
>> > >> >> > >
>> > >> >> > > https://issues.apache.org/jira/browse/FLINK-5379 (unresolved)
>> > >> >> > > https://issues.apache.org/jira/browse/FLINK-5383 (resolved)
>> > >> >> > > https://issues.apache.org/jira/browse/FLINK-5382 (resolved)
>> > >> >> > > https://issues.apache.org/jira/browse/FLINK-5381 (resolved)
>> > >> >> > > https://issues.apache.org/jira/browse/FLINK-5380 (pending PR)
>> > >> >> > >
>> > >> >> > >
>> > >> >> > >
>> > >> >> > >
>> > >> >> > > On Tue, Jan 10, 2017 at 11:58 AM, shijinkui <
>> > shijin...@huawei.com>
>> > >> >> > wrote:
>> > >> >> > >
>> > >> >> > > > Do we have a probable time of 1.2 release? This month or
>> Next
>> > >> month?
>> > >> >> > > >
>> > >> >> > > > -----邮件原件-----
>> > >> >> > > > 发件人: Robert Metzger [mailto: <rmetz...@apache.org>
>> > >> >> rmetz...@apache.org]
>> > >> >> > > > 发送时间: 2017年1月3日 20:44
>> > >> >> > > > 收件人: d...@flink.apache.org
>> > >> >> > > > 抄送: user@flink.apache.org
>> > >> >> > > > 主题: [DISCUSS] Apache Flink 1.2.0 RC0 (Non-voting testing
>> > release
>> > >> >> > > candidate)
>> > >> >> > > >
>> > >> >> > > > Hi,
>> > >> >> > > >
>> > >> >> > > > First of all, I wish everybody a happy new year 2017.
>> > >> >> > > >
>> > >> >> > > > I've set user@flink in CC so that users who are interested
>> in
>> > >> >> helping
>> > >> >> > > > with the testing get notified. Please respond only to the
>> dev@
>> > >> >> list to
>> > >> >> > > > keep the discussion there!
>> > >> >> > > >
>> > >> >> > > > According to the 1.2 release discussion thread, I've
>> created a
>> > >> first
>> > >> >> > > > release candidate for Flink 1.2.
>> > >> >> > > > The release candidate will not be the final release, because
>> > I'm
>> > >> >> > certain
>> > >> >> > > > that we'll find at least one blocking issue in the
>> candidate :)
>> > >> >> > > >
>> > >> >> > > > Therefore, the RC is meant as a testing only release
>> candidate.
>> > >> >> > > > Please report every issue we need to fix before the next RC
>> in
>> > >> this
>> > >> >> > > thread
>> > >> >> > > > so that we have a good overview.
>> > >> >> > > >
>> > >> >> > > > The release artifacts are located here:
>> > >> >> > > > http://people.apache.org/~rmetzger/flink-1.2.0-rc0/
>> > >> >> > > >
>> > >> >> > > > The maven staging repository is located here:
>> > >> >> > > > https://repository.apache.org/
>> content/repositories/orgapache
>> > >> >> flink-1111
>> > >> >> > > >
>> > >> >> > > > The release commit (in branch "release-1.2.0-rc0"):
>> > >> >> > > > http://git-wip-us.apache.org/r
>> epos/asf/flink/commit/f3c59ced
>> > >> >> > > >
>> > >> >> > > >
>> > >> >> > > > Happy testing!
>> > >> >> > > >
>> > >> >> > >
>> > >> >> >
>> > >> >>
>> > >> >
>> > >> >
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
>
>

Reply via email to