Difference between revisions of "Merge-then-review"

From PRPL
Jump to: navigation, search
Line 1: Line 1:
 
In the merge-then-review system for code modifications, committers can commit code to a branch without prior review. Any community member may request a review of code that once it has been merged and, if they see fit, they may veto the code change and have the change removed. The intent of this system to allow rapid development and prototyping while still allowing any member of the community veto authority as in the [[Review-then-merge]] system.
 
In the merge-then-review system for code modifications, committers can commit code to a branch without prior review. Any community member may request a review of code that once it has been merged and, if they see fit, they may veto the code change and have the change removed. The intent of this system to allow rapid development and prototyping while still allowing any member of the community veto authority as in the [[Review-then-merge]] system.
  
 +
===Diagram===
 
The diagram below summarizes the merge-then-review system:
 
The diagram below summarizes the merge-then-review system:
  
put diagram here
+
[[File:Merge_then_review.png]]

Revision as of 21:15, 15 July 2014

In the merge-then-review system for code modifications, committers can commit code to a branch without prior review. Any community member may request a review of code that once it has been merged and, if they see fit, they may veto the code change and have the change removed. The intent of this system to allow rapid development and prototyping while still allowing any member of the community veto authority as in the Review-then-merge system.

Diagram

The diagram below summarizes the merge-then-review system:

Merge then review.png