MySQL 5.1 continues community release madness
By Osma on Tuesday 2 December 2008, 11:35 - Permalink
So MySQL 5.1 is declared GA, contains enough bugs to make Monty rail against it publically, doesn't (as far as I've been able to gather) have a stable cross-release pluggable storage engine ABI (despite that being a major release feature -- meaning you have to have new plugin releases for each MySQL server release before upgrading anything), and continues the madness of less frequent community releases and less stable enterprise releases against the wishes of every sensible enterprise customer and (I would guess) every community member.
I know enough about running MySQL to know that Monty's comments don't necessarily reflect much on the practicalities of someone trying to run something using MySQL rather than developing it, but the rest of the noise about this release definitely makes me want to seriously reconsider a policy of using MySQL Enterprise version and look at a real community-released version instead for production use.. There's just a "small" question of figuring out which community..
Comments
before talking about stable ABI and API for storage engine plugins, they should think a bit about decoupling a shared library from the mysqld executable. That shared library cannot be used without loading mysqld seems nonsense.
Yes. A REALLY good way to get MySQL to stop doing this is to stop buying their Enterprise product.
I don't understand the logic really.
Why would I want to use a product that has *less* QA?