My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 458: Add a terminology page to the docs
7 people starred this issue and may be notified of changes. Back to list
Status:  Accepted
Owner:  ----


Sign in to add a comment
 
Reported by docw...@gmail.com, Feb 18, 2010
Here are some terms I put together when I reviewed gerrit for use in our 
workplace.

-------------------

Change: A "change" is a change to the code that attempts to do one thing. 
Ultimately, it will be committed as a single commit. However, it may go 
through multiple iterations.

Patch: An iteration to a change. A change may go through many versions 
before it is approved and allowed to be submitted.

Code-Review: A look at the code by other developers. The developer may 
have a stake in the code or may be just looking. Code can be marked at 
multiple levels of code review. The scores with an absolute value of 2 are 
for stake-holders, people who are intimate with the code. The scores with 
an absolute value of 1 are for non-stake-holders or people who don't feel 
strongly about their opinion.
+2 Looks good to me, approved.
+1 Looks good to me, but someone else must approve.
0 No score
-1 I would prefer that you didn't submit this.
-2 Do not submit.

Verification: This is site and possibly project dependent. It could mean it 
was ran through unit-tests (and therefore automated) or it could mean 
that it was approved by management. It has three values. Only one 'fails' is 
needed to prevent a change from being accepted.
+1 Verified
0 No score
-1 Fails

Submit (aka Merge): This means that the change was verified, approved 
and put into the official branch. This is done automatically once a change 
has met the requirements.
May 20, 2011
Project Member #1 nas...@grainawi.org
(No comment was entered for this change.)
Status: Accepted
Sign in to add a comment

Powered by Google Project Hosting