First Incubator Relase

classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

First Incubator Relase

Stephan Ewen
Hi everyone!

We just had a hangout discussion (see previous mails for minutes and
recording) where we talked about getting the first incubator release of
Flink out.

Legal is blocked on the trademark issue until we make a release and we
thought it cannot hurt to get the process started soon, because the first
release is going to take a while.


A suggestion we came up was to:

 - Do a feature-freeze now, collect a shortlist of crucial bugs (not even
"important enhancements") to fix, and start with the release process very
soon.

 - Concurrently add the critical improvements and other upcoming feature
patches to a different branch.

 - Once the release has been cleared and the release is out there, we
rebase the feature branch and continue from there.

It would give us the advantage to get out of the name limbo soon and
pipeline the legal overhead for the first release. The successive release
could be very soon after the initial one.

How do you feel about this?

Greetings,
Stephan
Reply | Threaded
Open this post in threaded view
|

Re: First Incubator Relase

Kostas Tzoumas
+1

Let us tackle the big things one at a time (and the first Apache release is
a big thing by itself)


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

> Hi everyone!
>
> We just had a hangout discussion (see previous mails for minutes and
> recording) where we talked about getting the first incubator release of
> Flink out.
>
> Legal is blocked on the trademark issue until we make a release and we
> thought it cannot hurt to get the process started soon, because the first
> release is going to take a while.
>
>
> A suggestion we came up was to:
>
>  - Do a feature-freeze now, collect a shortlist of crucial bugs (not even
> "important enhancements") to fix, and start with the release process very
> soon.
>
>  - Concurrently add the critical improvements and other upcoming feature
> patches to a different branch.
>
>  - Once the release has been cleared and the release is out there, we
> rebase the feature branch and continue from there.
>
> It would give us the advantage to get out of the name limbo soon and
> pipeline the legal overhead for the first release. The successive release
> could be very soon after the initial one.
>
> How do you feel about this?
>
> Greetings,
> Stephan
>
Reply | Threaded
Open this post in threaded view
|

Re: First Incubator Relase

Henry Saputra
In reply to this post by Stephan Ewen
+1


On Wed, Jul 16, 2014 at 9:48 AM, Stephan Ewen <[hidden email]> wrote:

> Hi everyone!
>
> We just had a hangout discussion (see previous mails for minutes and
> recording) where we talked about getting the first incubator release of
> Flink out.
>
> Legal is blocked on the trademark issue until we make a release and we
> thought it cannot hurt to get the process started soon, because the first
> release is going to take a while.
>
>
> A suggestion we came up was to:
>
>  - Do a feature-freeze now, collect a shortlist of crucial bugs (not even
> "important enhancements") to fix, and start with the release process very
> soon.
>
>  - Concurrently add the critical improvements and other upcoming feature
> patches to a different branch.
>
>  - Once the release has been cleared and the release is out there, we
> rebase the feature branch and continue from there.
>
> It would give us the advantage to get out of the name limbo soon and
> pipeline the legal overhead for the first release. The successive release
> could be very soon after the initial one.
>
> How do you feel about this?
>
> Greetings,
> Stephan
Reply | Threaded
Open this post in threaded view
|

Re: First Incubator Relase

Fabian Hueske-2
+1


2014-07-16 20:37 GMT+02:00 Henry Saputra <[hidden email]>:

> +1
>
>
> On Wed, Jul 16, 2014 at 9:48 AM, Stephan Ewen <[hidden email]> wrote:
> > Hi everyone!
> >
> > We just had a hangout discussion (see previous mails for minutes and
> > recording) where we talked about getting the first incubator release of
> > Flink out.
> >
> > Legal is blocked on the trademark issue until we make a release and we
> > thought it cannot hurt to get the process started soon, because the first
> > release is going to take a while.
> >
> >
> > A suggestion we came up was to:
> >
> >  - Do a feature-freeze now, collect a shortlist of crucial bugs (not even
> > "important enhancements") to fix, and start with the release process very
> > soon.
> >
> >  - Concurrently add the critical improvements and other upcoming feature
> > patches to a different branch.
> >
> >  - Once the release has been cleared and the release is out there, we
> > rebase the feature branch and continue from there.
> >
> > It would give us the advantage to get out of the name limbo soon and
> > pipeline the legal overhead for the first release. The successive release
> > could be very soon after the initial one.
> >
> > How do you feel about this?
> >
> > Greetings,
> > Stephan
>
Reply | Threaded
Open this post in threaded view
|

Re: First Incubator Relase

Fabian Hueske
+1


2014-07-16 21:59 GMT+02:00 Fabian Hueske <[hidden email]>:

