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.
The last few months have been exciting for Java SE with the many JavaOne activities and presentations, our announcement to open source the JDK, and getting beta 2 out the door. Let me tell you, it's kept us all very busy here at Sun! Things aren't slowing down either, so I'd like to give you a brief update as to what's going on.
It's been almost a year now since we started the JDK Community on java.net and I'd like to give a well deserved "Thank You!" to all of you who have participated and visited the site. As part of this thanks, I'd like to provide an update to where we stand and where we're going.
Roadmap for Mustang
Sun began the Mustang project (Java SE 6) on java.net over a year ago when we started releasing weekly binary and source snapshots that included bug fixes and minor enhancements to Tiger (Java SE 5). Over time we've introduced major features described by new and existing JSRs that are part of the Mustang release.
Thanks to thoughtful comments and questions from the community and great feedback at Java One, Sun has revised the Java Research License (JRL) to address several concerns that have been brought to our attention -- in particular with how it affects open source developers.
I am very pleased to announce that Sun has released a new license for the JDK called the Java Internal Use License (JIUL or "jewel"). This license lets developers easily make changes to the JDK for internal deployments. It's free, click-through and should be easy-to-read by non-lawyers.