Yes, but I think we would pretty much have to do that. I don't think we can
stop doing 2.11 releases.
> On 8. Oct 2018, at 15:37, Chesnay Schepler wrote:
>
> The infrastructure would only be required if we opt for releasing 2.11 and
> 2.12 builds simultaneously, correct?
>
> On 08.10.2018 15:
The infrastructure would only be required if we opt for releasing 2.11
and 2.12 builds simultaneously, correct?
On 08.10.2018 15:04, Aljoscha Krettek wrote:
Breaking the API (or not breaking it but requiring explicit types when using
Scala 2.12) and the Maven infrastructure to actually build a
Breaking the API (or not breaking it but requiring explicit types when using
Scala 2.12) and the Maven infrastructure to actually build a 2.12 release.
> On 8. Oct 2018, at 13:00, Chesnay Schepler wrote:
>
> And the remaining parts would only be about breaking the API?
>
> On 08.10.2018 12:24,
And the remaining parts would only be about breaking the API?
On 08.10.2018 12:24, Aljoscha Krettek wrote:
I have an open PR that does everything we can do for preparing the code base
for Scala 2.12 without breaking the API:
https://github.com/apache/flink/pull/6784
On 8. Oct 2018, at 09:56,
I have an open PR that does everything we can do for preparing the code base
for Scala 2.12 without breaking the API:
https://github.com/apache/flink/pull/6784
> On 8. Oct 2018, at 09:56, Chesnay Schepler wrote:
>
> I'd rather not maintain 2 master branches. Beyond the maintenance overhead I'm
I'd rather not maintain 2 master branches. Beyond the maintenance
overhead I'm
wondering about the benefit, as the API break still has to happen at
some point.
@Aljoscha how much work for supporting scala 2.12 can be merged without
breaking the API?
If this is the only blocker I suggest to ma
Thanks Aljoscha for starting this discussion. The described problem brings
us indeed a bit into a pickle. Even with option 1) I think it is somewhat
API breaking because everyone who used lambdas without types needs to add
them now. Consequently, I only see two real options out of the ones you've
p