Path: csiph.com!aioe.org!.POSTED!not-for-mail From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= Newsgroups: comp.lang.java.programmer Subject: Re: new JDK 1.8.0_112 Date: Wed, 19 Oct 2016 21:26:07 -0400 Organization: Aioe.org NNTP Server Lines: 24 Message-ID: References: <801e31b0-8a86-4276-952c-45c44a0d5d81@googlegroups.com> NNTP-Posting-Host: PBuS014lhzVyHjLbXmo/ZQ.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:35835 On 10/19/2016 8:03 AM, Eric Douglas wrote: > On Tuesday, October 18, 2016 at 6:24:23 PM UTC-4, Roedy Green wrote: >> JDK 1.8.0_111 and 1.8.0_112 are out. > > 111 and 112? Which one works? Last update there was a 101 and 102 > and we had problems with 102. So I guess we stick with 111, even > though when we fixed the rest of the machines on our network by > removing 102 and installing 101 I just put 122 on my machine which > seems to be working fine. So, 111, or early release is at least up to > 122... I think this topic has come up so many times recently. 111 = 102 + security fixes 112 = 102 + security fixes + other fixes So I think the logical upgrade strategy is: 101 or 102 works and want to minimize risk => pick 111 want latest and greatest => pick 112 101 works, 102 does not work and bug not fixed in 111/112 => stay at 101 Arne