Issue 703: "Master and apprentice" concept in review activity.
Status:  Released
Owner: ----
Closed:  Oct 2012

Blocked on:
issue 971
Project Member Reported by fredrik....@sonyericsson.com, Sep 1, 2010
Now that we have a much more flexible rights system coming through the doors shortly, I'd like to request a another quite useful way to use it;
Master and apprentice. We've had the concept as a nice example as to how code review can be used, a more senior developer can code review a junior one before it's time to submit.
Well, I'd like to formalize this feature a bit because I think it's great idea, but with the current rule set it's in practice a voluntary concept. What if we could enforce it?

Example:
For a given apprentice developer, a senior developer is the assigned the master/mentor role.
For each change uploaded by the apprentice, the mentor must give an approving review (code review or verification depending on the rule stated) before the change can be submitted, regardless of others also giving positive reviews.
Sep 1, 2010
Project Member #1 fredrik....@sonyericsson.com
I might add that with this kind of role we probably also want to implement watch functionality of changes uploaded by a certain user to certain or all projects.

I'll write a separate issue on the watch functionality overall.
May 20, 2011
Project Member #2 nas...@grainawi.org
Should be supportable though the custom workflow engine and similar to  Issue 739 .
Status: Accepted
Blockedon: 971
Oct 25, 2012
#3 JBjo...@gmail.com
Added this as an example in the prolog-cookbook.
Review request:
https://gerrit-review.googlesource.com/#/c/38860/
Oct 30, 2012
Project Member #4 edwin.ke...@gmail.com
(No comment was entered for this change.)
Status: Submitted
Labels: FixedIn-2.5
Oct 31, 2012
Project Member #5 edwin.ke...@gmail.com
(No comment was entered for this change.)
Status: Released