Then please remove the directory refactoring also from CHANGES.txt. This is still a blocker to me. It should not be *documented* in the CHNAGES.txt, I said it should be mentione:
--------------------- Build * LUCENE-xxxx: Moved build system to use Apache Ivy for retrival of 3rd party JAR files. (Robert Muir, Chris Male, Uwe Schindler,...) --------------------- ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Robert Muir [mailto:[email protected]] > Sent: Friday, April 06, 2012 12:43 PM > To: [email protected] > Subject: Re: VOTE: Lucene/Solr 3.6 > > On Fri, Apr 6, 2012 at 6:35 AM, Uwe Schindler <[email protected]> wrote: > > > > - URGENT: Our change to IVY is nowhere noted in CHANGES.txt!!! This is a > major problem, as this is a huge change and people used to building Lucene > from source only looking into CHANGES.txt will fail to build without > inspecting > BUILD.txt. We have changes entries for the refactoring of the build directory > structure (by Steven), but not for the Ivy change. Very bad! We must at least > tell people about that in the release notes, otherwise -1. > > > > This information is in BUILD.txt, which is where the instructions for building > are. > People building need to look at BUILD.txt, thats what this file exists for. > We don't need to duplicate documentation across *BOTH* build.txt and > changes.txt, thats ridiculous. > > -- > 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]
