Ray Gans's Blog

Mustang and Dolphin... we'll miss you

Yes, we must retire some old friends. Management says it's time to drop these code names and develop a new project naming system around our open source model. Better now than after Dolphin get's firmly entrenched – and as for Mustang, well it's almost done anyway.

So with some sadness, we're walking Mustang out from her stable one last time to let her roam free in the meadows and we're opening the gate so Dolphin can return to the sea. Code names come and go and it's time to move on to our bright new future.

What has been Project Mustang on java.net will now be recast as JDK 6 (no surprise there I hope) and I'm happy to say we're launching JDK 7 on java.net today!

The mustang project on java.net has been redirected to the new URL https://jdk6.dev.java.net.

Our new project, JDK 7 can be found at https://jdk7.dev.java.net.

JDK 7 (formerly Project Dolphin)

We have posted build 1 on the JDK 7 download site (just a version string change from JDK 6 build 92). Plus by popular demand, we'll soon be hosting a Subversion repository of JDK 7 code from java.net as well.

We'll only be updating the JDK 7 binaries periodically for a month or two, since most of our efforts are still on JDK 6, but we do plan to start posting source and binary updates weekly again as soon as possible. New builds will track with improvements made to the JDK 6 release plus add additional enhancements and features over time.

Note that some javadocs still say Java SE 6 – we'll update them to Java SE 7 sometime during the next few weeks).

Wait... so how can Sun roll out a new project before it's been approved by the JCP?

I don't think anyone expects Java SE to stop at version 6! In anticipation of a future release, we are continuing work on enhancements to Sun's implementation that are covered by the Java SE 6 specification – things that were deemed too risky or disruptive to include at this time in the code base for JDK 6. This would include performance enhancements, bug fixes and other improvements (such as contributions made by developers) that we just didn't have time to get into JDK 6. Minor enhancements to the API may also be included – with the clear understanding that any change to the specification must be approved by the JCP before it can be included in the final release.

What about Open Source?

Laurie Tolson, VP Java Platform Group, gave an update to press and analysts yesterday about our plans to open source the JDK. Take a look at our new JDK open source community site at http://community.java.net/jdk/opensource to find out more and talk to us. We're interested in your thoughts and opinions about an open source JDK. Mark Reinhold and Danny Coward also tell about the latest in their blogs.

Comments

• :(
  
  Just as i waited to see what will be the codename for JavaSE 8

  Posted by: kirillcool on August 15, 2006 at 04:41 PM

• Not a big deal, but on the JDK 6 page it always mentions "JDK 6" (with a space). On the new JDK 7 page it always mentions "JDK7" (no space). I don't know if there's a strict rule about it, but personally I'd prefer to see a space in there; either way, consistency is best. Also, both pages refer to the "J2SE bug reporting channels", might be nice to update that to say Java SE instead.

  Thanks, Chris (aka the Naming Police).

  Posted by: campbell on August 15, 2006 at 05:25 PM

• Whoops, missed that... we need to add the space for JDK 7. Thanks!

  Posted by: ray_gans on August 15, 2006 at 05:29 PM

• Why does "Management" waste their time with silly things like this? I can just imagine the hours of useless meetings that went into this. The code names were fun (pssst, hey management, thats a GOOD thing), and this doesn't actually help anything. If anything the redirection should have gone in the other direction, jdk6->mustang. Oh well, this isn't the first time management chooses to make things a little more boring.

  Posted by: swpalmer on August 16, 2006 at 05:53 AM

• I liked the codenames idea. :(

  Posted by: olsonje on August 16, 2006 at 07:37 AM

• This is silly. But here's a chance for Sun to listen to the budding Java SE hacking community and change back to using code names.

  Also, you've now muddied the naming convention waters. Previously, we understood that "Mustang" = "Java SE 6" and one could download either the JDK or the JRE.

  Now, the project is called "JDK 6" = "Java SE 6", but the JRE is part of the JDK project? WTF? (I know that the JRE is bundled with the JDK, but really... it's like calling Solaris OE part of the Forte Developer Kit.)

  Heh - the Java SE 5/JDK 5 web site is still https://tiger.dev.java.net/. :-)

  Posted by: mapnjd on August 17, 2006 at 01:32 AM

• Although the JDK is a great product, it's (lack of) naming convention is one of the biggest mistakes in Java history I believe. Try explaining the following terms to non-java programmer and convince them that Java is the most mature computer language: - 1.2, 1.3, 1.4, 1.5 are all Java 2 (so if you buy a book about Java 2, make sure it's at least 1.5...) - 5.0 came directly after 1.4 and is backward compatible - 1.6 is bigger then 5.0 - Most call 5.0 either tiger or 1.5, only marketing calls it 5.0 - JDK is SDK is JDK - J++ and J# are not improved java versions None the less, dropping the 2 in J(2)SE and J(2)EE seems a good thing. Dropping the ".0" for JDK 6 also seems a good thing in long term. As long as this convention hold up for the next 30 years :) I seriously hope that JDK 12 will be named "JDK 12" and not "JDK X²++" or something other which looks very cool.

  Posted by: ge0ffrey on August 17, 2006 at 01:47 AM

• Ah, well, I always tell people that there is a technical numbering and a marketing numbering. Take Microsoft Word XP, 2003, Vista whatever, in the about box it just says "10" or "11". Hence I always talk about Java in 1.x and the marketing guys can have their moment... But if the marketing comes back down to earth and just drops the "1." then that is good.

  Posted by: tbee on August 18, 2006 at 02:48 AM

• Ok, you management guys can call your projects whatever you want.

  However, we (the java community) love codenames. So we'll go on calling the toys tiger, mustang and dolphin.

  For JDK 8 I suggest 'bunny'. No need for approval by the management :-) .

  Posted by: tauronx on August 23, 2006 at 07:14 AM

This work is licensed under a Creative Commons License.