[Maria-developers] Information for release notes
Hi Daniel, Here is a rough changelog written from reading through bzr history. I took a dump of every commit in MariaDB that is not in MySQL 5.1.38, and wrote this summary of the changes. I don't have sufficient knowledge to parse through all of the Maria changes from before MariaDB started. Instead I wrote a generic entry for the Maria storage engine, and also added entries for what is already written (by Monty I think) on http://askmonty.org/wiki/index.php/MariaDB_versus_MySQL So this is probably the best shot we have at a complete list of relevant differences between MySQL and MariaDB. Do let me know if anyone finds anything missing or any errors. Daniel, I hope you can use this as the basis for the release notes. Maybe this list will also be useful for you to fill out the Manual on the Wiki. I am thinking you could check that all new features are documented, and add pages for those that are not. If not trivial, you could just make a stub page and ask on maria-developers@ for someone to fill them out? - Kristian. ----------------------------------------------------------------------- Generally: MariaDB-5.1.38-beta1 is based on MySQL-5.1.38, but has these additional features and bug fixes. Feature: mysql-test-run now has options --stop-file and --stop-keep-alive (also accessible with environment variables MTR_STOP_FILE and MTR_STOP_KEEP_ALIVE). With these, it is possible to pause a running test temporarily and let it continue later. Bug fix: mysqlslap: setting --engine does not get replicated http://bugs.mysql.com/bug.php?id=46967 mysqlslap: specifying --engine and --create does not work with --engine=<storage_engine>:<option> https://bugs.launchpad.net/maria/+bug/429773 Feature: Improvements to Gcov support in testing. Feature: New column TIME_MS in SHOW FULL PROCESSLIST and INFORMATION_SCHEMA.PROCESSLIST, similar to the old TIME column, but with microsecond resolution. Also fixes old TIME column to not be influenced by @TIMESTAMP. Patch by Percona. Bug fix: rpl_do_grant fails on PB-2 with a failing connect http://bugs.mysql.com/bug.php?id=47016 Bug fix: Windows: mysql-test-run --log-error fixed to not add --console. Bug fix: The myisam_crash_before_flush_keys test fails on Windows http://bugs.mysql.com/bug.php?id=47455 Bug fix: rpl.rpl_get_master_version_and_clock fails on hpux11.31 http://bugs.mysql.com/bug.php?id=46931 Bug fix: safe_process: FATAL ERROR, Unknown option: --nocore http://bugs.mysql.com/bug.php?id=46212 Feature: Optimizer improvement: Table elimination. http://askmonty.org/worklog/Server-Sprint/?tid=17 Bug fix: XtraDB crashes on startup on windows https://bugs.launchpad.net/maria/+bug/417751 Bug fix: Eliminate compiler warnings. Bug fix: Fix parsing of enum-valued options for plugins. https://bugs.launchpad.net/maria/+bug/423035 Feature: Enhancements to slow log. Includes details of execution plan and microsecond-precision resolution. Based on microslow patch by Percona. Feature: PBXT storage engine. PBXT is developed by PrimeBase Technologies, http://www.primebase.org/ Bug fix: Solaris build fixes. Feature: XtraDB storage engine as a replacement for the MySQL built-in InnoDB. XtraDB is based on the Oracle/Innobase InnoDB plugin version 1.0.3, with enhancements. XtraDB is developed by Percona. Feature: Performance improvements for common cases of character set conversion. Feature: Pool-of-threads, allowing to map a high number of simultaneous connections onto a lower number of operating system treads, to reduce overhead with using large number of threads. Feature: New handler call prepare_index_scan() and other small improvements to the internal storage engine handler API. Bug fix: query_cache_debug.test fails http://bugs.mysql.com/bug.php?id=45632 Bug fix: enum-style command-line options are not honoured (maria.maria-recover fails) http://bugs.mysql.com/bug.php?id=41010 Bug fix: mysql-test-run sometimes terminated mysqld early, causing loss of memory leak error reports from Valgrind and GCov test coverage output. http://bugs.mysql.com/bug.php?id=43418 Bug fix: Several Valgrind reported bugs in the source code fixed. Bug fix: Save SAFE_MUTEX configure #define in config.h, to facilitate correct build options for plugins. Feature: ./configure now outputs a summary section at the end of the output. (By C.J. Adams-Collier). Bug fix: test maria.maria fails if server built without '--with-partition' https://bugs.launchpad.net/maria/+bug/330611 Feature: NDB storage engine disabled in MariaDB builds. (NDB is not supported in MariaDB). Feature: Added --abort-source-on-error to the mysql client. Feature: Faster CHECKSUM TABLE. Feature: Debugging code to check for taking mutexes in the wrong order, which enables to catch potential deadlocks in the server code. Feature: Maria storage engine. The Maria storage engine is an enhanment over the MyISAM storage engine which provides journaling and crash recovery.
On Thu, Sep 24, 2009 at 4:19 PM, Kristian Nielsen <knielsen@knielsen-hq.org> wrote:
Hi Daniel,
Here is a rough changelog written from reading through bzr history.
I took a dump of every commit in MariaDB that is not in MySQL 5.1.38, and wrote this summary of the changes.
I don't have sufficient knowledge to parse through all of the Maria changes from before MariaDB started. Instead I wrote a generic entry for the Maria storage engine, and also added entries for what is already written (by Monty I think) on http://askmonty.org/wiki/index.php/MariaDB_versus_MySQL
So this is probably the best shot we have at a complete list of relevant differences between MySQL and MariaDB. Do let me know if anyone finds anything missing or any errors.
Daniel, I hope you can use this as the basis for the release notes.
Maybe this list will also be useful for you to fill out the Manual on the Wiki. I am thinking you could check that all new features are documented, and add pages for those that are not. If not trivial, you could just make a stub page and ask on maria-developers@ for someone to fill them out?
Could the list itself be a basis for a changelog document and then we make release notes into a more human readable document? I thought that was your intention yesterday on IRC? henrik -- email: henrik.ingo@avoinelama.fi tel: +358-40-5697354 www: www.avoinelama.fi/~hingo book: www.openlife.cc
Also posting this message to maria-discuss for those that might be interested in the changelog, but are not subscribed to maria-developers. On Thu, 24 Sep 2009 15:19:19 +0200, Kristian Nielsen <knielsen@knielsen-hq.org> wrote: Kristian> Hi Daniel, Kristian> Kristian> Here is a rough changelog written from reading through bzr Kristian> history. Kristian> Kristian> I took a dump of every commit in MariaDB that is not in MySQL Kristian> 5.1.38, and wrote this summary of the changes. Kristian> Kristian> I don't have sufficient knowledge to parse through all of the Kristian> Maria changes from before MariaDB started. Instead I wrote a Kristian> generic entry for the Maria storage engine, and also added Kristian> entries for what is already written (by Monty I think) on Kristian> http://askmonty.org/wiki/index.php/MariaDB_versus_MySQL Kristian> Kristian> So this is probably the best shot we have at a complete list Kristian> of relevant differences between MySQL and MariaDB. Do let me Kristian> know if anyone finds anything missing or any errors. Kristian> Kristian> Daniel, I hope you can use this as the basis for the release Kristian> notes. This list helps a lot. Thanks! Using the contents of the list, I have created a Changelog page on the wiki: http://askmonty.org/wiki/index.php/Manual:MariaDB_5.1_Changelog I organized the page into two sections: Features, and Bug Fixes. I also added links to the pages in the manual which exist for the changelog entries refer to. Kristian> Maybe this list will also be useful for you to fill out the Kristian> Manual on the Wiki. I am thinking you could check that all Kristian> new features are documented, and add pages for those that are Kristian> not. If not trivial, you could just make a stub page and ask Kristian> on maria-developers@ for someone to fill them out? Stub pages for the manual are easy to create: 1. add a link to the new page to http://askmonty.org/wiki/index.php/Manual:Contents 2. click on the new link 3. enter the following text into the new page: {{stub}} 4. save the new stub page To get things going, I created the following new stub pages for the manual: http://askmonty.org/wiki/index.php/Manual:Mysql_client_--abort-source-on-err... http://askmonty.org/wiki/index.php/Manual:XtraDB_storage_engine http://askmonty.org/wiki/index.php/Manual:Character_Set_Conversion_performan... http://askmonty.org/wiki/index.php/Manual:CHECKSUM_TABLE_performance Other stubs may need to be created, but I don't know which of the remaining topics need documentation or not. For example, does the entry about MariaDB NOT supporting NDB need it's own Manual page or not? Any contributions to the above stubs are *very* welcome. Any contributions to any of the other refman pages are likewise welcome: http://askmonty.org/wiki/index.php/Manual:Contents Henrik> Could the list itself be a basis for a changelog document and Henrik> then we make release notes into a more human readable document? Henrik> I thought that was your intention yesterday on IRC? The changelog page is a good compliment to the release notes page. The changelog is brief and is presented as a series of bullet points. The release notes page is longer with items presented as paragraphs in a more readable way. Thanks. -- Daniel Bartholomew
Hi Daniel On 27/09/2009, at 2:24 PM, Daniel Bartholomew wrote:
Using the contents of the list, I have created a Changelog page on the wiki:
http://askmonty.org/wiki/index.php/Manual:MariaDB_5.1_Changelog
I organized the page into two sections: Features, and Bug Fixes. I also added links to the pages in the manual which exist for the changelog entries refer to.
Fabs.
Stub pages for the manual are easy to create:
1. add a link to the new page to http://askmonty.org/wiki/index.php/Manual:Contents 2. click on the new link 3. enter the following text into the new page: {{stub}} 4. save the new stub page
To get things going, I created the following new stub pages for the manual:
http://askmonty.org/wiki/index.php/Manual:Mysql_client_--abort-source-on-err...
http://askmonty.org/wiki/index.php/Manual:XtraDB_storage_engine
http://askmonty.org/wiki/index.php/Manual:Character_Set_Conversion_performan...
http://askmonty.org/wiki/index.php/Manual:CHECKSUM_TABLE_performance
Other stubs may need to be created, but I don't know which of the remaining topics need documentation or not. For example, does the entry about MariaDB NOT supporting NDB need it's own Manual page or not?
I'd say just create, you can always change things over time - the MySQL manual evolved also with sections appearing, merging, splitting and also disappearing. The cool thing about the wiki is that you can easily redirect a deleted page to a relevant new one. Re NDB... the NDB in the source tree may not be production capable, but it's technically functional. Builds for Ubuntu tend to include NDB, and it actually works (I've used it in training classes). So that's already the real world. MariaDB may also consider a magic merge solution with the actual NDB 6.whatever tree, as mixed setups (NDB and other engines) are perfectly common and sensible in various deployment scenarios. You then need the up-to date InnoDB stuff and binlog/replication fixes, as well as the server-side NDB infrastructure with enhancements and bugfixes. In short, a merge - at least that's what I can tell, someone please correct me if I'm wrong. I appreciate it might be a difficult thing to do.
Any contributions to the above stubs are *very* welcome. Any contributions to any of the other refman pages are likewise welcome:
http://askmonty.org/wiki/index.php/Manual:Contents
Henrik> Could the list itself be a basis for a changelog document and Henrik> then we make release notes into a more human readable document? Henrik> I thought that was your intention yesterday on IRC?
The changelog page is a good compliment to the release notes page. The changelog is brief and is presented as a series of bullet points. The release notes page is longer with items presented as paragraphs in a more readable way.
For this, think about what a user or support/DBA person needs: will upgrading to version N break anything? Any changes required or things to look out for? If you can organise the info in such a way that that's clear and easy (smart grouping, for starters), that'd be fab! Cheers, Arjen. -- Arjen Lentz, Exec.Director @ Open Query (http://openquery.com) Exceptional Services for MySQL at a fixed budget. Follow our blog at http://openquery.com/blog/ OurDelta: enhanced builds for MySQL @ http://ourdelta.org
participants (4)
-
Arjen Lentz -
Daniel Bartholomew -
Henrik Ingo -
Kristian Nielsen