I'm not sure I care what the version number is (5.3,5.4,5.4,6.0), and you can talk about milestone releases all you want. What really matters to me is when we'll have something beyond 5.1 marked as GA. Will it be 5.5? When should I expect that?
5.4 was announced last year at the conference with lots of performance fixes for the mysql server itself. Great. Until those changes percolate up into a stable release, they aren't worth too much to me. With all the hoopla about the release cycle, I haven't seen any results in the form of new features/fixes making it to stable any faster than 5.1 did.
What's the point of any release cycle beyond getting good solid code to stable in a timely (i.e., not 3 years) and safe (i.e., well tested) manner? Can't we have both timely and safe?
Although I understand your
Although I understand your frustration, I think one should not underestimate the amount of time and energy that has been burned by the uncertainty regarding the possibilities of the takeover. And former MySQL ab employees may still bear some scars of the Sun integration. I don't want to overdramatize things, but these takeovers and the integration process disrupt the normal way of doing your work, and can be very tiring and detrimental to the overall morale.
kind regards,
Roland Bouman
+1 on your post. Maybe we
+1 on your post. Maybe we should have a bug on MySQL to get a more transparent release schedule. Having a quick look at bugs.mysql.com i submited bug http://bugs.mysql.com/bug.php?id=51033 inviting everyone interested to discuss the bug.
To summarise, you want
To summarise, you want production-ready versions (GA), not just "releases" - right?
From my perspective: published code and binaries are of course important, and Sun/MySQL has vastly improved that aspect over the last year, but it does not help today's production systems if that code doesn't make it into a GA release in the fairly short term. So that's the next necessary step, get that right again.
Yes, exactly. To me the
Yes, exactly. To me the release cycle is incomplete if it's not clear when a milestone (or set of milestones) will make it to GA. Unless I missed something, I can't find any such plan for 5.5 (or what is in 5.5 now, and was in 5.4 almost a year ago).
I totally agree. If Oracle
I totally agree. If Oracle does not kill MySQL, they kill themself :-(
Anyone who implenents MySQL needs a reliable schedule about what to expect next. Timetables can skip, but you can't announce 5.4 just to let it silently die half a year later. I spent = wasted a lot of time with 5.4.
OK, so MySQL has now announced next is 5.5. Can I trust them? No! Perhaps in another half year, MySQL=Oracle will go for 6.0. Or MySQL VI, just for the fun of it! This makes no sense.
Sadly, it appears that MySQL
Sadly, it appears that MySQL is going down the same path as Java. Sun started with the open source Java project for a reason. Oracle is profit motivated, and it will only be a matter of time before Java falls into that paradigm, now that Oracle has acquired Sun. Same with MySQL. You want to build MySQL enterprise applications? Buy it.
Post new comment