0.6-incubating release

[Ufuk Celebi]

Hey all,

thanks to Stephan and Robert for taking care of the renaming and pushing it so fast. With this out of the way, we are heading for our first Apache release. :)

If I understand the ASF document [1] correctly, we will need a release manager. I would propose to have Robert [~rmetzger] do it as he has prior experience with this and also the code publishing. He can then initiate the release vote at some point.

@Robert: do you agree?

But before we can start on a vote for the release, there are some issues, which need to be addressed in any case:

1) Resolve the breaking API changes:

I've labeled the breaking API issues: https://issues.apache.org/jira/browse/FLINK-1023?jql=labels%20%3D%20breaking-api

It would be great if we had more comments for these issues to not have just few people decide these changes.

2) Resolve critical issues:

https://issues.apache.org/jira/browse/FLINK-1026?jql=project%20%3D%20FLINK%20AND%20priority%20%3D%20Critical

These are all assigned except for FLINK-629, which is imo important (I've pushed it to critical).

---

If anyone has more relevant information, please post it here. ;)

[1] http://www.apache.org/dev/release-publishing

[Robert Metzger]

Thanks for starting this!
I agree being a release manager. I did the last releases for Stratosphere
and know how the Maven / release stuff works.
This guide is also relevant for releasing:
http://incubator.apache.org/guides/releasemanagement.html

We should certainly have FLINK-629 fixed for the 0.6 release. I think
everyone I know who is using Flink stumbled into it.
Another issue that is affecting a lot of users is this one:
https://issues.apache.org/jira/browse/FLINK-610. I would really like to see
them both fixed in the 0.6 release

As a preparation for the release, I requested access (5 days ago) to the
Apache Maven infrastructure:
https://issues.apache.org/jira/browse/INFRA-8026 (we also need this for
publishing SNAPSHOT versions)
I will look into the details of requesting a dist space where we can
distribute the release binaries.



On Wed, Jul 16, 2014 at 9:52 AM, Ufuk Celebi <[hidden email]> wrote:

> Hey all,
>
> thanks to Stephan and Robert for taking care of the renaming and pushing
> it so fast. With this out of the way, we are heading for our first Apache
> release. :)
>
> If I understand the ASF document [1] correctly, we will need a release
> manager. I would propose to have Robert [~rmetzger] do it as he has prior
> experience with this and also the code publishing. He can then initiate the
> release vote at some point.
>
> @Robert: do you agree?
>
> But before we can start on a vote for the release, there are some issues,
> which need to be addressed in any case:
>
> 1) Resolve the breaking API changes:
>
> I've labeled the breaking API issues:
> https://issues.apache.org/jira/browse/FLINK-1023?jql=labels%20%3D%20breaking-api
>
> It would be great if we had more comments for these issues to not have
> just few people decide these changes.
>
> 2) Resolve critical issues:
>
>
> https://issues.apache.org/jira/browse/FLINK-1026?jql=project%20%3D%20FLINK%20AND%20priority%20%3D%20Critical
>
> These are all assigned except for FLINK-629, which is imo important (I've
> pushed it to critical).
>
> ---
>
> If anyone has more relevant information, please post it here. ;)
>
> [1] http://www.apache.org/dev/release-publishing

[Ufuk Celebi]

On 16 Jul 2014, at 10:14, Robert Metzger <[hidden email]> wrote:

> Thanks for starting this!
> I agree being a release manager. I did the last releases for Stratosphere
> and know how the Maven / release stuff works.
> This guide is also relevant for releasing:
> http://incubator.apache.org/guides/releasemanagement.html
>
> We should certainly have FLINK-629 fixed for the 0.6 release. I think
> everyone I know who is using Flink stumbled into it.
> Another issue that is affecting a lot of users is this one:
> https://issues.apache.org/jira/browse/FLINK-610. I would really like to see
> them both fixed in the 0.6 release

+1

I also think that this is important.

[Stephan Ewen]

Okay. Let's make an estimate how long we take to resolve the critical
issues.

[Robert Metzger]

It seems that we don't have to request a special distribution directory.
That seems to apply only to top-level projects.
I'm going to familiarize myself with the keying infrastructure and I'll
probably ask all committers at some point to provide their public keys.

I went through all "API breaking" issues and commented on them.

Isn't Till working on a preparatory task for FLINK-610?
Gyula has picked up FLINK-629.
Can you both give an estimate?




On Wed, Jul 16, 2014 at 12:32 PM, Stephan Ewen <[hidden email]> wrote:

> Okay. Let's make an estimate how long we take to resolve the critical
> issues.
>

[Márton Balassi]

As for FLINK-629:

I might aid Gyula with prepairing a couple of tests for the issue. It is
safe to estimate that it should be ready by Friday.



On Wed, Jul 16, 2014 at 2:20 PM, Robert Metzger <[hidden email]> wrote:

> It seems that we don't have to request a special distribution directory.
> That seems to apply only to top-level projects.
> I'm going to familiarize myself with the keying infrastructure and I'll
> probably ask all committers at some point to provide their public keys.
>
> I went through all "API breaking" issues and commented on them.
>
> Isn't Till working on a preparatory task for FLINK-610?
> Gyula has picked up FLINK-629.
> Can you both give an estimate?
>
>
>
>
> On Wed, Jul 16, 2014 at 12:32 PM, Stephan Ewen <[hidden email]> wrote:
>
> > Okay. Let's make an estimate how long we take to resolve the critical
> > issues.
> >
>

[till.rohrmann]

Yes I worked on FLINK-610 but had to postpone it a little bit due to my
thesis deadline. I can try to get it done until friday. But it's gonna be
tough with testing it thoroughly. But for this part of Flink it is
absolutely necessary.


On Wed, Jul 16, 2014 at 2:29 PM, Márton Balassi <[hidden email]>
wrote:

> As for FLINK-629:
>
> I might aid Gyula with prepairing a couple of tests for the issue. It is
> safe to estimate that it should be ready by Friday.
>
>
>
> On Wed, Jul 16, 2014 at 2:20 PM, Robert Metzger <[hidden email]>
> wrote:
>
> > It seems that we don't have to request a special distribution directory.
> > That seems to apply only to top-level projects.
> > I'm going to familiarize myself with the keying infrastructure and I'll
> > probably ask all committers at some point to provide their public keys.
> >
> > I went through all "API breaking" issues and commented on them.
> >
> > Isn't Till working on a preparatory task for FLINK-610?
> > Gyula has picked up FLINK-629.
> > Can you both give an estimate?
> >
> >
> >
> >
> > On Wed, Jul 16, 2014 at 12:32 PM, Stephan Ewen <[hidden email]> wrote:
> >
> > > Okay. Let's make an estimate how long we take to resolve the critical
> > > issues.
> > >
> >
>