> +1
>
>
> 2014-07-16 20:37 GMT+02:00 Henry Saputra <[hidden email]>:
>
> +1
>>
>>
>> On Wed, Jul 16, 2014 at 9:48 AM, Stephan Ewen <[hidden email]> wrote:
>> > Hi everyone!
>> >
>> > We just had a hangout discussion (see previous mails for minutes and
>> > recording) where we talked about getting the first incubator release of
>> > Flink out.
>> >
>> > Legal is blocked on the trademark issue until we make a release and we
>> > thought it cannot hurt to get the process started soon, because the
>> first
>> > release is going to take a while.
>> >
>> >
>> > A suggestion we came up was to:
>> >
>> >  - Do a feature-freeze now, collect a shortlist of crucial bugs (not
>> even
>> > "important enhancements") to fix, and start with the release process
>> very
>> > soon.
>> >
>> >  - Concurrently add the critical improvements and other upcoming feature
>> > patches to a different branch.
>> >
>> >  - Once the release has been cleared and the release is out there, we
>> > rebase the feature branch and continue from there.
>> >
>> > It would give us the advantage to get out of the name limbo soon and
>> > pipeline the legal overhead for the first release. The successive
>> release
>> > could be very soon after the initial one.
>> >
>> > How do you feel about this?
>> >
>> > Greetings,
>> > Stephan
>>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: First Incubator Relase

Robert Metzger
+1

I also agree with pushing for a 0.6-incubating release asap.
In general, it causes me some headaches when developing on a separate
branch (merging/rebase issues, hard-to-understand development process), but
in this case we should really not let the legal / infra stuff block our
regular development process.
I'm going to start working on the release-related stuff soon (signing keys,
licensing, maven infra) and push out a first release candidate then.
However, I'm planning to go on vacation next week, so I'm not going to work
at full speed. But I'm confident to find enough time to keep the ball
rolling.

On a side note, there was another email-thread opened at the same day as
this one, named "0.6-incubating release" to plan the release. In my
opinion, it would have been better to continue the discussion there.

Robert



On Wed, Jul 16, 2014 at 10:00 PM, Fabian Hueske <[hidden email]> wrote:

> +1
>
>
> 2014-07-16 21:59 GMT+02:00 Fabian Hueske <[hidden email]>:
>
> > +1
> >
> >
> > 2014-07-16 20:37 GMT+02:00 Henry Saputra <[hidden email]>:
> >
> > +1
> >>
> >>
> >> On Wed, Jul 16, 2014 at 9:48 AM, Stephan Ewen <[hidden email]> wrote:
> >> > Hi everyone!
> >> >
> >> > We just had a hangout discussion (see previous mails for minutes and
> >> > recording) where we talked about getting the first incubator release
> of
> >> > Flink out.
> >> >
> >> > Legal is blocked on the trademark issue until we make a release and we
> >> > thought it cannot hurt to get the process started soon, because the
> >> first
> >> > release is going to take a while.
> >> >
> >> >
> >> > A suggestion we came up was to:
> >> >
> >> >  - Do a feature-freeze now, collect a shortlist of crucial bugs (not
> >> even
> >> > "important enhancements") to fix, and start with the release process
> >> very
> >> > soon.
> >> >
> >> >  - Concurrently add the critical improvements and other upcoming
> feature
> >> > patches to a different branch.
> >> >
> >> >  - Once the release has been cleared and the release is out there, we
> >> > rebase the feature branch and continue from there.
> >> >
> >> > It would give us the advantage to get out of the name limbo soon and
> >> > pipeline the legal overhead for the first release. The successive
> >> release
> >> > could be very soon after the initial one.
> >> >
> >> > How do you feel about this?
> >> >
> >> > Greetings,
> >> > Stephan
> >>
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: First Incubator Relase

Stephan Ewen
I have started going through all dependencies, collecting Licenses and
Notices to place into our License and notice file.
Reply | Threaded
Open this post in threaded view
|

Re: First Incubator Relase

Stephan Ewen
I have updated the LICENSE and NOTICE files with notices and licenses from
all immediate subcomponents.

NOTICE and LICENSE are available both in the root of the source repository,
as well as in the root of the binary distribution.

The DISCLAIMER (incubator requirement) is also in place.

Could someone verify the files at
https://github.com/apache/incubator-flink/blob/master/LICENSE
https://github.com/apache/incubator-flink/blob/master/NOTICE
https://github.com/apache/incubator-flink/blob/master/flink-dist/src/main/flink-bin/DISCLAIMER

Greetings,
Stephan





On Mon, Jul 21, 2014 at 12:18 PM, Stephan Ewen <[hidden email]> wrote:

> I have started going through all dependencies, collecting Licenses and
> Notices to place into our License and notice file.
>
Reply | Threaded
Open this post in threaded view
|

Re: First Incubator Relase

Ufuk Celebi

On 21 Jul 2014, at 16:42, Stephan Ewen <[hidden email]> wrote:

> I have updated the LICENSE and NOTICE files with notices and licenses from
> all immediate subcomponents.

