2.2.1 Release notes update

2.2.1 Release notes update

Documentation/Release-Notes/MaxScale-2.2.1-Release-Notes.md

@@ -8,6 +8,12 @@ release 2.2.0.
 For any problems you encounter, please consider submitting a bug
 report at [Jira](https://jira.mariadb.org).
 
+## Update from 2.2.0
+
+Since version 2.2.0 MaxScale binlog server can accept GTID
+slave registration from MariaDB 10.X slaves and can also
+register to Master server MariaDB 10.x using GTID.
+
 ## Changed Features
 
 ### Process identity
@@ -29,9 +35,11 @@ root@host:~# maxscale --user=root ...
 
 * The `mariadb10_slave_gtid` parameter was removed and slave connections can now
   always register with MariaDB 10 GTID.
+  This means the gtid_maps SQLite database is always updated.
 
 * The `binlog_structure` parameter was removed and the binlogs are stored
-  automatically in 'tree' mode when `mariadb10_master_gtid` is enabled.
+  automatically in 'tree' mode when `mariadb10_master_gtid` is enabled
+  (GTID registration to master).
 
 * If `mariadb10_master_gtid` is enabled, the `transaction_safety` is
   automatically enabled. In MaxScale 2.2.0, if `transaction_safety` was disabled

Documentation/Upgrading/Upgrading-To-MaxScale-2.2.md

@@ -25,3 +25,8 @@ Modules may now use a built-in regular expression string parameter type instead
 of a normal string when accepting patterns. The modules that use the new regex
 parameter type are *qlafilter* and *tee*. When inputting pattern, enclose the
 string in slashes, e.g. `match=/^select/` defines the pattern `^select`.
+
+### Binlog Server
+
+Binlog server automatically accepts GTID connection from MariaDB 10 slave servers
+by saving all incoming GTIDs into a SQLite map database.