Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Eric Sosman <esosman@comcast-dot-net.invalid>
Newsgroups: comp.lang.java.programmer
Subject: Re: JDK 1.8.0_131
Date: Mon, 24 Apr 2017 09:07:54 -0400
Organization: A noiseless patient Spider
Lines: 36
Message-ID: <odkt5d$og$1@dont-email.me>
References: <pcmcfc1ath4l6siqlf87ocn35hvpm11t4g@4ax.com> <odkrt7$1aub$1@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 24 Apr 2017 13:04:45 -0000 (UTC)
Injection-Info: mx02.eternal-september.org; posting-host="794eff07d11dde1d0a66b78b25ef162e"; logging-data="784"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19Sox8uXL6JOe0WtbL1KpER"
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
In-Reply-To: <odkrt7$1aub$1@gioia.aioe.org>
Content-Language: en-US
Cancel-Lock: sha1:jD6qGDNw67IDG9yJGxUqUu3h83o=
Xref: csiph.com comp.lang.java.programmer: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.