Showing entries 11 to 20 of 37
« 10 Newer Entries | 10 Older Entries »
Displaying posts with tag: contribution (reset)
Contributing to MySQL

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.)

Contributing to MySQL

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.)

Contributing to MySQL

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.)

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 …
[Read more]
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 …
[Read more]
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 …
[Read more]
The pursuit of openness

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 …

[Read more]
The pursuit of openness

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 …

[Read more]
The pursuit of openness

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 …

[Read more]
Another Pluggable Storage Engine for MySQL

Kazuho Oku of Cybozu Labs, Inc., a community contributor to MySQL and SCA signatory, gives a talk on Q4M, a message queue stroage engine for MySQL.

Showing entries 11 to 20 of 37
« 10 Newer Entries | 10 Older Entries »