Developers criticize Oracle's handling of MySQL
In recent days, some developers complained from the MySQL community about Oracle's handling of the free relational database. So criticized the MariaDB developers Sergei Golubchik missing test cases for the recent released version 5.5.27.
The release notes did lead to numerous bug fixes in the directory mysql-test/suite would find, however, no tests that could be explored, the bugs. Indeed there are, for example, no tests for the bugs fixed in version 5.5.27 error 61579 and 60926 found. Golubchik points out that now in one of the scripts directory internal / mysql-test shows up as a test repository, it is not included in the source code. His ten days ago asked the internal MySQL mailing list to question whether this is a new procedure or an oversight, Oracle has not yet been answered.
"[...] In MySQL AB and later at Sun had any correction must always be accompanied by a test case for the bug. Since the tests [...] always ran on multiple platforms, we were reasonably certain that once fixed bugs was removed forever, "Golubchik justified the need for testing. He could not imagine that Oracle did not comply with this rule. Consequently, it would have to go with the changes to something else.
Other developers complain that a bug was originally publicly available now as "private" declared without Oracle justifying the decision. This error may have even cause the server to crash and had been resolved. However, the release notes contained no evidence.
Stewart Smith, at Percona Director responsible for the development has, in his blog points out that the funds available in Launchpad MySQL BZR trees from the published sources from Oracle now lagging behind. Thus, there exists there instead of the younger version 5.1.65 or 5.1.63, and the BZR version of the 5.6 development branch is not up to date: "5.6.6-m9 was published, but the BCR-Tree is still somewhere on MySQL 5.6.5 ".
Mark Callaghan summarizes the phenomena under the heading "(less) open source" together: "MySQL is improving much more difficult, if tests are missing and BZR will no longer be updated My teams at Google and Facebook have MySQL done much better I wish.. we would not have to deal with such problems that slow us down unnecessarily. " Callaghan was instrumental in accelerating the InnoDB plug-ins for MySQL and has developed at Google performance improvements for MySQL. He is now the MySQL team at Facebook.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment