On 08/01/2011 05:33 AM, Wayne Fay 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
You realize that you're talking about open source communities -- we
scratch our own itches, and I'm literally months if not longer away
from getting jdk7 in production anywhere important, so even if I was a
committer on Lucene/Solr, I might not have done any testing with jdk7
until now myself... Hard to really blame them, IMO.
At first sight I'd not "blame" anybody in particular, also because the
Lucene guys - as far as I understand - just blogged "hey, we've got a
problem" without spreading FUD. As usual, the culprit is the blogsphere
where people like to amplify events because they have got some personal
bias, or to increment their click counter.
At second sight, I think that "open source" can't automatically mean
that some basic QA parts are missing. There are some small projects that
are the effort from one or just a few individuals; others, such as those
at the FSF or Apache Foundations, or Eclipse, or Netbeans, etc... where
you expect QA is taken seriously. Consider that there's not only the
risk of bug of the new JDK, but your own bugs (e.g. they discovered the
hidden dependency on a precise sequence of tests). Given that if you
have CI set up creating a new job for running JDK 7 is easy, frankly
they could have been that months ago.
Of course, the same holds for Oracle. I don't know whether they're
already doing that, but if I were them I'd set up myself some tests for
JDK running some popular, large framework / libraries. It would a be to
take advantage that even tests are FLOSS and while this would cost some
money, it must be compared with the costs of bad press.
Frankly, to me it holds the principle "if it's not tested it doesn't
work", so I assume that everything that others or I haven't explicitly
tested on Java 7 doesn't work (including all of my software, that I
haven't tested).
So I'd part the blame between Oracle and Lucene in this case. Just a few
of blame, because the thing doesn't sound very dramatic, until as soon
as there are no reports by other people discovering problems with their
own code.
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
java.net/blog/fabriziogiudici - www.tidalwave.it/people
[email protected]
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
