lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "ReleaseNote34" by MikeMcCandless
Date Fri, 09 Sep 2011 18:49:33 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "ReleaseNote34" page has been changed by MikeMcCandless:
http://wiki.apache.org/solr/ReleaseNote34?action=diff&rev1=4&rev2=5

  {{{
- MMM??? 2011, Apache Solr™ 3.4 available
+ MMM??? 2011, Apache Solr™ 3.4.0 available
- The Lucene PMC is pleased to announce the release of Apache Solr 3.4.
+ The Lucene PMC is pleased to announce the release of Apache Solr 3.4.0.
  
  Solr is the popular, blazing fast open source enterprise search platform from 
  the Apache Lucene project. Its major features include powerful full-text 
@@ -18, +18 @@

     http://www.apache.org/dyn/closer.cgi/lucene/solr (see note below).
  
  If you are already using Apache Solr 3.1, 3.2 or 3.3, we strongly
- recommend you upgrade to 3.4 because of the index corruption bug on OS
+ recommend you upgrade to 3.4.0 because of the index corruption bug on OS
- or computer crash or power loss (LUCENE-3418), now fixed in 3.4.
+ or computer crash or power loss (LUCENE-3418), now fixed in 3.4.0.
  
  See the CHANGES.txt file included with the release for a full list of
  details.
  
- Solr 3.4 Release Highlights:
+ Solr 3.4.0 Release Highlights:
  
-   * Bug fixes and improvements from Apache Lucene 3.4, including a
+   * Bug fixes and improvements from Apache Lucene 3.4.0, including a
      major bug (LUCENE-3418) whereby a Lucene index could
      easily become corrupted if the OS or computer crashed or lost
      power.
@@ -60, +60 @@

  
    * Various fixes for multi-threaded DataImportHandler.
  
- 
  Note: The Apache Software Foundation uses an extensive mirroring network for
  distributing releases.  It is possible that the mirror you are using may not
  have replicated the release yet.  If that is the case, please try another

Mime
View raw message