Difference between revisions of "Review-then-merge"

From PRPL
Jump to: navigation, search
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.  
 
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.  
  
 +
===Diagram===
 
A diagram of the process is below:
 
A diagram of the process is below:
 +
 +
[[File:Review_then_merge.png]]

Revision as of 21:15, 15 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.

Diagram

A diagram of the process is below:

Review then merge.png