Perhaps add something to the effect that autoCommit=false was a new 2.3 feature, so it's only those who actually started using it who were at risk?
-Yonik On Fri, Feb 22, 2008 at 7:02 PM, Michael Busch <[EMAIL PROTECTED]> wrote: > Hi Team, > > the 2.3.1 release files will be available for download within the next > 24 hours. I'll announce the release tomorrow; you can find a draft of > the announcement below. Please let me know in case you want me to make > changes to the announcement within the next 24 hours. Thanks! > > -Michael > > > DRAFT: > > Release 2.3.1 of Lucene Java is now available! > > This release contains fixes for serious bugs in 2.3.0 that could cause > index corruptions in autoCommit=false mode. 2.3.1 does not contain any > new features, API or file format changes, which makes it fully > compatible to 2.3.0. > > We would like to encourage everyone who currently uses Lucene Java 2.3.0 > to upgrade to 2.3.1 to prevent possible index corruptions! > > > The detailed change log is at: > http://svn.apache.org/repos/asf/lucene/java/tags/lucene_2_3_1/CHANGES.txt > > Binary and source distributions are available at > http://www.apache.org/dyn/closer.cgi/lucene/java/ > > Lucene artifacts are also available in the Maven2 repository at > http://repo1.maven.org/maven2/org/apache/lucene/ > > -Michael (on behalf of the Lucene team) > > > --------------------------------------------------------------------- > 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]
