hcq/MaxScale
hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge branch '2.3' into 2.4

Browse Source
This commit is contained in:
Johan Wikman 2020-04-27 15:54:24 +03:00
commit 9106392c12
3 changed files with 1 additions and 79 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
Documentation/Release-Notes/MaxScale-2.3.18-Release-Notes.md
View File

@ -1,40 +0,0 @@
# MariaDB MaxScale 2.3.18 Release Notes -- 2020-03-11
Release 2.3.18 is a GA release.
This document describes the changes in release 2.3.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-2917](https://jira.mariadb.org/browse/MXS-2917) qc_sqlite leaks memory with complex CREATE TABLE query
* [MXS-2899](https://jira.mariadb.org/browse/MXS-2899) Server charset set to latin1 on retrieval query failure
* [MXS-2896](https://jira.mariadb.org/browse/MXS-2896) Server wrongly in Running state after failure to connect
* [MXS-2894](https://jira.mariadb.org/browse/MXS-2894) Fails to download avro tar file
* [MXS-2883](https://jira.mariadb.org/browse/MXS-2883) session closed by maxscale when it received "auth switch request" packet from backend server
* [MXS-2832](https://jira.mariadb.org/browse/MXS-2832) Failover timing estimates are not documented
* [MXS-2810](https://jira.mariadb.org/browse/MXS-2810) maxscale process still running after uninstalling maxscale package
* [MXS-2277](https://jira.mariadb.org/browse/MXS-2277) Calling MaxAdmin/MaxCtrl in a monitor event script can cause a deadlock
## 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).

38
Documentation/Release-Notes/MaxScale-2.3.19-Release-Notes.md
View File

@ -1,38 +0,0 @@
# MariaDB MaxScale 2.3.19 Release Notes
Release 2.3.19 is a GA release.
This document describes the changes in release 2.3.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-2969](https://jira.mariadb.org/browse/MXS-2969) maxscale service still not stopped / restarted on package upgrade
* [MXS-2956](https://jira.mariadb.org/browse/MXS-2956) admin_ssl_ca_cert reads the wrong certificate
* [MXS-2954](https://jira.mariadb.org/browse/MXS-2954) cluster sync doesn't update global configuration options
* [MXS-2948](https://jira.mariadb.org/browse/MXS-2948) Fix cluster sync
* [MXS-2942](https://jira.mariadb.org/browse/MXS-2942) DELETE of a monitor doesn't check whether it uses servers
* [MXS-2931](https://jira.mariadb.org/browse/MXS-2931) MXS-2810 still unfixed in RHEL / CentOS 6 packages
## 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).

2
VERSION23.cmake
View File

@ -5,7 +5,7 @@
set(MAXSCALE_VERSION_MAJOR "2" CACHE STRING "Major version")
set(MAXSCALE_VERSION_MINOR "3" CACHE STRING "Minor version")
set(MAXSCALE_VERSION_PATCH "19" CACHE STRING "Patch version")
set(MAXSCALE_VERSION_PATCH "20" CACHE STRING "Patch version")
# This should only be incremented if a package is rebuilt
set(MAXSCALE_BUILD_NUMBER 1 CACHE STRING "Release number")