Skip to content
phoncey edited this page May 18, 2014 · 3 revisions

The following diagram shows the base setup for each scenario demonstrated in BuildVerification:

The blue circles are commits on the mainline while green circle are commits on developer branches. Arrows going from a blue circle to a green circle is a branch, arrows going the other direction are merges.

origin.tag is a git tag that point to the SHA1 commit (unique identifier for a commit) that is the point where development begins. release.tag points to the SHA1 commit where all changes have been made, merged to the mainline, and a new software build is ready for release!

Each Dev?_b.review is a git tag that points to the SHA1 commit that has been verified as being reviewed by other developers.

With all of this information we should have all the information we need to accurately verify that everything in the release.tag has been peer reviewed!

To do this we can take a look at verifying release.tag!

Clone this wiki locally