Thank you very much for taking care of this!

1. I've looked at all the pom files and the LICENSE and NOTICE files. I noticed the following:

- I couldn't find ASM. It's a dependency of flink-scala.
- I couldn't find ScalaTest (test scope, but it should be bundled with the testjar?)

2. I also remembered that ClosureCleaner in flink-scala is from Spark, but lacks a notice in the file itself. How should we handle it?
Reply | Threaded
Open this post in threaded view
|

Re: First Incubator Relase

Robert Metzger
We finally got access to the Apache Maven repositories (
https://issues.apache.org/jira/browse/INFRA-8026).
I was able to deploy the current version to the SNAPSHOT repository:
https://repository.apache.org/content/repositories/snapshots/org/apache/flink/
I'll now set it up for automated deployment with Travis.


On Tue, Jul 22, 2014 at 10:42 AM, Ufuk Celebi <[hidden email]> wrote:

>
> On 21 Jul 2014, at 16:42, Stephan Ewen <[hidden email]> wrote:
>
> > I have updated the LICENSE and NOTICE files with notices and licenses
> from
> > all immediate subcomponents.
>
> Thank you very much for taking care of this!
>
> 1. I've looked at all the pom files and the LICENSE and NOTICE files. I
> noticed the following:
>
> - I couldn't find ASM. It's a dependency of flink-scala.
> - I couldn't find ScalaTest (test scope, but it should be bundled with the
> testjar?)
>
> 2. I also remembered that ClosureCleaner in flink-scala is from Spark, but
> lacks a notice in the file itself. How should we handle it?
Reply | Threaded
Open this post in threaded view
|

Re: First Incubator Relase

Stephan Ewen
In reply to this post by Ufuk Celebi
Right, I forgot the Scala Project. Concerning the closure cleaner, there is
a notice in the code itself. Is that enough? There are also some small code
portions of hadoop used, mainly in the RPC infrastructure...
Reply | Threaded
Open this post in threaded view
|

Re: First Incubator Relase

Stephan Ewen
In reply to this post by Robert Metzger
Great news on the maven repos :-)
Reply | Threaded
Open this post in threaded view
|

Re: First Incubator Relase

Ufuk Celebi
In reply to this post by Stephan Ewen

On 22 Jul 2014, at 11:33, Stephan Ewen <[hidden email]> wrote:

> Right, I forgot the Scala Project. Concerning the closure cleaner, there is
> a notice in the code itself. Is that enough? There are also some small code
> portions of hadoop used, mainly in the RPC infrastructure...

I've updated the LICENSE file.

But ClosureCleaner [1] does not contain a notice in the code itself.

What do we do about the Hadoop RPC stuff?

[1] https://github.com/apache/incubator-flink/blob/master/flink-scala/src/main/scala/org/apache/flink/api/scala/operators/ClosureCleaner.scala

Reply | Threaded
Open this post in threaded view
|

Re: First Incubator Relase

Stephan Ewen
Okay, the ClosureCleaner has a notice. The Hadoop-based parts of the RPC
have had notices all the way already.

Is anything missing now (formal and legal requirements), before we can
start an official vote to create a first release?

(Note: I am aware that there are two API breaking issues pending, all other
efforts can go into the branch for the followup version.)
Reply | Threaded
Open this post in threaded view
|

Re: First Incubator Relase

Ufuk Celebi

On 24 Jul 2014, at 01:44, Stephan Ewen <[hidden email]> wrote:

> Okay, the ClosureCleaner has a notice. The Hadoop-based parts of the RPC
> have had notices all the way already.
>
> Is anything missing now (formal and legal requirements), before we can
> start an official vote to create a first release?

I think we are ready for take off :-)
Reply | Threaded
Open this post in threaded view
|

Re: First Incubator Relase

Robert Metzger
I have spend some time getting familiar with the keying infrastructure of
Apache. My key is now in the https://people.apache.org/keys/ directory and
we have a "flink" directory in "dist.apache.org":
https://dist.apache.org/repos/dist/release/incubator/flink/
So from the infrastructure point of view, everything should be good to go
for the release.

Whats missing are the breaking API changes to be merged, before we can
start with the vote.

I'll create a "release-0.6" branch now where we are going to add the last
commits for the 0.6-incubating release to.
I will update the version of the "master" once we released 0.6.


On Thu, Jul 24, 2014 at 1:45 AM, Ufuk Celebi <[hidden email]> wrote:

>
> On 24 Jul 2014, at 01:44, Stephan Ewen <[hidden email]> wrote:
>
> > Okay, the ClosureCleaner has a notice. The Hadoop-based parts of the RPC
> > have had notices all the way already.
> >
> > Is anything missing now (formal and legal requirements), before we can
> > start an official vote to create a first release?
>
> I think we are ready for take off :-)
>