MySQL Development Process

1. feature development)

The function development process is as follows:

• A MySQL function refers to a worklog.
• The development of worklog should go through the process of specification definition, design, architecture review, code implementation, code review, and QA review (but these processes are not carried out in strict order ).
• MySQL functions are first implemented on a feature tree (feature tree.
• The function tree is cloned from the MySQL code master development tree trunk (generally created by the developer), and is occasionally synchronized from the trunk during the development process.
• After the function is implemented, it must be reviewed by the Code.
• After the code review is passed, the development tree is taken over by QA.
• QA tests functions. If a defect (bugs) is found, the developer must fix the fault. After the test is passed, QA sets the status to sign off ).
• Once the QA verification is completed, the functions will be merged into the trunk.

Through this process, trunk will continuously accumulate functions and code for defect fixing. The additional regression test (regression testing) is continuously executed on the trunk to ensure that the trunk is always able to maintain the quality of the candidate release version (Release Candidate.

2. Lab version (lab releases)

The lab version is a preview version of one or more features. Features in the preview version are usually under development and have not been integrated into trunk. When the MySQL Community is very interested in a function and wants to evaluate the function as soon as possible, a lab version will be created. The lab version has the same quality as the beta version, and may only run on a specific platform. No documentation is available for reference. Finally, functions in the lab version may not be integrated into future development milestones (DMR) or GA versions. The lab version can be found in labs.mysql.com.

3. Development Milestone version (Development Milestone releases (DMR ))

The Development Milestone version contains all the new Code on the trunk (from the previous DMR to the current DRM ). every 3-6 months, a Development Milestone version (DMR) will be generated from trunk. when a Development Milestone version is created, all new functions are written in the document (MySQL Manual ). the Development Milestone version has the quality of the candidate release version (RC) and can run on all platforms supported by MySQL.

Frequent releases of Development Milestones provide reliable versions for users who want to use them as soon as possible, and collect feedback from users. These feedback can be used to improve the quality of the next milestone version. The milestone version can be found in MySQL developer zone.

The milestone version production process is as follows:

• The release manager sets the cut-off date for the Development Milestone version. All new features merged into the trunk before the split date are included in this milestone version.
• Trunk will be temporarily frozen before code separation. QA will conduct additional tests and evaluations on frozen trunks.
• The QA confirms that code can be separated (signs off trunk ).
• Clone the code from the trunk and create the Development Milestone version tree. The trunk is restored, and the daily merge operation can proceed normally.
• QA tests the Development Milestone version tree. After a bug is fixed, QA approves the release of the milestone version.
• Announce the release of the milestone version.

Figure 1. Milestone version release

4. General available version (generally availability (GA) releases)

The GA version is recommended in the production environment. A ga version is released every 18-24 months. You can find it in MySQL developer zone.

The production process of GA version is as follows:

• The GA version is based on the Development Milestone version.
• The selected Development Milestone version, after more tests and defect fixes, generates a candidate version (Release Candidate) and publishes it to the community.
• The candidate version can be released only after it reaches the GA quality after being evaluated by customers and users. The candidate version is released several iterations until Ga quality is achieved.
• Ga version released.

Figure 2. Ga version released

In general, this article is a translation of the official English version, which may be slightly different (for easier understanding). The original Article is here.

Original article, reprinted Please note:Article address: MySQL development process Introduction

Link: http://www.mysqlops.com/2013/05/07/mysql%e5%bc%80%e5%8f%91%e6%b5%81%e7%a8%8b%e4%bb%8b%e7%bb%8d.html