Hi, Don't be disappointed - I just say this: I would never have denied a release with the Jetty UTF-8 bug! This bug was clearly out of our scope; so I don’t care, I helped to investigate it, but fixing was not in Lucene's responsibility, sorry. A release with the Jetty UTF-8 bug or the XALAN XSLTC-Uppercase-Bug would always get +1 from me - especially as Apache releases source code not binary artifacts. And OUR source code was correct - PERIOD. If it does not work with Jetty version XYZ its not our problem.
Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Robert Muir [mailto:rcm...@gmail.com] > Sent: Monday, April 23, 2012 11:39 PM > To: dev@lucene.apache.org > Subject: Re: [DISCUSS] Build/deploy Maven artifacts outside of Lucene/Solr > > On Mon, Apr 23, 2012 at 5:37 PM, Uwe Schindler <u...@thetaphi.de> wrote: > > Hi, > > > > The answer is quite clear: Not our problem! Note that bug in our release > notes that there is a not-yet fixed zookeeper bug. We cannot make the world > perfect. If there is a bug outside our responsibility, we can document it, > but not > necessarily fix it. > > > > Just bookmarking this response to link to in the next release vote, so I can > reference it for the guy that i know likes to run tests with > -Dmultiplier=10000 -Diters=10000 and find horrible JVM bugs, etc before > release :) > > -- > lucidimagination.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional > commands, e-mail: dev-h...@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
