It is a good idea to stick with the MySQL branch that you currently use in production. The only reasons I can see to do otherwise are 1) if you need a feature introduced in one of the newer development trees or 2) if your project is in its early stages and you want to avoid the hassle of upgrading later. There are several changes between 3.23.x and 4.0.x that could require you to modify/upgrade your MySQL-enabled apps. You can avoid most of them by keeping up with the change-log for the dev tree branch that comes after yours (4.0.x if you use 3.23.x, 4.1.x if you're using 4.0.x, etc.)and writing your apps with those changes in mind.
Personally, I have some production servers running 3.23.x and some running 4.0.x versions of MySQL. Neither version has given me a problem. There's my two cents. ;) -Rob -----Original Message----- From: Jeremy Zawodny [mailto:[EMAIL PROTECTED] Sent: Monday, September 15, 2003 2:08 PM To: Dan Anderson Cc: Paul DuBois; [EMAIL PROTECTED] Subject: Re: MySQL 3.23.58 has been released On Mon, Sep 15, 2003 at 01:48:36PM -0400, Dan Anderson wrote: > > There are 3.23, 4.0, 4.1, and 5.0 development trees, each at different > > stages of their lifetime. > > Is there any reason not to use 4.0.15 and instead use 3.23 in a > production environment? I know MAX is unstable but I have 4.0.15 > installed. Well, some organizations are more cautious approach to upgrades. -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 4.0.15-Yahoo-SMP: up 1 days, processed 58,542,256 queries (388/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
