From d8cbdae83d2c4e30a2ddb0f078b2ba1dfa679064 Mon Sep 17 00:00:00 2001 From: Johan Wikman Date: Tue, 25 Jun 2019 11:44:59 +0300 Subject: [PATCH] Remove 2.2 release notes from 2.3 branch By convention, we only retain the release notes for the current branch. --- .../MaxScale-2.2.17-Release-Notes.md | 38 ----------------- .../MaxScale-2.2.18-Release-Notes.md | 37 ----------------- .../MaxScale-2.2.19-Release-Notes.md | 39 ------------------ .../MaxScale-2.2.20-Release-Notes.md | 40 ------------------ .../MaxScale-2.2.21-Release-Notes.md | 41 ------------------- 5 files changed, 195 deletions(-) delete mode 100644 Documentation/Release-Notes/MaxScale-2.2.17-Release-Notes.md delete mode 100644 Documentation/Release-Notes/MaxScale-2.2.18-Release-Notes.md delete mode 100644 Documentation/Release-Notes/MaxScale-2.2.19-Release-Notes.md delete mode 100644 Documentation/Release-Notes/MaxScale-2.2.20-Release-Notes.md delete mode 100644 Documentation/Release-Notes/MaxScale-2.2.21-Release-Notes.md diff --git a/Documentation/Release-Notes/MaxScale-2.2.17-Release-Notes.md b/Documentation/Release-Notes/MaxScale-2.2.17-Release-Notes.md deleted file mode 100644 index 5081c3429..000000000 --- a/Documentation/Release-Notes/MaxScale-2.2.17-Release-Notes.md +++ /dev/null @@ -1,38 +0,0 @@ -# MariaDB MaxScale 2.2.17 Release Notes -- 2018-11-28 - -Release 2.2.17 is a GA release. - -This document describes the changes in release 2.2.17, 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-2175](https://jira.mariadb.org/browse/MXS-2175) available_when_donor=true is not respected in Galera Monitor with xtrabackup-v2 sst method and only one synced node available in the cluster -* [MXS-2159](https://jira.mariadb.org/browse/MXS-2159) Oracle Connector/J 8.0 with SSL doesn't work with MaxScale -* [MXS-2151](https://jira.mariadb.org/browse/MXS-2151) MaxScale does not log any info when "Connection killed by MaxScale: Router could not recover from connection errors" -* [MXS-2106](https://jira.mariadb.org/browse/MXS-2106) Maxscale CDC JSON output does not respect null values -* [MXS-2095](https://jira.mariadb.org/browse/MXS-2095) Fatal: MaxScale 2.2.15 received fatal signal 11 - libavrorouter.so(count_columns+0x21) -* [MXS-2081](https://jira.mariadb.org/browse/MXS-2081) Unable to execute maxctrl commands in RHEL 6 - Maxscale 2.2.9 - -## 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-tx/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). diff --git a/Documentation/Release-Notes/MaxScale-2.2.18-Release-Notes.md b/Documentation/Release-Notes/MaxScale-2.2.18-Release-Notes.md deleted file mode 100644 index d20cfab6f..000000000 --- a/Documentation/Release-Notes/MaxScale-2.2.18-Release-Notes.md +++ /dev/null @@ -1,37 +0,0 @@ -# MariaDB MaxScale 2.2.18 Release Notes -- 2018-12-13 - -Release 2.2.18 is a GA release. - -This document describes the changes in release 2.2.18, 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-2221](https://jira.mariadb.org/browse/MXS-2221) Fatal signal handling does not always create a core -* [MXS-2216](https://jira.mariadb.org/browse/MXS-2216) Read past stack buffer -* [MXS-2213](https://jira.mariadb.org/browse/MXS-2213) Growing memory consumption with 2.2.17 -* [MXS-2207](https://jira.mariadb.org/browse/MXS-2207) qc_mysqlembedded does not classify SET STATEMENT ... FOR UPDATE correctly. -* [MXS-2183](https://jira.mariadb.org/browse/MXS-2183) Excessive memory use, but not growing endlessly - -## 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-tx/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). diff --git a/Documentation/Release-Notes/MaxScale-2.2.19-Release-Notes.md b/Documentation/Release-Notes/MaxScale-2.2.19-Release-Notes.md deleted file mode 100644 index 8ff6492e8..000000000 --- a/Documentation/Release-Notes/MaxScale-2.2.19-Release-Notes.md +++ /dev/null @@ -1,39 +0,0 @@ -# MariaDB MaxScale 2.2.19 Release Notes -- 2019-01-11 - -Release 2.2.19 is a GA release. - -This document describes the changes in release 2.2.19, 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-2248](https://jira.mariadb.org/browse/MXS-2248) INSERT sent to all nodes -* [MXS-2242](https://jira.mariadb.org/browse/MXS-2242) MaxScale does not recognize builtin read-only functions -* [MXS-2238](https://jira.mariadb.org/browse/MXS-2238) MaxScale fails to send large CDC schemas -* [MXS-2234](https://jira.mariadb.org/browse/MXS-2234) Add extra info to log when MaxScale loads persisted configuration files -* [MXS-2232](https://jira.mariadb.org/browse/MXS-2232) version_string prefix 5.5.5- is always added -* [MXS-2231](https://jira.mariadb.org/browse/MXS-2231) Kerberos together with ssl doesn't work -* [MXS-2048](https://jira.mariadb.org/browse/MXS-2048) Rewrite dbfwfilter module command documentation - -## 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-tx/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). diff --git a/Documentation/Release-Notes/MaxScale-2.2.20-Release-Notes.md b/Documentation/Release-Notes/MaxScale-2.2.20-Release-Notes.md deleted file mode 100644 index 9c0340924..000000000 --- a/Documentation/Release-Notes/MaxScale-2.2.20-Release-Notes.md +++ /dev/null @@ -1,40 +0,0 @@ -# MariaDB MaxScale 2.2.20 Release Notes -- 2019-03-15 - -Release 2.2.20 is a GA release. - -This document describes the changes in release 2.2.20, 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-2375](https://jira.mariadb.org/browse/MXS-2375) maxctrl stop maxscale is confusing -* [MXS-2368](https://jira.mariadb.org/browse/MXS-2368) maxctrl requires password on command line and cannot change user password -* [MXS-2335](https://jira.mariadb.org/browse/MXS-2335) lower_case_table_names doesn't work -* [MXS-2322](https://jira.mariadb.org/browse/MXS-2322) Null characters in passwords break maxctrl -* [MXS-2311](https://jira.mariadb.org/browse/MXS-2311) connection_keepalive and error : (4852) Unexpected internal state: received response 0x00 from server -* [MXS-2296](https://jira.mariadb.org/browse/MXS-2296) maxscale-system-test does not generate core dumps -* [MXS-2268](https://jira.mariadb.org/browse/MXS-2268) readwritesplitter is not routing queries properly in Maxscale 2.3.2 -* [MXS-2206](https://jira.mariadb.org/browse/MXS-2206) Cmake version check fails with version = 3.10.2 - -## 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-tx/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). diff --git a/Documentation/Release-Notes/MaxScale-2.2.21-Release-Notes.md b/Documentation/Release-Notes/MaxScale-2.2.21-Release-Notes.md deleted file mode 100644 index 6a074ea88..000000000 --- a/Documentation/Release-Notes/MaxScale-2.2.21-Release-Notes.md +++ /dev/null @@ -1,41 +0,0 @@ -# MariaDB MaxScale 2.2.21 Release Notes -- 2019-05-08 - -Release 2.2.21 is a GA release. - -This document describes the changes in release 2.2.21, 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-2410](https://jira.mariadb.org/browse/MXS-2410) Hangup delivered to wrong DCB -* [MXS-2366](https://jira.mariadb.org/browse/MXS-2366) Wrong tarball RPATH - -## Changes to MariaDB-Monitor failover - -Failover is no longer disabled permanently if it or any other cluster operation fails. -The disabling is now only temporary and lasts for 'failcount' monitor iterations. Check -[MariaDB-Monitor documentation](../Monitors/MariaDB-Monitor.md#limitations-and-requirements) -for more information. - -## 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-tx/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).