MySQL Lifecycle Policy
Database administrators hate to upgrade their databases. At MySQL, we like to think that we have been early to recognise this, and we have given more or less unlimited support to even very old releases, on a multitude of platforms. However, this has not been without cost to ourselves.
Many of our users know that the cost of maintaining several releases is high. We have thus been asked to clarify our support lifecycle policy. After long internal discussions, that were not always easy, we are now pleased to say that we have an explicit support lifecycle policy. It addresses the timeframes we will provide updates and continued support for current and older versions of the MySQL server.
Keeping older versions alive for a long time is appreciated by our community and our customers alike. However, we are no longer in a position to maintain our older versions without remuneration. This means that those wishing to enjoy MySQL’s support in their usage of MySQL 3.23 and MySQL 4.0 need to plan for their future, as our support of these releases will be limited to those covered by a MySQL Network subscription, starting in 1 Aug 2006 (for MySQL 3.23) and 1 Oct 2006 (for MySQL 4.0).
This means that we are no longer offering publicly available binary updates for our 3.23 and 4.0 releases. The sources of these will still be provided. We are also evaluating whether we will continue hosting archived versions of old binaries, as well as the timeline for the support of MySQL 4.1.
We hope the clarity offered by this explicit support lifecycle policy will give a good base to our Customers and Users alike, when planning for their future use of MySQL!
July 14th, 2006 at 5:10
[…] MySQL is arguably the most used open source database system. Now, MySQL has published its first “end of life” timetable for its databases (LifeCycle Policy), which would fundamentally cease free updates and support for older versions starting next month (August 2006). However, updates will still be made available for legacy systems for a premium. Customers using MySQL 3.23 and 4.0 will have to buy a Network Subscription to receive binary updates after August 1st, 2006 and October 1st, 2006, respectively. Users can get a basic subscription for almost $600 USD annually. “Keeping older versions alive for a long time is appreciated by our community and our customers alike. However, we are no longer in a position to maintain our older versions without remuneration,” said Kaj Arnö, MySQL’s Vice President of Community Relations. ShareThese icons link to social bookmarking sites where readers can share and discover new web pages. […]
July 18th, 2006 at 22:13
[…] Keeping support going for older versions of software while developing new versions proves costly over time. Kaj Arnö, VP Community for MySQL AB, blogged about the company’s clarification of end of life dates for MySQL, and why they have made this difficult choice: […]
October 7th, 2006 at 21:43
[…] Kaj Arnö’s blog » Blog Archive » MySQL Lifecycle Policy This means that we are no longer offering publicly available binary updates for our 3.23 and 4.0 releases. The sources of these will still be provided. We are also evaluating whether we will continue hosting archived versions of old binaries, as well as the timeline for the support of MySQL 4.1. mysql […]
December 21st, 2006 at 5:35
mysql hosting
I am all for it. I wonder how many folks actually use these. I built a small store that grew into over 100 thousands items. Its crazy how fast it grows!. Anyway. I agree!