Hi, >From my perspective the argument is:
A missing/temporary unavailable external resource is no problem of a release. It was fixed by Oracle, so only temporary and all is fine again. Just because you *may* not build javadocs at some time in the future does not rectify to hold a release. How do maven-based projects handle this? Do they never release because maven-central at some time may be overloaded and may not deliver the dependencies - or dependencies may got deleted because of error? If this would be the case, there wouldn't be any project using maven on earth - maybe we should have told them about those risks - the world would be free of maven - juhee :-) Happy Thanksgiving, god bless Maven! Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Yonik > Seeley > Sent: Wednesday, November 23, 2011 11:30 PM > To: [email protected] > Subject: Re: [VOTE] Release Lucene/Solr 3.5.0, RC2 > > On Wed, Nov 23, 2011 at 5:13 PM, Uwe Schindler <[email protected]> wrote: > > As far as I remember you cannot vote against... > > Re-read what I wrote: one should debate the merit of the actual > argument/issues, not "your vote doesn't count". > > -Yonik > http://www.lucidimagination.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
