Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #36487 > unrolled thread

JDK 1.8.0_131

Back to article view | Back to comp.lang.java.programmer

Contents

  JDK 1.8.0_131 Roedy Green <inquiry@mindprod.com> - 2017-04-18 11:23 -0700
    Re:JDK 1.8.0_131 omegajunior <omegajunior@protonmail.com> - 2017-04-24 08:43 -0400
      Re: JDK 1.8.0_131 Eric Sosman <esosman@comcast-dot-net.invalid> - 2017-04-24 09:07 -0400
        Re: JDK 1.8.0_131 v_borchert@despammed.com (Volker Borchert) - 2017-04-24 18:00 +0000
        Re: JDK 1.8.0_131 omegajunior <omegajunior@protonmail.com> - 2017-04-26 18:16 -0400
      Re: JDK 1.8.0_131 Arne Vajhøj <arne@vajhoej.dk> - 2017-04-24 11:25 -0400
        Re: JDK 1.8.0_131 omegajunior <omegajunior@protonmail.com> - 2017-04-26 18:12 -0400

#36487 — JDK 1.8.0_131

JDK 1.8.0_131 is out

[toc] | [next] | [standalone]

#36512

Roedy Green <inquiry@mindprod.com> Wrote in message:
> JDK 1.8.0_131 is out
> 

Oh, bloody hell, what is it this time? I just got through testing
 all my applications with 1.8.0_121. There must be a faster
 way.
-- 


----Android NewsGroup Reader----
http://usenet.sinaapp.com/

[toc] | [prev] | [next] | [standalone]

#36514

On 4/24/2017 8:43 AM, omegajunior wrote:
> Roedy Green <inquiry@mindprod.com> Wrote in message:
>> JDK 1.8.0_131 is out
>>
> 
> Oh, bloody hell, what is it this time? I just got through testing
>   all my applications with 1.8.0_121. There must be a faster
>   way.

     To answer "What is it this time?" begin by studying the release
notes.  Sometimes the study's answers are less than comprehensive
(release notes can be downright coy when discussing security issues),
but that's where you should start.

     The "faster way" is largely up to you.  Three months and a day
intervened between 121 and 131, and if it truly takes you that long
to test your applications I'd say your test procedures could use some
attention.  If your applications are so voluminous and so intricate
that they can't be re-qualified in the span of a calendar quarter
(the typical time between Java releases, nowadays), you may need to
adopt new strategies.  For example, you might use an every-other-
release policy, giving you six months between test cycles.  Or you
might leave half your apps on 121 while migrating the other half
to 131, intending to migrate the laggards to 144 (or whatever) when
it appears -- a sort of "leapfrog" approach in which each app gets
migrated twice a year instead of four times.  (Important security
fixes might require some alterations to the schedule, such as "out
of cycle" migrations of selected vulnerable apps.)

     There is, alas, no one-size-fits all solution to the problem
of keeping current.  Have you updated the firmware in your WiFi-
enabled toaster oven recently?  ;)

-- 
esosman@comcast-dot-net.invalid
Thirteen hundred sixty-seven days to go.

[toc] | [prev] | [next] | [standalone]

#36525

Eric Sosman wrote:
> On 4/24/2017 8:43 AM, omegajunior wrote:
> > Roedy Green <inquiry@mindprod.com> Wrote in message:
> >> JDK 1.8.0_131 is out
> >>
> > 
> > Oh, bloody hell, what is it this time? I just got through testing
> >   all my applications with 1.8.0_121. There must be a faster
> >   way.
> 
>      To answer "What is it this time?" begin by studying the release
> notes.  Sometimes the study's answers are less than comprehensive
> (release notes can be downright coy when discussing security issues),
> but that's where you should start.

And it seems to be more often than not that the security fixes
only apply to Java-in-the-browser causing sandbox escapes and
do not affect standalone applications at all, so that you might
even be able to completely ignore them unless you have customers
who are paranoid and stubborn at the same time.

-- 

"I'm a doctor, not a mechanic." Dr Leonard McCoy <mccoy@ncc1701.starfleet.fed>
"I'm a mechanic, not a doctor." Volker Borchert  <v_borchert@despammed.com>

