flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Metzger <rmetz...@apache.org>
Subject Re: 0.6-incubating release
Date Wed, 16 Jul 2014 08:14:13 GMT
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:

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 <u.celebi@fu-berlin.de> 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

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