On Wed, Oct 18, 2017 at 10:59 AM, Eugene Kirpichov
wrote:
> So far we seem to have unanimous consensus in favor of dropping Java7, and
> we seem to also be converging on declaring that this doesn't require
> increasing major version - but the discussion has been going on
So far we seem to have unanimous consensus in favor of dropping Java7, and
we seem to also be converging on declaring that this doesn't require
increasing major version - but the discussion has been going on for only a
couple of days and we might not have reached some users.
Robert - I think it's
On Oct 18, 2017 3:25 AM, "Jean-Baptiste Onofré" wrote:
What happens for the users using spark 1.5 that run with Java 7 only ?
One of the goals of this thread is to tease out such users if any.
To reach a wider audience, maybe the next set of release notes could
mention that
+1
On 18 October 2017 at 16:00, Ismaël Mejía wrote:
> Small correction EOL of Java 8 is Sep. 2018 not Mar. 2018.
> http://www.oracle.com/technetwork/java/eol-135779.html
>
> JB the goal of this thread is to get an opinion from the users of all
> the runners on their
Small correction EOL of Java 8 is Sep. 2018 not Mar. 2018.
http://www.oracle.com/technetwork/java/eol-135779.html
JB the goal of this thread is to get an opinion from the users of all
the runners on their opinions/constraints, but we have to reach some
consensus and deal with the tradeoffs of
+1
-
Srinivas
- Typed on tiny keys. pls ignore typos.{mobile app}
On 17-Oct-2017 9:47 PM, "Ismaël Mejía" wrote:
> We have discussed recently in the developer mailing list about the
> idea of removing support for Java 7 on Beam. There are multiple
> reasons for this:
>
> -
What happens for the users using spark 1.5 that run with Java 7 only ?
On Oct 18, 2017, 12:06, at 12:06, "Ismaël Mejía" wrote:
>+1
>
>I forgot to vote yesterday, I don't really think this is a change
>worth requiring a major version of Beam. Just clear information in the
+1
I forgot to vote yesterday, I don't really think this is a change
worth requiring a major version of Beam. Just clear information in the
site/release notes should make it. Also I am afraid that if we wait
until we have enough changes to switch Beam to a new major version the
switch to Java 8
+1
On 18 October 2017 at 05:16, Griselda Cuevas wrote:
> +1
>
> On 17 October 2017 at 16:36, Robert Bradshaw wrote:
>
>> +1 to removing Java 7 support, pending no major user outcry to the
>> contrary.
>>
>> In terms of versioning, I fall into the camp that
+1
On 17 October 2017 at 16:36, Robert Bradshaw wrote:
> +1 to removing Java 7 support, pending no major user outcry to the
> contrary.
>
> In terms of versioning, I fall into the camp that this isn't
> sufficiently incompatible to warrant a major version increase.
>
+1 to removing Java 7 support.
In terms of release 3.0, we can handle this two ways:
- Wait until enough other potentially incompatible changes accumulate, do
all of them, and call it a "3.0" release, so that 3.0 will truly differ in
a lot of incompatible and hopefully nice ways from 2.x. This
+1
On Tue, Oct 17, 2017 at 5:21 PM Raghu Angadi wrote:
> +1.
>
> On Tue, Oct 17, 2017 at 2:11 PM, David McNeill
> wrote:
>
>> The final version of Beam that supports Java 7 should be clearly stated
>> in the docs, so those stuck on old production
+1.
On Tue, Oct 17, 2017 at 2:11 PM, David McNeill wrote:
> The final version of Beam that supports Java 7 should be clearly stated in
> the docs, so those stuck on old production infrastructure for other java
> app dependencies know where to stop upgrading.
>
> David
The final version of Beam that supports Java 7 should be clearly stated in
the docs, so those stuck on old production infrastructure for other java
app dependencies know where to stop upgrading.
David McNeill
021 721 015
On 18 October 2017 at 05:16, Ismaël Mejía wrote:
>
+1
(snip):
So, please vote:
+1 Yes, go ahead and move Beam support to Java 8.
0 Do whatever you want. I don’t have a preference.
-1 Please keep Java 7 compatibility (if possible add your argument to
keep supporting for Java 7).
+1
On Tue, Oct 17, 2017 at 8:22 PM, Thomas Groh wrote:
> I'm pretty strongly in favor of phasing out Java7 support, especially
> given that it was EoL'd more than two years ago. However, I'm not sure how
> this interacts with the repository's backwards-compatibility guarantees
+1
On Tue, Oct 17, 2017 at 6:52 PM, Henning Rohde wrote:
> +1
>
> On Tue, Oct 17, 2017 at 9:47 AM, Jean-Baptiste Onofré
> wrote:
>
>> However, it's good to target this for Beam 3.0.0 as it can have an impact
>> especially for runners.
>>
>> Regards
>> JB
+1
On Tue, Oct 17, 2017 at 9:38 AM Steve Anderson wrote:
> +1
>
> Sent from my iPhone
>
> On Oct 17, 2017, at 09:31, Aleksandr wrote:
>
> +1
>
> 17. okt 2017 7:17 PM kirjutas kuupäeval "Ismaël Mejía" >:
>
> We have discussed
+1
17. okt 2017 7:17 PM kirjutas kuupäeval "Ismaël Mejía" :
We have discussed recently in the developer mailing list about the
idea of removing support for Java 7 on Beam. There are multiple
reasons for this:
- Java 7 has not received public updates for almost two years and
19 matches
Mail list logo