Mailing-List: contact dev-help@flink.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.incubator.apache.org
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Planning Flink release 0.7-incubating
From: Ufuk Celebi <uce@apache.org>
In-Reply-To: 
 <CAGr9p8AC4LVYXOdPPQFAvkpEN5Fizb=XogRFE7Yi2DcxUvRc2A@mail.gmail.com>
Date: Wed, 24 Sep 2014 18:53:57 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D01A691-C554-4D09-BA7B-8AAB93A5216D@apache.org>
References: 
 <CAGr9p8CnEa9fnB8XUBQD-9Z04Oq32OUG6U204GBPyZ_0U3T92g@mail.gmail.com>
 <CANC1h_ukQiET3vdZ6f1WsbV4Zfjnjm0T3Nab9qfw-Z+EMha2pw@mail.gmail.com>
 <CAAdrtT0G59XZtRPaauZ=u_4Q1xZ3N6Hq8oEGOoSsbRfbmzA_AA@mail.gmail.com>
 <CAGr9p8CakGTWmhg8VKJpMncNWa6_kFQwRgyU4HGhw+LBxLF5KQ@mail.gmail.com>
 <CAKiyyaF3Bfu0Yn7NvOpksBcwXvEZGdRt-gw+uSGcVSNjqA0G4Q@mail.gmail.com>
 <CAGr9p8CKeAUXGPtrw=USD3eFvt77SfVJom6ccrZQiBW+NH5cWA@mail.gmail.com>
 <CAC27z=NBxM9ZLVUtrcueF-uOHMDWwLppq5B8ki-LBxvh0egaSA@mail.gmail.com>
 <CAKADb_OTxhf+LY3LvL0pcSAvWT-vH97fVfAyeYC+762x73rX_Q@mail.gmail.com>
 <CAGWx-_s7H=MTTo-NyDyZ7Op1odchvcAiF0bVYAudJeeaGSj-5A@mail.gmail.com>
 <CAAdrtT3Y1OBBoNVSBucRVMcZDT9kfZOHXd2ezJ1xH6PCStZGVw@mail.gmail.com>
 <CANC1h_szA2Jmkq=QnEv_whq195qmMFpyk6=qRYyRMKaLo38M6Q@mail.gmail.com>
 <CA+faj9x4KMjBs+_p2rLMPaz=pemjy27uuiLHrzrv1EKnfSbF3w@mail.gmail.com>
 <CAGWx-_v_5rs6_5HWUDFOAkF49sp=-XdHA0ZnY1syZKsgTALNyA@mail.gmail.com>
 <CAGr9p8AC4LVYXOdPPQFAvkpEN5Fizb=XogRFE7Yi2DcxUvRc2A@mail.gmail.com>
To: dev@flink.incubator.apache.org


On 24 Sep 2014, at 18:37, Robert Metzger <rmetzger@apache.org> wrote:

> Hey guys,
>=20
> exactly 3 weeks ago, we discussed to do a feature freeze for the
> 0.7-incubating release today.
>=20
> =46rom our initial feature list:
> - *Flink Streaming* "Beta Preview". I would suggest to ship the =
streaming,
> but clearly mark it as a preview in the documentation.
> -* Java API Pojo improvements*: Code generation, key selection using a
> string-expression: https://issues.apache.org/jira/browse/FLINK-1032
>  - *Reworked Scala API*. Bring the Scala API in sync with the latest
> developments in the Java API:
> https://issues.apache.org/jira/browse/FLINK-641
>  -* Akka-based RPC service*:
> https://issues.apache.org/jira/browse/FLINK-1019
>  - *Kryo-based serialization*. This feature has been requested by many
> users. Mostly because they wanted to use Collections inside POJOs:
> https://issues.apache.org/jira/browse/FLINK-610
> - Rework JobManager internals to support incremental program rollout &
> execution
> - First parts of dynamic memory assignments
>=20
> The following features are in the master, as of today:
> - *Flink Streaming*
> - *Reworked Scala API*
> -* New Scheduler*
>=20
> We certainly need some days to test everything until we can start the =
vote.
> Based on our experience with the last major release, I would really =
like to
> do the testing and bugfixing BEFORE the first release candidate. For =
the
> 0.6-incubating release, we had 6  candidates)
>=20
> How do you guys feel about this? Should we wait a few more days for =
the
> release so that a few more features make it into the release?
>=20
> I'm undecided on this. On the one hand, its really nice to release on =
a
> regular schedule, but it also eats up some time and causes overhead
> (different branches etc.).
> I would really like to have the Java API Pojo improvements in the =
release.
> I think I can finish it until end of this week.
>=20
> Opinions?

I agree that the finished features (especially the Scala API) are nice =
for a new release, but still I would like to wait a few more days.

Some of the missing features are on the brink of being finished (e.g. =
the Pojo improvements). I wouldn't want to invest a week in bug fixing =
and doing the release vote, when the new features are likely to be =
finished just a few days afterwards. And the upcoming features will =
definitely be worth a release, so users can work with them. ;)=