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


Groups > comp.lang.java.programmer > #33501

Re: new Java 1.8.0_72

From Jan Burse <janburse@fastmail.fm>
Newsgroups comp.lang.java.programmer
Subject Re: new Java 1.8.0_72
Date 2016-01-21 16:54 +0100
Organization albasani.net
Message-ID <n7qv04$e4p$1@news.albasani.net> (permalink)
References (1 earlier) <n7qoeh$183$1@news.albasani.net> <af716f67-530c-401a-8b3e-e37c7a68da2f@googlegroups.com> <n7qsp6$qfb$1@gioia.aioe.org> <5e41f67c-f936-44d3-9491-8764d182252a@googlegroups.com> <n7qtki$t99$1@gioia.aioe.org>

Show all headers | View raw


Hi,

The "should only" sounds a little bit frightening to me:

"Java SE Patch Set Updates (PSU) contain all of fixes in the 
corresponding CPU, as well as additional non-critical fixes. Java PSU 
releases should only be used if you are being impacted by one of the 
additional bugs fixed in that version. The release notes call out the 
additional fixes available in Java SE PSU releases."

http://www.oracle.com/technetwork/java/javase/cpu-psu-explained-2331472.html

Anyway, I have started listening to comp.java.openjdk.hotspot.devel
recently. But this stream of posts is very difficult to comprehend,
but also interesting to see how development proceeds.

I guess anyway, should start with JDK 9 soon.

Bye

Arne Vajhøj schrieb:
> On 1/21/2016 10:25 AM, Eric Douglas wrote:
>> On Thursday, January 21, 2016 at 10:17:36 AM UTC-5, Arne Vajhøj
>>> It is somewhat explained in the release notes.
>>>
>>> And also in more detail here:
>>>
>>> http://www.oracle.com/technetwork/java/javase/cpu-psu-explained-2331472.html
>>>
>>>
>>
>> This sounds too complicated.  They call the 'current' version the CPU
>> and the +1 version the PSU.  They recommend using the CPU but say to
>> test the PSU because everything in the PSU will be in the next CPU.
>> I'd rather not run 2 versions, so unless they really expect the PSU
>> to break something they're going to fix in the next CPU or I need to
>> change before the next CPU it seems I might as well install the PSU.
>>
>> It's not like I'm running the latest version in a production
>> environment anyhow.  Unless there's a note saying critical fix
>> install now or you're at high security risk, I just put the latest in
>> my development environment asap and update production some weeks
>> after.
>
> I am PSU inclined as well.
>
> CPU is for those that:
> - need to put security fixes in production ASAP
> - are afraid that bugs in the PSU may impact production stability
>
> Arne
>
>
>

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

new Java 1.8.0_72 Roedy Green <see_website@mindprod.com.invalid> - 2016-01-20 08:15 -0800
  Re: new Java 1.8.0_72 Arne Vajhøj <arne@vajhoej.dk> - 2016-01-20 22:20 -0500
    Re: new Java 1.8.0_72 Roedy Green <see_website@mindprod.com.invalid> - 2016-01-20 21:55 -0800
  Re: new Java 1.8.0_72 Jan Burse <janburse@fastmail.fm> - 2016-01-21 15:02 +0100
    Re: new Java 1.8.0_72 Arne Vajhøj <arne@vajhoej.dk> - 2016-01-21 09:33 -0500
    Re: new Java 1.8.0_72 Eric Douglas <e.d.programmer@gmail.com> - 2016-01-21 06:57 -0800
      Re: new Java 1.8.0_72 Eric Sosman <esosman@comcast-dot-net.invalid> - 2016-01-21 10:05 -0500
      Re: new Java 1.8.0_72 Arne Vajhøj <arne@vajhoej.dk> - 2016-01-21 10:16 -0500
        Re: new Java 1.8.0_72 Eric Douglas <e.d.programmer@gmail.com> - 2016-01-21 07:25 -0800
          Re: new Java 1.8.0_72 Arne Vajhøj <arne@vajhoej.dk> - 2016-01-21 10:31 -0500
            Re: new Java 1.8.0_72 Jan Burse <janburse@fastmail.fm> - 2016-01-21 16:54 +0100
              Re: new Java 1.8.0_72 Arne Vajhøj <arne@vajhoej.dk> - 2016-01-21 14:36 -0500

csiph-web