Posted by ray_gans
on August 15, 2006 at 4:28 PM PDT
Sun is retiring the Mustang and Dolphin code names today and opening the JDK 7 project (formerly project Dolphin) on java.net.
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.