Docs: Add release notes

Testing: make docs

Author: rschlussel-zz

HISTORY.rst

@@ -4,5 +4,9 @@ Release History
 ===============
 
 0.1.0 (2015-06-09)
----------------------
+------------------
 Initial release!
+
+1.1 (2015-09-23)
+----------------
+Release for Presto versions 0.103-0.115

docs/release.rst

@@ -1 +1,9 @@
-.. include:: ../HISTORY.rst
+=============
+Release Notes
+=============
+.. toctree::
+    :maxdepth: 1
+
+    release/release-1.2
+    release/release-1.1
+    release/release-0.1.0

docs/release/release-0.1.0.rst

@@ -0,0 +1,6 @@
+=============
+Release 0.1.0
+=============
+
+Initial Release!
+This release works for Presto versions 0.100-0.102

docs/release/release-1.1.rst

@@ -0,0 +1,5 @@
+===========
+Release 1.1
+===========
+
+This release works for Presto versions 0.103-0.115

docs/release/release-1.2.rst

@@ -0,0 +1,31 @@
+===========
+Release 1.2
+===========
+
+The default values in this release are intended to work with Presto versions
+0.116 through at least 0.130. However, the user can supply non-default
+configurations to use this release with other versions of Presto.
+
+General Fixes
+-------------
+* Fix server status to work with later versions of Presto
+* Exit with non-zero code when operations fail
+* Update configuration defaults for Presto versions >0.115
+* Make remote log directory configurable
+* Add support for specifying java8 home in config.json
+* :ref:`collect-logs` will use the log directory specified in
+  Presto's config.properties if configured.
+
+
+Configuration
+-------------
+Before this release, :ref:`configuration-deploy-label` would fill in default
+values for any required properties that the user did not supply in the
+configuration files. However, this created problems when different versions of
+Presto had different configuration requirements.  In particular, it became
+impossible to remove any required properties from the configuration even if the
+user's Presto version did not require those properties.
+
+In the current behavior, when the user needs to override the defaults in any
+configuration file, they must write out all the properties for that
+configuration file, which will be deployed as-is.