As this new MySQL bug shows, there is a difference between supported, and cutting edge.

Many Linux administrators treat their system as though having the latest version of a program is always the best. This is not always – and is usually never true for production environments.

Yes. I am advocating “If it ain’t broke, don’t fix it.”:

The whole concept of production is for stability; that’s why you never want to run your testing-grade code on a production system. If you have security issues, release, and test this in your testing environment BEFORE you use it live.

Today, they have finally rolled out a patch into MySQL 5.0.50, InnoDB was broken for sorting in descending order in 5.0.48. I can only imagine the chaos if all administrators utilized the same ‘Linux Upgrade Path.’