You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aurora.apache.org by Bill Farner <wf...@apache.org> on 2015/01/22 20:50:30 UTC
When (if ever) should we require JDK 8?
Hi folks,
JDK 8 was officially released in March 2014, and brought a bunch of new
features to the runtime and compiler. A side-effect of using java 8
language features is that it requires a >= 1.8 runtime, This means users
currently running the scheduler with java 1.7 would need to upgrade their
JRE. We have a ticket [1] to track adopting JDK 8 on our end.
Does anyone have an opinion on which release we should aim to include this
change in, if at all?
[1] https://issues.apache.org/jira/browse/AURORA-274
-=Bill
Re: When (if ever) should we require JDK 8?
Posted by Maxim Khutornenko <ma...@apache.org>.
I am big +1 on the migration but I am afraid jumping into it too soon
may lock out everyone from upgrading their Aurora cluster until they
have 1.8 infra support.
The 0.9.0 sounds about right unless there is a pushback from our customers.
On Thu, Jan 22, 2015 at 12:04 PM, Kevin Sweeney <ke...@apache.org> wrote:
> How about 0.9, with a deprecation warning at 0.8
>
> On Thu, Jan 22, 2015 at 12:02 PM, Bill Farner <wf...@apache.org> wrote:
>
>> Kevin - do you care to propose a concrete release number?
>>
>> -=Bill
>>
>> On Thu, Jan 22, 2015 at 12:00 PM, Kevin Sweeney <ke...@apache.org>
>> wrote:
>>
>> > Adopting Java8 syntax would get us significant gains in productivity and
>> > code readability.
>> >
>> > Using JRE8 in production should get us some significant performance
>> gains,
>> > though how significant would require performance benchmarks.
>> >
>> > IMO our target platform is 3-5 servers per Mesos cluster and we shouldn't
>> > consider it an operational burden to install the currently-supported
>> > version of the JRE.
>> >
>> > So I'm +1 to adopting JDK8, and soon.
>> >
>> > On Thu, Jan 22, 2015 at 11:50 AM, Bill Farner <wf...@apache.org>
>> wrote:
>> >
>> > > Hi folks,
>> > >
>> > > JDK 8 was officially released in March 2014, and brought a bunch of new
>> > > features to the runtime and compiler. A side-effect of using java 8
>> > > language features is that it requires a >= 1.8 runtime, This means
>> users
>> > > currently running the scheduler with java 1.7 would need to upgrade
>> their
>> > > JRE. We have a ticket [1] to track adopting JDK 8 on our end.
>> > >
>> > > Does anyone have an opinion on which release we should aim to include
>> > this
>> > > change in, if at all?
>> > >
>> > > [1] https://issues.apache.org/jira/browse/AURORA-274
>> > >
>> > >
>> > > -=Bill
>> > >
>> >
>>
Re: When (if ever) should we require JDK 8?
Posted by Zameer Manji <zm...@apache.org>.
+1 to Kevin's proposed cycle.
I would like us to use JDK 8 as soon as possible. Kevin's proposal will
allow us to get there with the minimal amount of breakage.
On Thu, Jan 22, 2015 at 12:04 PM, Kevin Sweeney <ke...@apache.org> wrote:
> How about 0.9, with a deprecation warning at 0.8
>
> On Thu, Jan 22, 2015 at 12:02 PM, Bill Farner <wf...@apache.org> wrote:
>
> > Kevin - do you care to propose a concrete release number?
> >
> > -=Bill
> >
> > On Thu, Jan 22, 2015 at 12:00 PM, Kevin Sweeney <ke...@apache.org>
> > wrote:
> >
> > > Adopting Java8 syntax would get us significant gains in productivity
> and
> > > code readability.
> > >
> > > Using JRE8 in production should get us some significant performance
> > gains,
> > > though how significant would require performance benchmarks.
> > >
> > > IMO our target platform is 3-5 servers per Mesos cluster and we
> shouldn't
> > > consider it an operational burden to install the currently-supported
> > > version of the JRE.
> > >
> > > So I'm +1 to adopting JDK8, and soon.
> > >
> > > On Thu, Jan 22, 2015 at 11:50 AM, Bill Farner <wf...@apache.org>
> > wrote:
> > >
> > > > Hi folks,
> > > >
> > > > JDK 8 was officially released in March 2014, and brought a bunch of
> new
> > > > features to the runtime and compiler. A side-effect of using java 8
> > > > language features is that it requires a >= 1.8 runtime, This means
> > users
> > > > currently running the scheduler with java 1.7 would need to upgrade
> > their
> > > > JRE. We have a ticket [1] to track adopting JDK 8 on our end.
> > > >
> > > > Does anyone have an opinion on which release we should aim to include
> > > this
> > > > change in, if at all?
> > > >
> > > > [1] https://issues.apache.org/jira/browse/AURORA-274
> > > >
> > > >
> > > > -=Bill
> > > >
> > >
> >
>
--
Zameer Manji
Re: When (if ever) should we require JDK 8?
Posted by Kevin Sweeney <ke...@apache.org>.
How about 0.9, with a deprecation warning at 0.8
On Thu, Jan 22, 2015 at 12:02 PM, Bill Farner <wf...@apache.org> wrote:
> Kevin - do you care to propose a concrete release number?
>
> -=Bill
>
> On Thu, Jan 22, 2015 at 12:00 PM, Kevin Sweeney <ke...@apache.org>
> wrote:
>
> > Adopting Java8 syntax would get us significant gains in productivity and
> > code readability.
> >
> > Using JRE8 in production should get us some significant performance
> gains,
> > though how significant would require performance benchmarks.
> >
> > IMO our target platform is 3-5 servers per Mesos cluster and we shouldn't
> > consider it an operational burden to install the currently-supported
> > version of the JRE.
> >
> > So I'm +1 to adopting JDK8, and soon.
> >
> > On Thu, Jan 22, 2015 at 11:50 AM, Bill Farner <wf...@apache.org>
> wrote:
> >
> > > Hi folks,
> > >
> > > JDK 8 was officially released in March 2014, and brought a bunch of new
> > > features to the runtime and compiler. A side-effect of using java 8
> > > language features is that it requires a >= 1.8 runtime, This means
> users
> > > currently running the scheduler with java 1.7 would need to upgrade
> their
> > > JRE. We have a ticket [1] to track adopting JDK 8 on our end.
> > >
> > > Does anyone have an opinion on which release we should aim to include
> > this
> > > change in, if at all?
> > >
> > > [1] https://issues.apache.org/jira/browse/AURORA-274
> > >
> > >
> > > -=Bill
> > >
> >
>
Re: When (if ever) should we require JDK 8?
Posted by Bill Farner <wf...@apache.org>.
Kevin - do you care to propose a concrete release number?
-=Bill
On Thu, Jan 22, 2015 at 12:00 PM, Kevin Sweeney <ke...@apache.org> wrote:
> Adopting Java8 syntax would get us significant gains in productivity and
> code readability.
>
> Using JRE8 in production should get us some significant performance gains,
> though how significant would require performance benchmarks.
>
> IMO our target platform is 3-5 servers per Mesos cluster and we shouldn't
> consider it an operational burden to install the currently-supported
> version of the JRE.
>
> So I'm +1 to adopting JDK8, and soon.
>
> On Thu, Jan 22, 2015 at 11:50 AM, Bill Farner <wf...@apache.org> wrote:
>
> > Hi folks,
> >
> > JDK 8 was officially released in March 2014, and brought a bunch of new
> > features to the runtime and compiler. A side-effect of using java 8
> > language features is that it requires a >= 1.8 runtime, This means users
> > currently running the scheduler with java 1.7 would need to upgrade their
> > JRE. We have a ticket [1] to track adopting JDK 8 on our end.
> >
> > Does anyone have an opinion on which release we should aim to include
> this
> > change in, if at all?
> >
> > [1] https://issues.apache.org/jira/browse/AURORA-274
> >
> >
> > -=Bill
> >
>
Re: When (if ever) should we require JDK 8?
Posted by Kevin Sweeney <ke...@apache.org>.
Adopting Java8 syntax would get us significant gains in productivity and
code readability.
Using JRE8 in production should get us some significant performance gains,
though how significant would require performance benchmarks.
IMO our target platform is 3-5 servers per Mesos cluster and we shouldn't
consider it an operational burden to install the currently-supported
version of the JRE.
So I'm +1 to adopting JDK8, and soon.
On Thu, Jan 22, 2015 at 11:50 AM, Bill Farner <wf...@apache.org> wrote:
> Hi folks,
>
> JDK 8 was officially released in March 2014, and brought a bunch of new
> features to the runtime and compiler. A side-effect of using java 8
> language features is that it requires a >= 1.8 runtime, This means users
> currently running the scheduler with java 1.7 would need to upgrade their
> JRE. We have a ticket [1] to track adopting JDK 8 on our end.
>
> Does anyone have an opinion on which release we should aim to include this
> change in, if at all?
>
> [1] https://issues.apache.org/jira/browse/AURORA-274
>
>
> -=Bill
>