Steven A Rowe wrote:
However, I noticed a problem: in CHANGES.txt under the 2.3.0 release in the "Bug fixes" section, there is a gap in the sequence:
Argh! Yet more evidence that I cannot count :) This is the 2nd time I've done that!
But my script only notices that it's a numbered list, not the specific numbers on each item, and so re-numbers item #19 as #18, and then continues for all following items to be misaligned with CHANGES.txt. Should we preserve incorrect sequencing in the HTML format?
I think, ideally, the script should be the only thing that does the numbering ;) Then I can't make this mistake again.
So if we can simply put entries like this into CHANGES.txt, under the right section:
LUCENE-1010: Fixed corruption case when document with no term vector fields is added after documents with term vector fields. This case is hit during merge and would cause an EOFException. This bug was introduced with LUCENE-984. (Andi Vajda via Mike McCandless) LUCENE-1009: Fix merge slowdown with LogByteSizeMergePolicy when autoCommit=false and documents are using stored fields and/or term vectors. (Mark Miller via Mike McCandless) And then let the script take care of the numbering, that'd be great! Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
