Slashdot Mirror

← Back to Stories (view on slashdot.org)

To Avoid Confusion: Oracle's Confusing New Java Numbering Scheme

Posted by timothy on from the only-have-eyes-for-u dept.

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.

5 of 183 comments (clear)

  1. CPU=Critical Patch Update by fnj · · Score: 5, Informative

    An absurd TLA overloading.

    1. Re:CPU=Critical Patch Update by Tackhead · · Score: 5, Funny

      Its not like they could have just said Critical update patch...oh no, we need to make things confusing.

      What happens when admins get confused and pour the contents of their beverage containers into their servers?

      We apologize for the confusion in the Critical Patch Updates. The individuals responsible have been sacked. To avoid further confusion, all CPUs will be processed through CUPS, the Critical Update Patch Server.

      And now the goddamn printer doesn't work.

  2. Re:IQ by SJHillman · · Score: 5, Funny

    I hear Mensa is planning on using the Microsoft Copy dialog instead.

    "You have 4 minutes left, then 3 minutes, then 29 minutes, then 1800 years, then 32 seconds, then potato. What is the next number in the sequence?"

  3. Re:IQ by Barefoot+Monkey · · Score: 5, Funny

    That's easy. The next number in the sequence is (not responding).

  4. Re:Why Does Name Matter? by LordLimecat · · Score: 5, Funny

    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.