[Lucene-java Wiki] Update of "ReleaseNote53" by jpountz

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

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

The "ReleaseNote53" page has been changed by jpountz:
https://wiki.apache.org/lucene-java/ReleaseNote53?action=diff&rev1=5&rev2=6

Comment:
reordered the changes a bit

  
  Lucene 5.3.0 Release Highlights:
  
+ API Changes
+  * PhraseQuery and BooleanQuery are now immutable
+ 
+ New features:
-  * SlowCompositeReaderWrapper.getSorted[Set]DocValues() become much faster on highly segmented index.
-  * New common suggest API that mirrors Lucene's Query/IndexSearcher APIs for Document based suggester.
-  * Added experimental BKD geospatial tree doc values format and queries, for fast "bbox/polygon contains lat/lon points"
-  * IndexWriter can now be initialized from an already open near-real-time or non-NRT reader
-  * Added GeoPointField, GeoPointInBBoxQuery, GeoPointInPolygonQuery for simple "indexed lat/lon point in bbox/shape" searching
   * Added a new org.apache.lucene.search.join.CheckJoinIndex class that can be used to validate that an index has an appropriate structure to run join queries
   * Added a new BlendedTermQuery to blend statistics across several terms
+  * New common suggest API that mirrors Lucene's Query/IndexSearcher APIs for Document based suggester.
+  * IndexWriter can now be initialized from an already open near-real-time or non-NRT reader
   * Add experimental range tree doc values format and queries, based on a 1D version of the spatial BKD tree, for a faster and smaller alternative to postings-based numeric and binary term filtering.  Range trees can also handle values larger than 64 bits.
+ 
+ Geo-related features and improvements
+  * Added GeoPointField, GeoPointInBBoxQuery, GeoPointInPolygonQuery for simple "indexed lat/lon point in bbox/shape" searching
+  * Added experimental BKD geospatial tree doc values format and queries, for fast "bbox/polygon contains lat/lon points"
   * Use doc values to post-filter GeoPointField hits that fall in boundary cells, resulting in smaller index, faster searches and less heap used for each query
+ 
+ Optimizations
   * Reduce RAM usage of FieldInfos, and speed up lookup by number, by using an array instead of TreeMap except in very sparse cases
+  * Faster intersection of the terms dictionary with very finite automata, which can be generated eg. by simple regexp queries
+ 
-  * Various bugfixes and optimizations since the 5.1.0 release.
+  * Various bugfixes and optimizations since the 5.2.0 release.
  
  Please read CHANGES.txt for a full list of new features.