哇! 我没看错吧? J2SE 6.0!!!!!!

核心提示：不过真的是哦：Download J2SE 6.0Posted by daniel on November 16, 2004 at 07:57 AM Comments (0) No, really, we mean it. The brand new java.net "Mustang" Snaps

不过真的是哦：

Download J2SE 6.0

Posted by daniel on November 16, 2004 at 07:57 AM Comments (0)

No, really, we mean it.

The brand new java.net "Mustang" Snapshot Releases are perfect for you. These snapshots give developers access to the latest features and fixes made to the J2SE 6.0 release. Whether you choose to download the binaries or the source code, be aware that these early releases are only lightly tested before being made available so if you are risk averse or ineXPerienced, these snapshot releases should be avoided. If you live for adventure, join us on the cutting edge.

The Mustang snapshot news leads off today's Weblogs. Mark Rheinhold explains that this is Another experiment in openness. Building on the sUCcess of releasing the Tiger Snapshots, they will be releasing Mustang starting with build twelve. In addition "For the first time ever we're shipping source bundles for a J2SE release while it's under active development (gulp). This should make it easier for interested developers to contribute to the release as it evolves." The hope is that soon there will be " a streamlined PRocess for patch submission so that you can send code directly to real live JDK engineers rather than paste it into a bug report, cross your fingers, and hope for the best. a streamlined process for patch submission so that you can send code directly to real live JDK engineers rather than paste it into a bug report, cross your fingers, and hope for the best."

This is a big deal. I'm sure you can say "but why didn't you ..." or "it's not ..." but, in my opinion, this is a huge step. Mark also asks for you to submit ideas on how the process can be improved. Finally, anticipating some obvious feedback, Mark notes that "The source bundles are covered by the Java Research License. The JRL is, to my non-lawyerly brain, a big improvement over the old SCSL license -- for one thing, I can understand it! The JRL also gives developers and researchers more flexibility than SCSL did, though it's still not an actual open source license in OSI terms (sorry)."