When I joined MySQL back in June of 2005, one of the first “MySQL Truths” I learned and repeated often when discussing MySQL with others was “release early, release often.” If you’ve been using MySQL for any length of time, you know what that statement means – it meant that MySQL was: (1) dedicated to getting new features and enhancements into the hands of its community so the software’s quality could be validated; (2) eager to take early feedback on those features so the input could rapidly be incorporated back into the product allowing everyone to benefit; (3) committed to very frequent releases of the software so helpful new features and/or external contributions that were ready for action could quickly be put into play and not sit idle on the shelf. And if you’ve been around Open Source for a while now, you know this is the spirit in which most providers of Open Source software operate.
If interested in contributing code to MySQL, you should attend the MySQL University session on contributing code to MySQL.
(Live broadcast with Q&A will be held on Thursday, June 25, 2009. You can still have access to rebroadcasts afterwards.)
If interested in contributing code to MySQL, you should attend the MySQL University session on contributing code to MySQL.
(Live broadcast with Q&A will be held on Thursday, June 25, 2009. You can still have access to rebroadcasts afterwards.)
If interested in contributing code to MySQL, you should attend the MySQL University session on contributing code to MySQL.
(Live broadcast with Q&A will be held on Thursday, June 25, 2009. You can still have access to rebroadcasts afterwards.)
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 …
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 …
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 …
|
When I joined MySQL in 2006, after several profitable years as a consultant, I had a dream. I wanted to improve the product that had contributed to my professional success. The first thing that I learned when I started the uphill task is that it was far more difficult than expected. MySQL called itself open source, but the development practices were for all practical purposes closed source. At the same time, I found that MySQL, below the surface, is an organization with complex and well oiled engineering practices. Indeed, opening up the cathedral, as Lenz put it, was a hard nut to crack. We had a closed source revision control system, and our developers loved it so much, that any proposal to change it was met with strong opposition. We discussed technical matters behind the firewall. Our … |
|
When I joined MySQL in 2006, after several profitable years as a consultant, I had a dream. I wanted to improve the product that had contributed to my professional success. The first thing that I learned when I started the uphill task is that it was far more difficult than expected. MySQL called itself open source, but the development practices were for all practical purposes closed source. At the same time, I found that MySQL, below the surface, is an organization with complex and well oiled engineering practices. Indeed, opening up the cathedral, as Lenz put it, was a hard nut to crack. We had a closed source revision control system, and our developers loved it so much, that any proposal to change it was met with strong opposition. We discussed technical matters behind the firewall. Our … |
|
When I joined MySQL in 2006, after several profitable years as a consultant, I had a dream. I wanted to improve the product that had contributed to my professional success. The first thing that I learned when I started the uphill task is that it was far more difficult than expected. MySQL called itself open source, but the development practices were for all practical purposes closed source. At the same time, I found that MySQL, below the surface, is an organization with complex and well oiled engineering practices. Indeed, opening up the cathedral, as Lenz put it, was a hard nut to crack. We had a closed source revision control system, and our developers loved it so much, that any proposal to change it was met with strong opposition. We discussed technical matters behind the firewall. Our … |