4 ms·
This test-case controversy was both discovered and ginned up by Monty and the MariaDB folks, who have much to gain by the rejection of Oracle's brand of MySQL a
by spudlyo 14y ago
This test-case controversy was both discovered and ginned up by Monty and the MariaDB folks, who have much to gain by the rejection of Oracle's brand of MySQL and the promotion of MariaDB. While it may be part of some larger and sinister plan to "kill" open source MySQL as the article suggests, it seems more likely to me that it was simply a mistake, and one they'll walk back at some point.
If it is an anti-competitive move, it reminds me of the recent move by RedHat, who have started shipping their new kernels as one big source tarball, without patches, which undoubtedly pissed off both Oracle and the CentOS folks.
- jeffdavis 14y ago"it seems more likely to me that it was simply a mistake, and one they'll walk back at some point." How do you explain removing access to the source repository then? Or the fact that the documentation is not free to redistribute?
- spudlyo 14y agoHow do you explain removing access to the source repository then? I can easily explain it, because it never happened. Access to the MySQL source repository on launchpad is available for anyone to browse. Oracle is occasionally lazy about updating it, but they've never removed access AFAIK. Or the fact that the documentation is not free to redistribute? The documentation has never been free to redistribute, it was that way under Monty, it was that way under Sun, and it remains that way under Oracle.
- army 14y agoFrom what I've heard withholding test cases is actually official Oracle policy, unlike, for example, the lack of updates to the launchpad repository. There wasn't any deliberate attempt to without commit history from launchpad - they were just slow in updating it.
- ibotty 14y agoit does not matter to simple rhel rebuilds like centos or scientific linux. it is unfortunate for the linux stable kernel maintainers. that's for sure though. it is very different from this case. that it's a simple mistake is not very probable. see the java sec update controversy a few days ago.