To Avoid Confusion: Oracle's Confusing New Java Numbering Scheme
twofishy writes "'To avoid the confusion caused by renumbering releases,' Oracle has announced that it is adopting a new numbering scheme for JDK 5.0, JDK 6 and JDK 7. 'The next Limited Update for JDK 7 will be numbered 7u40, and the next 3 CPUs after that will be numbered 7u45, 7u51, and 7u55." The vendor notes that a more elegant solution would require the changing of the version numbering scheme to accommodate different kinds of changes (for example by using 7u44-2 ). However this cannot be implemented outside of a major release, since doing so might break existing code that parses version strings (possibly including the Java auto-update system)"
Here's Oracle's announcement.
An absurd TLA overloading.
Mensa can use this as a 'What is the next number in the sequence' for their IQ test.
Every time they try to standardize version numbers, they make it more confusing. 11G database release 1 was 11.0, but release 2 is 11.2. Where was 11.1? App server 9i was actually an 8.0 base. Most of the time I can't even figure out which product I am actually buying.
I resolved the issue by removing it.. perhaps, that is the intended effect. Apologies to those with no choice.
..don't panic
Because programs are used to decode/encode the name. It's the same problem with Y2K, user agent strings, and so on. When programs expect data in a certain format, such as two digits for years or a single number after a u in a version string, they don't react well when the format is changed. RTFA.
What a fool believes, he sees, no wise man has the power to reason away.
I don't care what they call it so long as I don't have to install any toolbars.
Like seriously what is this 2003? It's crowding out my "Bonzi Buddy"
Because the old numbering system of incrementing by 1 was far too complicated. The new system is much easier to understand:
* Limited Update releases will be numbered in multiples of 20.
* We intend for Critical Patch Updates to continue to use odd numbers. The numbers will be calculated by adding multiples of five to the prior Limited Update and when needed adding one to keep the resulting number odd.
* Updates containing Norton instead of McAfee will be prime numbers
* If an update actually contains intentional regressions, it will end in a 9. We recommend you do not install these updates.
* If the update number is a prime but also a member of the fibonacci sequence, it is considered a "surprise" update: It will be automatically installed, and will contain 1 or more undesirable features. It may also install the ask toolbar.
Obviously this system is far superior.
After reading the Oracle announcement through three times, I actually checked my calendar to see if April 1st had somehow come around again.
Which is a distinct possibility if Oracle takes over the Gregorian Calendar next.
Koans and fables for the software engineer