MariaDB51 release plan
From Askmonty.org
Contributing | MCA | Contributions | Release Process | Release Criteria | Plans | Tools | Replication
Contents |
5.1 release plan
(Please move completed items to MariaDB_versus_MySQL also please consider creating a stub documentation page and adding it to the MariaDB 5.1 Reference Manual (see Help:Adding Pages to Categories for help with this.)).
ToDo list for MariaDB 5.1.42-rc release
- After code is done, follow release process: ReleaseProcess
ToDo list for MariaDB 5.1 final release
Currently tasks are filed as bugs in Launchpad. Please use tag "5.1" for anything that must be fixed before 5.1 final release.
Buildbot failures
Tests that fail sporadically (only sometimes)
- pbxt.status result file difference: failure history. Seems like there is a fix for the similar problem in main.status (BUG#29971), however the fix looks slightly suspicious and may need checking. It disables logging to table, but comments at the top of the test says that --log-output must include 'tables' for the test to work ...
General problems in Buildbot that have not yet been fully analysed
- Fix any failures in
mysql-test-run.pl --valgrind --suite=pbxt(not run in buildbot currently), so we can enable the pbxt suite by default. - Windows: lots of test failures.
- Win32: perror-win.test - testsuite problem on non-English windows
- Win32: binlog_index.test only on SergeyP's machine, not on Igor's, not on Bo's) (occurs on mainline also, reported as BUG#47751) (because of that, not considered to be as stopper)
- pbxt.multi_update may time out on slow Windows machines
- Windows: problems getting a host to run stable. I think we need a virtual machine that is booted for every test run (two actually, 32 and 64 bit).
- Fix compiler warnings.
- Mac OSX: general problems getting the build slaves to run stable.
Other small bugs that are not Buildbot stuff per se, but might earn us bonus points in the community
- select() overrun failure: http://bugs.mysql.com/bug.php?id=48929 and http://www.mysqlperformanceblog.com/2009/11/20/rare-evil-mysql-bug/ (may not have to do anything as MySQL now has a reasonably-looking patch pending fix for this).
Features
- Virtual columns patch
- There is an open "SP mem_root memory overrun" problem which needs to be resolved before we can push. (Sanja) (atm waiting on MWL:53 work to finish)
- Compiling and packaging on 64-bit Windows (Sanja)
- MWL:53: Avoid flushing keycache to disk in case of DROPping table (Sanja)
- (According to Sanja) The WL entry itself is for 5.0. Will need non-dummy merge to 5.1
- Sanja is fixing Monty's review feedback (it is not clear yet whether the second review will be needed)
- libmysqld as shared library
- (what's needed there? only change Makefile.am-s? ) (Kristian)
Nice to have features
These things are nice to have but we won't wait/make extra effort to get them before release. The nature of the features makes it possible to fix it after GA.
- Sphinx storage engine
- Spider storage engine
- OQGraph storage engine
- New storage engines can be added safely after GA.
Binaries
- Windows binaries currently built manually by Sergey. Sanja working on getting 64-bit Windows binaries. Webyog to later provide Windows installer.
- Task list for what to do with binaries is ReleaseProcess.
Supported platforms
- Linux distributions as supported by OurDelta (Red Hat/CentOS, Debian, Ubuntu)
- Need also: Fedora, OpenSuse
- Windows, 32bit and 64 bit.
- Solaris, Sparc + Intel
- This may be postponed
- Toby from Open Query has Sparc box too.
- Jani and Kurt to look into Suse buildfarm
Testing
Document the deb/rpm build procedure.
- How to use OpenQuery's scripts (Hakan)
- Howto deb on Ubuntu (done)
- Howto rpm on CentOS (Hakan ongoing)
Test rpm, deb, msi upgrade: MySQL 5.1 -> MariaDB 5.1.
- Test before publishing packages for download.
- Testing Debian, CentOS (and further, SUSE) - Hakan
- Debian and Ubuntu tests for this are in Buildbot (but could do more extensive testing; currently only selects a single row from one existing table).
Test replication MySQL 5.1 -> MariaDB 5.1
- Reported to be working in Oscon
- Test whether mysqlsandbox can be uses to automated replication testing - Hakan
Do smoke test
- Test that install and start of packages work.
- Buildbot automates this for many platforms, but could do more extensive testing.
Other kind of tests (SergeyP)
- Basically, check that we're shipping the right files
- Compiled with optimizations
- But with debug symbols (in a separate file? check what mainline does) Bug reported
- Default DB does not have any redundant users, traces of a mysql-test-run run or anything like that. debian packaging fails to add debian-sys-maint user, otherwise ok
- SQL permissions are set to what users are used to finding in the new install
- Comparison of list of files in the archive against the contents of previous release (taking MySQL's list of files for first release) shows that
- nothing is missing mariadb binaries are missing, bug filed
- there is no extra garbage
- Check that we've compiled the right set of engines (e.g. didn't forget pbxt). This needs to be a separate check as statically linked engines do not have any files in the binary package. One can only check for their presence by starting the server and running SHOW ENGINES. PBXT, MARIA, XTRADB are present. FEDERATED compiled but missing?
- Check if Maria is used for temporary tables YES
- Check that SELECT VERSION() produces what we expect it to. 5.1.38-maria-beta-ourdelta81-log
- Linking. I recall there were some issues with linking static vs linking against some particular versions of glibc, zlib, etc. Need to check we're linking it the right way.
Further testing
- Install MariaDB, when attempt to install an existing application and see if will install and be able to make use of MariaDB instead of MySQL
- Install MariaDB, then try to compile a program that links against the MySQL Client API.
TODO: Document what QA happens now (Buildbot). A link is fine.
- Develop plan of enhancing test suite for the future (random, stress test).
Docs and Release Notes
Daniel is in charge of Release Notes.
The Release Notes are written on the wiki: MariaDB_versus_MySQL#DRAFT_MariaDB_5.1_Release_Notes
MariaDB 5.1 Reference Manual - Manual:Contents
XtraDB incompatible with InnoDB if compression enabled.
There needs to be a "stub" manual / documentation for anything we've done new.
- Is there an XtraDB manual?
General release criteria
- Recommended Beta release == "Please test this"
- RC == We believe this could be the GA.
- GA == No serious bugs found in RC.
- Exception for known MySQL 5.1 bugs, we will check wether Sun will possibly be working on them . (MariaDB is still at least as good as MySQL.)
Web properties
MariaDB.com
- First version is simple
- Owned by Alliance, non-commercial
- links to commercial sites
- downloads on current askmonty.org page (link from mariadb.com)
- mirrors?
