I'd like to suggest that Oracle was asking people to test their projects with 7 and let them know if they ran into problems. Oracle *cannot* possibly test all products/projects and as important as Lucene may seem to you, I have only once run into it during an engagement (and I run through dozens a clients per year).
Bottom line, everyone knew it was coming.... the builds were freely avaliable. I've been using 7 on my Mac for months so.... I don't have much sympathy in this case. Regards, Kirk On Aug 1, 2011, at 12:53 AM, opinali wrote: > Yes that looks clear from the article. How stupid is that, start > testing a hugely popular project like Lucene on a hugely important JDK > update a single week before the latter is GA? And then complaining > that *Oracle* did not turn around immediately on the bug report, over > a weekend no less. > > In all fairness, the loop optimization bug has a submit date of May > 13, it was not discovered by the Lucene team. Maybe before Lucene, > Oracle evaluated that to be an extremely rare thing that wouldn't like > affect real-world code (Pentium FDIV all over again... never make this > kind of bet with bugs that silently produce wrong results, no matter > how huge your internal testing with real app code - as a single > important/vocal affected user/project means loads of shit hitting the > fan). So thumbs down to Oracle, too, for glossing over this particular > bug to keep their planned release date. But Lucene's behavior was just > as irresponsible. > > One interesting comment is to complain that the GA build was the same > as the month-old b147. That's stupid, this is how a RC build is > SUPPOSED to be. Old Sun never did that properly, the GA release of a > major JDK update (and even most minor updates when these had beta > builds) was never identical to the last RC; it always had a few last- > minute changes (often revealed by a "micro-build" letter suffix, e.g. > "125e" where only that latter was increased from the last RC). JDK 7 > is the first release I remember that's bit-per-bit identical to the > last public prerelease build, and that is good because that's a build > that thousands of people and projects have tested, which reduces the > risk of last-minute surprises in the GA. > > A+ > Osvaldo > > On Jul 31, 5:23 pm, Fabrizio Giudici <fabrizio.giud...@tidalwave.it> > wrote: >> Uwe has posted a clear and detailed crono-story of the thing: >> >> http://blog.thetaphi.de/2011/07/real-story-behind-java-7-ga-bugs.html >> >> Do I understand well that they started testing Lucene on Java 7 with >> Hudson only one week ago? >> >> -- >> Fabrizio Giudici - Java Architect, Project Manager >> Tidalwave s.a.s. - "We make Java work. Everywhere." >> java.net/blog/fabriziogiudici -www.tidalwave.it/people >> fabrizio.giud...@tidalwave.it > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to javaposse@googlegroups.com. > To unsubscribe from this group, send email to > javaposse+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javaposse@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
