But there is no easy way to identify that broken code a priori. They do know that the compiler fixes could change behavior of certain peoples' (broken) code. They can't know for sure that the BigInteger performance upgrades won't break your code. On the topic of why Oracle can't give you clear advice. In practice, software / devops engineers often have to balance competing risks and schedules without the resources to do a proper job. Note also that is an idealized decision making process. paying for Oracle to spin you custom security patches that might allow you to put off installing the enhancements. If you have a support contract, there may be other options e.g. Note that this is the picture if you don't have a support contract. If neither of the above applies, it doesn't matter which you chose. Otherwise, if you need the listed enhancements of the PSU, choose the PSU over the CPU. You cannot predict whether that will cause problems. If you skip the PSU in this upgrade cycle, you are putting off finding / fixing any unexpected breakages until the next (mandatory) CPU. The reason is that the next CPU release will most likely include the enhancements in this PSU. You should then plan to upgrade to the PSU soon. A CPU has the lesser risk of the upgrade breaking your application. If you have critical Java applications 1, initially choose the CPU over the PSU. based on the Oracle CPU and PSU Releases Explained page (quoted above). In general, here is how I think one should chose between a CPU or a PSU. You can update to 8u152 if you actually need some bugfix there. So it is recommended to update as fast as you can to the 8u151 and test/adjust you code for comparability with 8u152. And there is high probability that you are going to get most of them anyway in the next CPU release. So there are 238 bug fixes in the PSU (8u152) (not only BigInteger performance improvements). 8u151-relnotes or Wiki: Security fixes, 2 notes, 1Ĭertificate revocation, 1 new feature, 6 changes and 24 bug.8u152-relnotes or Wiki: Security fixes, 1 new feature,.To find full list of public bug fixes you need to open Bug Fixes page at the bottom of the release notes. What's the difference between odd and even Java updates? Non-critical fixes in addition to the critical fixes contained in the PSU releases provide organizations and developers with access to The release notes call out theĪdditional fixes available in Java SE PSU releases. Releases should only be used if you are being impacted by one of theĪdditional bugs fixed in that version. Java SE Patch Set Updates (PSU) contain all of fixes in theĬorresponding CPU, as well as additional non-critical fixes. More on Java SE version numbering schemes here). Java SE CPU releases are odd numbered versions (i.e. Users upgrade to the latest CPU releases as they are made available. Oracle strongly recommends that all Java SE What is the difference between a Java CPU and PSU release? Java SEĬritical Patch Updates (CPU) contain fixes to security vulnerabilitiesĪnd critical bug fixes. PSU in their environment in anticipation of these fixes being included For this reason, organizations should test the current The subsequent CPU release will contain all of the fixes from theĬurrent PSU. Impacted by one of the additional bugs fixed in that version as noted Users should only use the corresponding PSU release if they are being Strongly recommends that all Java SE users upgrade to the latest CPU Which Java version should I choose: the CPU or the PSU? Oracle Same time as a corresponding Patch Set Update (PSU) for Java SE 7. October 2014, Oracle will release a Critical Patch Update (CPU) at the Starting with the release of Java SE 7 Update 71 (Java SE 7u71) in 8u152 (tag jdk8u152-b16) is a Patch Set Update (PSU) Releaseįrom official Oracle CPU and PSU Releases Explained.8u151 (tag jdk8u151-b12) is a Critical Patch Update (CPU) Release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |