This has never been the case before. Just search the PBXT code for MYSQL_VERSION_ID, and you will find things like:
#if MYSQL_VERSION_ID < 50114and, even worse:
XT_RETURN_VOID;
#else
XT_RETURN(0);
#endif
#if MYSQL_VERSION_ID < 60000The lack of changes that affect pluggable storage engines can only mean that the bug fixes required are diminishing in scope.
#if MYSQL_VERSION_ID >= 50124
#define USE_CONST_SAVE
#endif
#else
#if MYSQL_VERSION_ID >= 60005
#define USE_CONST_SAVE
#endif
#endif
And I believe this is a far better gauge of whether GA is close than any other marketing orientated statements! :)
3 comments:
Wow. I had no idea the code was changing that much. It inspires both awe that you've managed to keep up with all of the changes, and a little concern that it was changing so much.
Hi!
5.1 was declared RC a little too optimistically early. I think it will be a while before we see a GA. Less churn does mean that the team is hopefully on the right track.
Cheers,
-Brian
SWEET.. congrats.
I think for people to evaluate PBXT they need to get up and running FAST so hopefully this is a step in the right direction.
Kevin
Post a Comment