[toc] | [prev] | [next] | [standalone]

#36538

Eric Sosman <esosman@comcast-dot-net.invalid> Wrote in message:
> On 4/24/2017 8:43 AM, omegajunior wrote:
>> Roedy Green <inquiry@mindprod.com> Wrote in message:
>>> JDK 1.8.0_131 is out
>>>
>> 
>> Oh, bloody hell, what is it this time? I just got through testing
>>   all my applications with 1.8.0_121. There must be a faster
>>   way.
> 
>      To answer "What is it this time?" begin by studying the release
> notes.  Sometimes the study's answers are less than comprehensive
> (release notes can be downright coy when discussing security issues),
> but that's where you should start.
> 
>      The "faster way" is largely up to you.  Three months and a day
> intervened between 121 and 131, and if it truly takes you that long
> to test your applications I'd say your test procedures could use some
> attention.  If your applications are so voluminous and so intricate
> that they can't be re-qualified in the span of a calendar quarter
> (the typical time between Java releases, nowadays), you may need to
> adopt new strategies.  For example, you might use an every-other-
> release policy, giving you six months between test cycles.  Or you
> might leave half your apps on 121 while migrating the other half
> to 131, intending to migrate the laggards to 144 (or whatever) when
> it appears -- a sort of "leapfrog" approach in which each app gets
> migrated twice a year instead of four times.  (Important security
> fixes might require some alterations to the schedule, such as "out
> of cycle" migrations of selected vulnerable apps.)
> 
>      There is, alas, no one-size-fits all solution to the problem
> of keeping current.  Have you updated the firmware in your WiFi-
> enabled toaster oven recently?  ;)
> 
> -- 
> esosman@comcast-dot-net.invalid
> Thirteen hundred sixty-seven days to go.
> 

Hah, funny. 
  
Yes, I understand the importance of staying up to date. 
  
We're managing dozens of small applications, and constantly build
 new ones. It's becoming quite time-consuming to repeat-test with
 every new java release. 
  
At some point we'll only ever be testing for regressions, and
 won't have time to develop new
solutions. 
  
Well. Maybe it's time to add some developers to our team. 
-- 


----Android NewsGroup Reader----
http://usenet.sinaapp.com/

[toc] | [prev] | [next] | [standalone]

#36520

On 4/24/2017 8:43 AM, omegajunior wrote:
> Roedy Green <inquiry@mindprod.com> Wrote in message:
>> JDK 1.8.0_131 is out
>
> Oh, bloody hell, what is it this time?

Some minor stuff + 2 security fixes.

For the latter see:

http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixJAVA

Both seems to be applet / JWS related.

>                                 I just got through testing
>  all my applications with 1.8.0_121. There must be a faster
>  way.

Maybe you don't need this update.

But in general you should keep up with new versions. And
the only practical way is to automate testing as much as
possible.

Arne

[toc] | [prev] | [next] | [standalone]

#36537

Arne Vajhøj <arne@vajhoej.dk> Wrote in message:
> On 4/24/2017 8:43 AM, omegajunior wrote:
>> Roedy Green <inquiry@mindprod.com> Wrote in message:
>>> JDK 1.8.0_131 is out
>>
>> Oh, bloody hell, what is it this time?
> 
> Some minor stuff + 2 security fixes.
> 
> For the latter see:
> 
> http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixJAVA
> 
> Both seems to be applet / JWS related.
> 
>>                                 I just got through testing
>>  all my applications with 1.8.0_121. There must be a faster
>>  way.
> 
> Maybe you don't need this update.
> 
> But in general you should keep up with new versions. And
> the only practical way is to automate testing as much as
> possible.
> 
> Arne
> 
> 
> 

I agree. We're managing dozens of small applications, most of
 which eaily will pass a test with this new java update.
 
  
I'll have to reconsider what and how we test. It's the integration
 tests that consume most time, and all of our applications
 integrate data. 
-- 


----Android NewsGroup Reader----
http://usenet.sinaapp.com/

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.java.programmer

csiph-web