The problem is: duplication of documentation is dangerous and only
creates more work for the RM.

if we start duplicating things like build instructions across both
BUILD.txt and CHANGES.txt, or whole text files, then its only a matter
of time before someone says in the next release vote:

XYZ is mentioned in foo/BUILD.txt but this is inconsistent with
foo/CHANGES.txt or XYZ/BUILD.txt is out of date with respect to
/BUILD.txt

On Fri, Apr 6, 2012 at 7:40 AM, Uwe Schindler <[email protected]> wrote:
> It was a suggestion, no critisism. Why do you attack me?
>
> -----
> 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 1:37 PM
>> To: [email protected]
>> Subject: Re: VOTE: Lucene/Solr 3.6
>>
>> On Fri, Apr 6, 2012 at 7:35 AM, Uwe Schindler <[email protected]> wrote:
>> > Hi Robert,
>> >
>> > In the case that you have to fix this one and respin, could you please 
>> > also fix
>> my CHANGES.txt complaint? The Ivy changes were such a huge piece of work, it
>> should be mentioned with names in CHANGES.txt.
>> >
>>
>>
>> > One more thing: When you extract Solr src package you are at the top-level
>> root. In my opinion these license/info/build... files should also be placed 
>> there
>> (including a BUILD.txt on the root!).
>> >
>>
>> we aren't doing this.
>>
>> We put license.txt/notice.txt at the root only because we are legally 
>> required to
>> do so.
>>
>>
>> --
>> 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]
>



-- 
lucidimagination.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to