Difference between revisions of "Review-then-merge"

From PRPL
Jump to: navigation, search
(Created page with "In the review-then-merge system for code modifications, changes to the code base happen after a review and vote of the project community. The intent of the review-then-merge s...")
 
Line 1: Line 1:
In the review-then-merge system for code modifications, changes to the code base happen after a review and vote of the project community. The intent of the review-then-merge system is to create and maintain a stable branch of code. A diagram of the process is below:
+
In the review-then-merge system for code modifications, changes to the code base happen after a review and vote of the project community. The intent of the review-then-merge system is to create and maintain a stable branch of code.  
 +
 
 +
A diagram of the process is below:

Revision as of 16:51, 14 July 2014

In the review-then-merge system for code modifications, changes to the code base happen after a review and vote of the project community. The intent of the review-then-merge system is to create and maintain a stable branch of code.

A diagram of the process is below: