Okay, This is getting very nasty. There is no need for harsh words. Let's take a step back and look at the problem a bit differently. The story, as I understand it, is this; Will made a decision some time ago to develop applications on MySQL. Will based his decision at least partially on the fact that the developers at MySQL stated/estimated/guessed/hoped that they would have a stable version of MySQL 4.0 in January or February. It is now August and no stable version seems to be forthcoming.
>From this, I draw the following conclusions: - Will has a schedule he has to meet but he will not be able to unless he has a stable version of 4.0 - The MySQL team has found the last few outstanding problems in 4.0 very difficult to fix and so they can't say when a stable 4.0 will go out the door I think know what your problem is Will. You made your "purchasing" decision based on a beta version of the software. This is a big no no. MySQL AB is not the first company to miss the mark when it comes to a release date. Always, always, always make your decision based on the current version of the software. You can never know what may happen to completely derail another companies project or a feature. Now, to the boys with the goods. What's the hold up guys? Saying "it will be stable when it's stable" kind of sounds like "go ask someone who cares." Getting a little visibility on the outstanding issues and exit conditions would give everyone the warm-fuzzies. Is there a specific Web page or email you can point us to? Looking forward to an answer from MySQL AB, John -----Original Message----- From: Dean Ellis [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 28, 2002 2:15 AM To: [EMAIL PROTECTED] Subject: Re: Info on 4.0.x release date -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 27 August 2002 09:51 pm, Will French wrote: > accepting this is part of growing up. And while I applaud the honesty of > saying "we won't declare it stable until it is stable," surely you can see > your way clear that if you were explaining a similar situation to your boss > or to your client, they would almost certainly (and justifyably) want you > to give them more details. This is called accountability. Just curious: Are you a customer of or investor in MySQL AB? Have you actually purchased a license or support agreement from them? Or are you, like so many others, expecting to have everything precisely the way you want it, before you even realize that you want it, even though you are not paying a dime for it? Really. Just curious. > Ironically, the fact that I pay no license fees to MySQL AB is based upon Ahhh, I see. So, you are _completely irrelevant_. You are fully entitled to your opinion. Yes, communication with regard to the 4.x series needs some improvement. Yes, they have taken considerably longer than they originally projected. But you are not a customer. You have no right to demand anything of them. They are not accountable to you in any way, shape or form. "You get what you pay for". Accepting this is a part of growing up. Dean Ellis -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9bGprRU3T/K5ORe8RAuqrAJwLiBdMvZzRXY7ttCfyAzVUGJAEPQCfRml/ /KYoxBSm4mmMnAieLXFPH2s= =I7h3 -----END PGP SIGNATURE----- --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
