One Step Ahead
Keeping up with the pre-JavaOne crunch
Yesterday, Joshua Marinacci blogged that JavaOne's approach is like the preparation crunch that precedes a big holiday like Christmas. In the comments, I asked if he really meant by his metaphor that he'd literally been working on JavaOne stuff for weeks, or months. He writes, "by the time JavaOne gets here, I will have spent almost two full months getting ready. Since I came back from Sydney March 11th."
True dat. Over here on the editorial side, this week started with a torrent of JavaOne-related meetings, which continues today, along with the at-deadline writing of the crossword puzzles for the JavaOne Today newspaper. Throw in secret announcements, guest appearances, and an inbox that went from empty to 40 overnight, and it's clear that the crunch is on.
Presumably working their own crunch to pull off a JavaOne-week release,
NetBeans QA is announcing that the NetBeans Community has approved NetBeans 6.1 for FCS. "We are pleased to announce the results of the NetBeans IDE 6.1 Community Acceptance Survey that ended April 16th: 91% of respondents agree that NetBeans 6.1 is stable enough to move into FCS! (A few respondents recommended that we fix some more issues, and we will try to deliver the fixes via the Update Center as soon as possible.)"
Also in Java Today,
the latest SDN Mobility Tech Tip is about Using Filters With the Java ME Device Matrix. "Let's say you have a design for a mobile application, and you know what technology (JSR) is required by the platform. You then want to know: What handsets will support your design? The SDN Device Matrix is a table that lists information on hundreds of devices that run Java ME technology."
Today's Weblogs begin with some advice from Tom