Hi All,
In reference to a recent mail by Ufuk [1] and because it has been a while since
the last Flink release we should start thinking about a Flink 1.8 release.
We’re actually a bit behind the cadence but I think we still shouldn’t rush
things. I’m hereby proposing myself as release manager f
+1 for doing a 1.8 release soon.
Some of the Table API refactoring work is blocked on a release (assuming we
want one release to deprecate some functions before dropping them.
On Tue, Feb 12, 2019 at 11:03 AM Aljoscha Krettek
wrote:
> Hi All,
>
> In reference to a recent mail by Ufuk [1] and be
+1 for Feb 22. Thanks for being the release manager.
– Ufuk
On Tue, Feb 12, 2019 at 7:00 PM Stephan Ewen wrote:
>
> +1 for doing a 1.8 release soon.
>
> Some of the Table API refactoring work is blocked on a release (assuming we
> want one release to deprecate some functions before dropping them
+1 for the 1.8 release. Thanks for volunteering as our release manager
Aljoscha.
Cheers,
Till
On Wed, Feb 13, 2019 at 9:01 AM Ufuk Celebi wrote:
> +1 for Feb 22. Thanks for being the release manager.
>
> – Ufuk
>
> On Tue, Feb 12, 2019 at 7:00 PM Stephan Ewen wrote:
> >
> > +1 for doing a 1.8
Subject:Re: [DISCUSS] Releasing Flink 1.8 / Feature Freeze
+1 for Feb 22. Thanks for being the release manager.
– Ufuk
On Tue, Feb 12, 2019 at 7:00 PM Stephan Ewen wrote:
>
> +1 for doing a 1.8 release soon.
>
> Some of the Table API refactoring work is blocked on a release (assuming w
Thanks for bring up the discuss of 1.8 release Aljoscha !
+1 for feature freeze for 1.8 release soon.
As Stephan mentioned above, Table API refactoring work is blocked on a
release.
The expects changes of deprecated(in 1.8) APIs (Such as:
ExternalCatalogTable#builder(), new Table(..) ) in the Tab
Thanks for planning on the 1.8 release. +1 for cutting the release branch
soon.
As Stephan and Jincheng said, the refactoring of Table API may block the
release. Fortunately, some issues have already been merged into the master,
for example, deprecate methods in TableEnvironment and Table. And som
I'm not involved enough with the development to say whether end of this
week is a realistic deadline.
But I see that it makes sense to release 1.8 soon, if it is blocking the
Table API refactoring.
There are 5 blockers assigned to the 1.8.0 release:
https://issues.apache.org/jira/issues/?jql=proje
Hi Robert,
Regarding FLINK-10776 - Update migration tests for Flink 1.7:
There's still one last test class that needs to be migrated (progress
reflected in the list of subtasks of FLINK-10776), and we definitely should
still fix that before releasing 1.8.0 to ensure backwards compatibility of
save
Hey,
are we doing a feature freeze today?
On Mon, Feb 18, 2019 at 9:52 AM Tzu-Li (Gordon) Tai
wrote:
> Hi Robert,
>
> Regarding FLINK-10776 - Update migration tests for Flink 1.7:
> There's still one last test class that needs to be migrated (progress
> reflected in the list of subtasks of FLINK
10 matches
Mail list logo
