Back in late 2006, MySQL AB decided to split (or “fork” for the more common open source term) their source code and release structure into two parts: “Community” and “Enterprise”. This has caused quite a lot of stirring in the MySQL market, and a lot of confusion about what exactly the difference is and how the release structure works. It’s actually not easy to really explain the new structure, and I won’t try here. The key point for the purposes of this discussion, is that MySQL is effectively no longer providing builds (binaries) of their community releases, and they don’t provide enterprise builds at all to the public. They are providing source releases of community, but fairly infrequently.
This is a big problem, because it means that there is no realistic way for the average developer or MySQL user to get regular builds (and ones that quickly address bugs) without paying MySQL for a support contract. Most of Proven Scaling‘s customers do not have support contracts with MySQL AB, and have been quite unhappy about the change, and personally I’ve lost a reasonable way to get new features pushed out to the public without excessive delays (up to 6 months to the next community release, and years for enterprise).
Back when MySQL originally polled me on this issue and told me of their plans, I told them that they would just force the community to repair the “damage” in the ecosystem, by providing the builds themselves. I even warned that the one doing the repairing could possibly be myself and Proven Scaling…
So, to get to the point…
This week, at the MySQL Conference and Expo, Solid Information Technology and Proven Scaling have announced a collaborative project to address the needs of the community for frequent releases with interesting features, bug fixes, and new patches: DorsalSource. Immediately, we have begun providing over 40 binaries of MySQL community and enterprise forks on Linux, Mac OS X, and Windows. We plan to add many additional platforms and variations of the builds, in addition to many more features to build a real developer community around MySQL.
We will continue the development of DorsalSource, adding many great new features—we have a ton of ideas, it’s just a matter of implementing them and getting them out there for users to use. If you have any questions, comments, or ideas for how to improve the site, or really anything at all, please feel free to contact me directly or leave a comment here.
Hey! This stuff is pretty cool. I’ll love to watch what happens with this. If the build system, etc. code will also be public, will make it rock…
Great. thanks for doing this.
You rock, is all.
I’d offer to have your babies but you found someone for that already. I’ll just admire….and coo at said babies.
dbnewz » Blog Archive » DorsalSource
Je ne sais pas vous mais moi si il y a quâ€™autre chose qui mâ€™ennuie câ€™est bien de recompiler les sources de MySQL Ã chaque fois que je veux tester un patch. Dâ€™une part il va toujours me manquer quelque chose et de lâ€™autre je perds un temps fou. La solution Ã ce problÃ¨me est enfin lÃ , grÃ¢ce Ã DorsalSource , la nouveautÃ© de mon ami JÃ©rÃ©my Cole de provenscaling.
Thanks You Al..