summaryrefslogtreecommitdiff
path: root/KNOWN_BUGS.txt
diff options
context:
space:
mode:
authorMonty <monty@mariadb.org>2018-11-07 13:16:29 +0200
committerMonty <monty@mariadb.org>2018-12-09 20:49:05 +0200
commitc82855d88272f0a1b95d0ad2b7abf804aeff8145 (patch)
treed21118e6caaf2f90e2df0a4a2780d7964caa349e /KNOWN_BUGS.txt
parentae58cd6b87bf1f872093816691ebdd46bef50c7f (diff)
downloadmariadb-git-c82855d88272f0a1b95d0ad2b7abf804aeff8145.tar.gz
Changed some MySQL names in messages to MariaDB
- Remove obsolete documentation files - Removed old obsolete information from some documentation files
Diffstat (limited to 'KNOWN_BUGS.txt')
-rw-r--r--KNOWN_BUGS.txt38
1 files changed, 9 insertions, 29 deletions
diff --git a/KNOWN_BUGS.txt b/KNOWN_BUGS.txt
index 56c9102b0cd..af65c98590d 100644
--- a/KNOWN_BUGS.txt
+++ b/KNOWN_BUGS.txt
@@ -1,35 +1,15 @@
-This file should contain all known fatal bugs in Mariadb and the Aria
-storage engine for the last source or binary release. Minor bugs,
-extensions and feature requests, and bugs found since this release can
-be found in the MariaDB bugs database at: http://mariadb.org/jira and
-in the MySQL bugs databases at: http://bugs.mysql.com/ (category
-"Maria storage engine").
+This file should contain all known fatal bugs in MariaDB for the last
+source or binary release. Minor bugs, extensions and feature requests,
+and bugs found since this release can be found in the MariaDB bugs
+database at: https://jira.mariadb.org
There should not normally be any bugs which affect normal operations
in any MariaDB release. Still, there are always exceptions and edge
cases and that is what this file is for.
-If you have found a bug that is not listed here, please add it to
-http://mariadb.org/jira so we can either fix it for next release or in
-the worst case add it here for others to know!
+If you have find bug please add it to https://jira.mariadb.org so
+that we are can try to fix it for the next release. You can also add
+feature request to the JIRA.
-
-IMPORTANT:
-
-If you have been using the Maria (now Aria) storage engine with the
-MySQL-5.1-Maria-alpha build and are upgrading to a newer MariaDB you
-MUST run [m]aria_chk --recover on all your Aria tables. This is because
-we made an incompatible change with how the transaction id is stored
-and old transaction id's must be reset!
-
-cd mysql-data-directory
-aria_chk --recover */*.MAI
-
-Going forward, we will do our best to not introduce any incompatible
-changes in the data format for Aria tables. If this would be ever be
-needed, we will, if possible, support both the old and the new version
-to make upgrades as easy as possible.
-
-Note that for the MariaDB 5.1 release the Aria storage engine is
-classified as 'beta'; It should work, but use it with caution. Please
-report all bugs to http://mariadb.org/jira so we can fix them!
+The latest documentation for the MariaDB server can be found at:
+https://mariadb.com/kb