Dear MySQL users,
MySQL Server 8.0.15, a new version of the popular Open Source
Database Management System, has been released. MySQL 8.0.15 is
recommended for use on production systems.
For an overview of what's new in MySQL 8.0, please see
http://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html
For information on installing MySQL 8.0.15 on new servers, please see
the MySQL installation documentation at
http://dev.mysql.com/doc/refman/8.0/en/installing.html
MySQL Server 8.0.15 is available in source and binary form for a number of
platforms from our download pages at
http://dev.mysql.com/downloads/mysql/
MySQL Server 8.0.15 is also available from our repository for Linux
platforms, go here for details:
http://dev.mysql.com/downloads/repo/
Windows packages are available via the Installer for Windows:
http://dev.mysql.com/downloads/installer/
[At the time of this announcement, the 8.0.15 Installer has not yet
been uploaded but it will arrive within a few days]
along with .ZIP (no-install) packages for more advanced needs.
8.0.15 also comes with a web installer as an alternative to the full
installer.
The web installer doesn't come bundled with any actual products
and instead relies on download-on-demand to fetch only the
products you choose to install. This makes the initial download
much smaller but increases install time as the individual products
will need to be downloaded.
We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc.:
http://bugs.mysql.com/report.php
The following link lists the changes in the MySQL 8.0 since
the release of MySQL 8.0.14. It may also be viewed
online at
http://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-15.html
Enjoy!
Changes in MySQL 8.0.15 (2019-02-01, General Availability)
Bugs Fixed
* Group Replication was unable to function in the 8.0.14
release of MySQL Server if IPv6 support was disabled at
the operating system level, even if the replication group
did not use any IPv6 addresses. The issue is fixed by
this release of MySQL Server, 8.0.15. (Bug #29249542, Bug
#94004)