Merge branch '2.3' into 2.4

Documentation/Changelog.md

@@ -60,6 +60,7 @@ For more details, please refer to:
 
 For more details, please refer to:
 
+* [MariaDB MaxScale 2.3.15 Release Notes](Release-Notes/MaxScale-2.3.15-Release-Notes.md)
 * [MariaDB MaxScale 2.3.14 Release Notes](Release-Notes/MaxScale-2.3.14-Release-Notes.md)
 * [MariaDB MaxScale 2.3.13 Release Notes](Release-Notes/MaxScale-2.3.13-Release-Notes.md)
 * [MariaDB MaxScale 2.3.12 Release Notes](Release-Notes/MaxScale-2.3.12-Release-Notes.md)

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

@@ -0,0 +1,37 @@
+# MariaDB MaxScale 2.3.15 Release Notes
+
+Release 2.3.15 is a GA release.
+
+This document describes the changes in release 2.3.15, when compared to the
+previous release in the same series.
+
+For any problems you encounter, please consider submitting a bug
+report on [our Jira](https://jira.mariadb.org/projects/MXS).
+
+## Bug fixes
+
+* [MXS-2786](https://jira.mariadb.org/browse/MXS-2786) Peer certificate isn't mandatory
+* [MXS-2782](https://jira.mariadb.org/browse/MXS-2782) Wrong thread id causes MaxScale to crash.
+* [MXS-2775](https://jira.mariadb.org/browse/MXS-2775) Document that a crashed master can break auto_rejoin with semisynchronous replication
+* [MXS-2773](https://jira.mariadb.org/browse/MXS-2773) SkySQL: Maxscale 2.4.2 takes longer to allow connections after restart compared to 2.3.9
+* [MXS-2763](https://jira.mariadb.org/browse/MXS-2763) ssl_version values are system dependent
+
+## Known Issues and Limitations
+
+There are some limitations and known issues within this version of MaxScale.
+For more information, please refer to the [Limitations](../About/Limitations.md) document.
+
+## Packaging
+
+RPM and Debian packages are provided for supported the Linux distributions.
+
+Packages can be downloaded [here](https://mariadb.com/downloads/#mariadb_platform-mariadb_maxscale).
+
+## Source Code
+
+The source code of MaxScale is tagged at GitHub with a tag, which is identical
+with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale
+is `maxscale-X.Y.Z`. Further, the default branch is always the latest GA version
+of MaxScale.
+
+The source code is available [here](https://github.com/mariadb-corporation/MaxScale).

test/docker-compose.yml

@@ -6,6 +6,7 @@ services:
         container_name: server1
         environment:
             MYSQL_ALLOW_EMPTY_PASSWORD: Y
+            MYSQL_INITDB_SKIP_TZINFO: Y
         volumes:
             - ./sql/master:/docker-entrypoint-initdb.d
         command: mysqld --log-bin=binlog --binlog-format=ROW --server-id=3000 --port=3000 --log-slave-updates
@@ -16,6 +17,7 @@ services:
         network_mode: "host"
         environment:
             MYSQL_ALLOW_EMPTY_PASSWORD: Y
+            MYSQL_INITDB_SKIP_TZINFO: Y
         volumes:
             - ./sql/slave:/docker-entrypoint-initdb.d
         command: mysqld --log-bin=binlog --binlog-format=ROW --server-id=3001 --port=3001 --log-slave-updates
@@ -26,6 +28,7 @@ services:
         network_mode: "host"
         environment:
             MYSQL_ALLOW_EMPTY_PASSWORD: Y
+            MYSQL_INITDB_SKIP_TZINFO: Y
         volumes:
             - ./sql/slave:/docker-entrypoint-initdb.d
         command: mysqld --log-bin=binlog --binlog-format=ROW --server-id=3002 --port=3002 --log-slave-updates
@@ -36,6 +39,7 @@ services:
         network_mode: "host"
         environment:
             MYSQL_ALLOW_EMPTY_PASSWORD: Y
+            MYSQL_INITDB_SKIP_TZINFO: Y
         volumes:
             - ./sql/slave:/docker-entrypoint-initdb.d
         command: mysqld --log-bin=binlog --binlog-format=ROW --server-id=3003 --port=3003 --log-slave-updates