Updated 1.2 release notes.

Release-Notes/MaxScale-1.2.0-Release-Notes.md

@@ -27,8 +27,8 @@ A quick list of changes in installation directories and file names:
 ### Client side SSL encryption
 MaxScale now supports SSL/TLS encrypted connections to MaxScale.
 
-### Monitor scripts
+### Launchable scripts
-State changes in backend servers can now trigger the execution of a custom script. With this you can easily customize MaxScale's behavior.
+Now you can configure MaxScale monitor module to automatically launch a script when it detects change in the state of a backend server. The script can be any customer script defined by you to take diagnostic or reporting action. With this you can easily customize MaxScale's behavior.
 
 ## Bug fixes
 
@@ -40,18 +40,58 @@ Here is a list of bugs fixed since the release of MaxScale 1.1.1.
 | [MXS-40](https://mariadb.atlassian.net/browse/MXS-40) | Display logged in users | 
 | [MXS-113](https://mariadb.atlassian.net/browse/MXS-113) | MaxScale seems to fail if built against MariaDB 10.0 libraries | 
 | [MXS-116](https://mariadb.atlassian.net/browse/MXS-116) | Do not run maxscale as root. | 
+| [MXS-117](https://mariadb.atlassian.net/browse/MXS-117) | Allow configuration of the log file directory | 
 | [MXS-125](https://mariadb.atlassian.net/browse/MXS-125) | inconsistency in maxkeys/maxpassword output and parameters | 
+| [MXS-128](https://mariadb.atlassian.net/browse/MXS-128) | cyclic dependency utils -> log_manager -> utils | 
 | [MXS-136](https://mariadb.atlassian.net/browse/MXS-136) | Check for MaxScale replication heartbeat table existence before creating | 
 | [MXS-137](https://mariadb.atlassian.net/browse/MXS-137) | cannot get sql for queries with length >= 0x80 | 
 | [MXS-139](https://mariadb.atlassian.net/browse/MXS-139) | Schemarouter authentication for wildcard grants fails without optimize_wildcard | 
 | [MXS-140](https://mariadb.atlassian.net/browse/MXS-140) | strip_db_esc does not work without auth_all_servers | 
-| [MXS-162](https://mariadb.atlassian.net/browse/MXS-162) | Fix Incorrect info in Configuration Guide | 
+| [MXS-162](https://mariadb.atlassian.net/browse/MXS-162) | Fix Incorrect info in Configuration Guide |
-| [MXS-163](https://mariadb.atlassian.net/browse/MXS-163) | Reload config leaks memory | 
 | [MXS-165](https://mariadb.atlassian.net/browse/MXS-165) | Concurrency issue while incrementing sessions in qlafilter | 
 | [MXS-166](https://mariadb.atlassian.net/browse/MXS-166) | Memory leak when creating a new event | 
 | [MXS-171](https://mariadb.atlassian.net/browse/MXS-171) | Allow reads on master for readwritesplit | 
 | [MXS-176](https://mariadb.atlassian.net/browse/MXS-176) | Missing dependencies in documentation | 
+| [MXS-180](https://mariadb.atlassian.net/browse/MXS-180) | MariaDB10 binlog router compatibilty |
 | [MXS-181](https://mariadb.atlassian.net/browse/MXS-181) | Poor performance on TCP connection due to Nagle's algoritm | 
+| [MXS-182](https://mariadb.atlassian.net/browse/MXS-182) | SHOW SLAVE STATUS and maxadmin "show services" for binlog router needs updated when used with MariaDB 10 Master | 
 | [MXS-212](https://mariadb.atlassian.net/browse/MXS-212) | Stopped services accept connections | 
 | [MXS-225](https://mariadb.atlassian.net/browse/MXS-225) | RPM Debug build packages have no debugging symbols | 
 | [MXS-227](https://mariadb.atlassian.net/browse/MXS-227) | Memory leak in Galera Monitor | 
+| [MXS-244](https://mariadb.atlassian.net/browse/MXS-244) | Memory leak when using prepared statements without arguments | 
+
+## Known Issues and Limitations
+
+There are a number bugs and known limitations within this version of MaxScale, the most serious of this are listed below.
+
+* MaxScale can not manage authentication that uses wildcard matching in hostnames in the mysql.user table of the backend database. The only wildcards that can be used are in IP address entries.
+
+* When users have different passwords based on the host from which they connect MaxScale is unable to determine which password it should use to connect to the backend database. This results in failed connections and unusable usernames in MaxScale.
+
+* LONGBLOB are currently not supported.
+
+* Galera Cluster variables, such as @@wsrep_node_name, are not resolved by the embedded MariaDB parser.
+
+* The Database Firewall filter does not support multi-statements. Using them will result in an error being sent to the client.   
+
+## Packaging
+
+Both RPM and Debian packages are available for MaxScale in addition to the tar based releases previously distributed we now provide
+
+* CentOS/RedHat 5
+
+* CentOS/RedHat 6
+
+* CentOS/RedHat 7
+
+* Debian 6
+
+* Debian 7
+
+* Ubuntu 12.04 LTS
+
+* Ubuntu 14.04 LTS
+
+* SuSE Linux Enterprise 11
+
+* SuSE Linux Enterprise 12