Markus Popp wrote:
> I think that's a good idea. At the first moment it looks a bit shocking to developers like me, but
> after reading the detailed information I found the new way that MySQL AB goes OK ;-).
>
> The most important desicion is that nothing is taken away from people who want to use MySQL in
> the same way as in the past. The worst error would have been to make developers (and people
> who want to use MySQL for free) 'second class users' and I hope that MySQL AB will always be
> aware of the importance of the 'free part of MySQL' - because that's what made MySQL what it
> is today. I also find it important that MySQL keeps a single code base so that both the Network
> Edition AND the Community Edition benefit from each other. So if I got it right - the
> implementation of new features and fixing bugs will just happen at different points of time,
> but both editions will get them (probably the Network Edition more conservatively, the Community
> Edition more progressively).
Thanks for your kind feedback - indeed, your summary pretty much describes how things work.
> I'm looking forward to seeing the progresses of MySQL in the future - I'm excited for the new
> MySQL 5 production release and I hope that many ISPs make their updates soon.
Ditto - ISPs have been quite conservative in the past... overall a good trait for sysadmins, not complaining on that account ;-)
> Please don't mind if I make a little advertising on my behalf ;-) - at www.db4free.net we offer
> free MySQL 5 database accounts. We are now in the public beta testing stage, but if you want
> to test the new features of MySQL 5 (and help MySQL making
> bug reports, if you find some), please contact me
> (m.popp@db4free.net) to get your account.
I've taken the liberty of plugging your site in my blog, I think it's an excellent initiative and a good example. Thanks.
Regards, Arjen.
--
Arjen Lentz, Exec.Director @ Open Query (http://openquery.com)
Remote expertise & maintenance for MySQL/MariaDB server environments.
Follow us at
http://openquery.com/blog/ &
http://twitter.com/openquery