MySQL has a new release model
In an earlier post, the pursuit of openness, I announced that MySQL is working at a new release model.
There are still a few details to sort out, but the general plan is ready. The new release model has been approved and starts to operate immediately.
The basic principles of this model are:
- The trunk is always at least in beta quality.
- A milestone starts in beta quality ( never in alpha) with a merge between the trunk and a stage tree;
- Milestone releases, with RC quality, released every three to six months.
- Integration windows between milestones allow the insertion of new features from stage trees
- GA releases happen every 12 to 18 months;
- There are not more than two releases in active support.
The practical consequences of this model adoption is that what was planned for the previous development is now canceled. MySQL 6.0 planned features (Falcon, Maria, Online Backup) are not a priority for the time being.
The next stage tree will be Azalea, which will include the 6.0 features that are stable enough to have a chance to be merged with 5.4 (mainly, subquery optimization batched key access, the fix for Bug#989, out parameters in stored procedures, information_schema.parameters, and some more).
The fundamental difference between this version and the previous one is that Azalea is not blocking. In the previous model, nothing could be released until all the features were ready. In this model, if the features in Azalea are not stable by the time of the intended GA for 5.4, we will rollback, and release only what is ready and stable.
This sort of train model, which has been quite successful with other open source projects, is more dynamic, easy to understand, and more open to participation.
The details of the model are explained in a MySQL University session, today, June 11, at 14:00 UTC (16:00 CET), where Tomas Ulin, director of engineering for the MySQL server, will explain the model and answer questions.
Posted at 12:14PM Jun 11, 2009 by Giuseppe Maxia in mysql | Comments[1]
webinar on Data Reduction and Smoothing in MySQL
|
If you have missed Michael McFadden's session at the last MySQL Conference, here's a chance to catch up. On June 11, at 17:00 UTC Michael McFadden will present at a free webinar, on the subject of Faster Data Reduction and Smoothing for Analysis & Archival in MySQL. Don't let the "For ISVs" distract you. This session is a collection of very practical and down to earth tips for tasks that can be in the TODO list of any DBA. |
|
In addition to being practical, Michael's advice is justified by rigorous statistical analysis, and the tips he provides have both the benefits of practical testing and a scientific justification.
Did I make you curious enough? I may add that the tips provided in this lesson will privilege SQL instead of external languages coding, but some Python will be there as a bonus for the patient attendees.
Posted at 08:38PM Jun 10, 2009 by Giuseppe Maxia in mysql |
MYSQL Planet now with tags and search
|
All this started during a long drive from Charlottesville to Washington, back in November 2008, when I and Dups discussed the status of MySQL Community web presence. We agreed that we needed to enhance the usefulness of the tools for the community, and MySQL Planet was the first candidate for change. Externally, you have noticed very little until now. First, a login, then the voting system, the Buzz, the Italian, Japanese, and Russian aggregators, an improved treatment for group blogs, and finally the Tags and Searching. |
Behind the scenes, there is much more. Dups has been refactoring most of the Planet MySQL code, with the goal of integrating it with the main site. The idea is to eventually allow users to search and use the information available in several formats, such as blogs, forums, presentations, articles, events, and to connect them to each other.
With today's release, we finally see a good reason for logging in to Planet MySQL. Now you can edit tags, thus making the blog posts more useful and easily searchable.
Kudos to Dups and Lenz for the results we got so far. However, there is much more in the making. Stay tuned for the next improvements.
Posted at 07:00PM Jun 04, 2009 by Giuseppe Maxia in mysql |