Merge pull request #5035 from palecur/relnotes

Adds release notes for Kibana 4.2, minor cleanup elsewhere.

docs/index.asciidoc

@@ -3,7 +3,7 @@
 
 :ref: http://www.elastic.co/guide/en/elasticsearch/reference/current/
 :shield: https://www.elastic.co/guide/en/shield/current
-:k4pull: https://github.com/elastic/kibana/pull/
+:k4issue: https://github.com/elastic/kibana/issues/
 
 include::introduction.asciidoc[]
 
@@ -25,4 +25,4 @@ include::settings.asciidoc[]
 
 include::production.asciidoc[]
 
-include::whats-new.asciidoc[]
+include::releasenotes.asciidoc[]

docs/introduction.asciidoc

@@ -13,9 +13,9 @@ dashboards that display changes to Elasticsearch queries in real time.
 Setting up Kibana is a snap. You can install Kibana and start exploring your
 Elasticsearch indices in minutes -- no code, no additional infrastructure required. 
 
-NOTE: This guide describes how to use Kibana 4.1. For information about what's new
-in Kibana 4.1, see <<whats-new>>. For earlier versions of Kibana 4, see the 
-http://www.elastic.co/guide/en/kibana/4.0/index.html[Kibana 4 User Guide]. For information about Kibana 3, see the 
+NOTE: This guide describes how to use Kibana 4.2. For information about what's new
+in Kibana 4.2, see the <<releasenotes, release notes>>. For earlier versions of Kibana 4, see the 
+http://www.elastic.co/guide/en/kibana/4.1/index.html[Kibana 4.1 User Guide]. For information about Kibana 3, see the 
 http://www.elastic.co/guide/en/kibana/3.0/index.html[Kibana 3 User Guide].
 
 [float]

docs/releasenotes.asciidoc

@@ -0,0 +1,35 @@
+[[releasenotes]]
+== Kibana 4.2 Release Notes
+
+* Starting with the 2.0 release of Elasticsearch, you can https://github.com/elastic/elasticsearch/pull/9670[no longer] 
+reference fields by leafnode. For example, the `geoip.country_code` field can no longer support searches such as 
+`country_code:US`. Instead, use the entire field name. This change affects saved searches, visualizations, and dashboards 
+from previous versions of Kibana.
+
+[float]
+[[enhancementss]]
+== Enhancements
+
+* {k4issue}2855[Issue 2855]: Configurable Kibana log levels.
+* {k4issue}4204[Issue 4204]: Plugin manager for Kibana server.
+* {k4issue}4218[Issue 4218]: New interface for switching between plugins.
+* {k4issue}3270[Issue 3270]: Server status page.
+* {k4issue}2245[Issue 2245]: Customizable visualization descriptions.
+* {k4issue}2906[Issue 2906]: Dark theme added to dashboards.
+* {k4issue}1902[Issue 1902]: Tile maps support configurable WMS-compliant map servers.
+* {k4issue}2245[Issue 2245]: Customize legends for the Filter aggregation.
+* {k4issue}4817[Issue 4817]: Advanced Settings option maps values to colors. 
+* {k4issue}2874[Issue 2874]: Advanced Settings option to change default timepicker value.
+* {k4issue}2760[Issue 2760]: Adds ability to filter by clicking on a legend. 
+* {k4issue}485[Issue 485]: Adds color rationalization across visualizations.
+
+[float]
+[[bugfixes]]
+== Bug Fixes
+
+* {k4issue}4902[Issue 4902]: Fixes a problem with object export logic.
+* {k4issue}3694[Issue 3694]: Improves timezone handling in visualizations as a result of Olson timezone support in ES.
+* {k4issue}4261[Issue 4261]: Improves highlighting on embedded searches in dashboards.
+* {k4issue}4816[Issue 4816]: Improves history limit setting to clear past history.
+* {k4issue}4670[Issue 4670]: Fixes issue with range aggregation.
+* {k4issue}4244[Issue 4244]: Fixes issue with pie chart labels.

docs/tilemap.asciidoc

@@ -27,8 +27,7 @@ Coordinates* on a single chart. A multiple chart split must run before any other
 Tile maps use the *Geohash* aggregation as their initial aggregation. Select a field, typically coordinates, from the
 drop-down. The *Precision* slider determines the granularity of the results displayed on the map. See the documentation 
 for the {ref}/search-aggregations-bucket-geohashgrid-aggregation.html#_cell_dimensions_at_the_equator[geohash grid] 
-aggregation for details on the area specified by each precision level. As of the 4.1 release, Kibana supports a maximum 
-geohash length of 7.
+aggregation for details on the area specified by each precision level. Kibana supports a maximum geohash length of 7.
 
 NOTE: Higher precisions increase memory usage for the browser displaying Kibana as well as for the underlying 
 Elasticsearch cluster.