Slashdot totally misinterpreted Jeremy's post about MySQL starting to build features first for their customers. As a business model , this sounds like a good way to get revenue , customers want certain features that are valuable to them , so why not let them pay for it .

The question however is how your development cycle works. Often this method of keeping code first for your paying customers , and when "the feature has been paid for" give it to the opensource community , is the wrong one.

What it comes down to is that you neglect the release early , release often and the peer review , many eyeballs see more bugs, fundamentals that made opensource projects big and stable. You are in effect stepping back to a proprietary model where you have to rush your deadlines because you have promised customers such and such feature, hence letting your customers do your beta testing.

It?s not like it?s the first time MySQL pulls this trick. They already did that when building a Carrier Grade edition for Cluster. That indeed also was a product where they had customers paying for unstable beta products.

The peer review process is one of the things that insanely attracted me in Open Source, the code that you get is not some piece of overrushed code where a developer made a dozen shortcuts because he had to make a deadline, but a piece of code that has been reviewed by many , discussed, and then eventually allowed into the project.

Releasing beta level code to customers and eventually to opensource means you miss out on a lot of the features a true opensource project has.

Often the reason why Open source minded organisations still chose for this approach is to get revenue to be able to hire more developers/ support peope and improve the product faster. But it's a vicious circle, because your product isn't up to the standards you are used to you need more people to support it.

However in the MySQL case , a mostly user community, lesser user development contributions, this could make sense.

Dear Falconers,

MySQL 6.0.4-alpha, a new version of the MySQL database system including
the Falcon transactional storage engine (now at beta stage), has been released. The main page for MySQL 6.0 is at:

http://www.mysql.com/mysql60/

If you are new to the Falcon storage engine and need more information,
please read the Falcon Evaluation Guide at:

http://www.mysql.com/why-mysql/white-papers/falcon-getting-started.php

and the Falcon White Paper at:

http://www.mysql.com/why-mysql/white-papers/storage-engines-falcon.php

MySQL 6.0.4-alpha is available in source and binary form for a number
of platforms from our download pages at

http://dev.mysql.com/downloads/mysql/6.0.html

and mirror sites. Note that not all mirror sites may be up to date at
this point in time, so if you can’t find this version on some mirror,
please try again later or choose another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches etc.:

http://forge.mysql.com/wiki/Contributing

The change list is extremely long. Therefore I did not c&p’ed it here. You can view it online at:
http://dev.mysql.com/doc/refman/6.0/en/news-6-0-4.html

We are planning to build a base of official testers for WikkaWiki, this post is to announce the launch of our beta-testing programme and the availability of (unstable) nightly builds from our code repository.
(more…)

The Wikka development team has made Wikka 1.1.6.4, release candidate 1 (RC1) available for download and testing. Please download from the WikkaWiki home page. Additional links to the release notes and issue tracker can be found there as well. While this release candidate has been thoroughly vetted by the development team, we do not recommend its use in a production environment. We anticipate the final release of Wikka 1.1.6.4 to occur at the end of the month.

Thank you so much for your patience. We believe this release will be well worth the time to upgrade to, as it addresses several spam-related issues that have cropped up with earlier Wikka versions over the past few months.