MySQL 5.1 was in RC stage for around 10 months now finally planned to be released as GA soon. As Monty Says MySQL 5.1.26 will be renamed as GA if no serious bugs are discovered.
Lets help MySQL to ensure GA release will be indeed GA quality and support Monty in his call to ensure this RC candidate works well for you.
If you know about any bugs in MySQL 5.1 or MySQL 5.0 (which are still unfixed in MySQL 5.1) make sure to report them on bugs.mysql.com. If there are some bugs already reported but still not fixed as of MySQL 5.1.26 make sure to post a comment to let MySQL know the bug is affecting you as well. The scream factor is important for bug fix prioritization so if you can make a story of your suffering because of the bug to slashdot you should be quite good.
If you’re the customer – make sure you put that note in your bug report. Bug reports from customers should be treated more seriously so make sure you use this advantage. And if you’re not a customer I guess one of your friends is so you can ask them to vote for a bug for you.
It also helps to be descriptive to explain why exactly this bug is important. Many MySQL developers are isolated to the customer so they may not quite understand how often bug circumstances happen and how bad are consequences.
It is surely helps to have repeatable bug reports but make sure to report bug even if you do not have one. If significant number of people are reporting similar issue it shows some problem exists, even if they can’t exactly pinpoint it. It helps MySQL with bug hunting and what is even more important it helps other users which know they are not alone and can find a workaround assuming fix does not exist.
In general I’m quite happy to see MySQL 5.1 is reaching GA stage and I think it is already better than Quality Disaster MySQL 5.0 initial release have been. Though I still think it is not quite where yet when it comes to Quality. Error rate with 5.1 we’ve seen among the customers during last few months was higher than with 5.0, also Scalability of MySQL 5.1 is often subpar compared to MySQL 5.0 possibly due to this bug which is not fixed up to now (not in 5.1.26 at least)
Percona’s widely read Percona Data Performance blog highlights our expertise in enterprise-class software, support, consulting and managed services solutions for both MySQL® and MongoDB® across traditional and cloud-based platforms. The decades of experience represented by our consultants is found daily in numerous and relevant blog posts.
Besides specific database help, the blog also provides notices on upcoming events and webinars.
Want to get weekly updates listing the latest blog posts? Subscribe to our blog now! Submit your email address below.