Issue 2442: Implement Work-In-Progress Workflow
Status:  ChangeUnderReview
Owner: ----
Project Member Reported by David.Os...@gmail.com, Jan 30, 2014
Very big Gerrit installation sites with >1k active developers and hundreds of new changes per day
have INSANELY high patch review queue and have problem not to be able to keep up with it.

Work In Progress Workflow solves that problem: marking the change as WIP or READY with two buttons
placed on the change screen and only visible for change owners.
With the consequence: hiding or showing the change again on reviewers queue and sending notification to the reviewers.

The process is very easy to grasp:

1. Bob uploads a change for review
2. Alice reviews the change and votes "dislike" on it.
3. Bob realized that addressing Alice's comments takes days or weeks and marks that change per WIP action as Work-in-Progress.
After doing this, that change is removed from Alice's reviewer dashboard.
4. Weeks later Bob uploads new patch set of the change and during the upload its status is changed from WIP to NEW.
5. Alice review it again and find out that not all comments were addressed and votes "dislike" on it again.
6. Bob realized that it takes days or week ... the loop 3,..,6 can be repeated multiple time.
[...]
42. Alice approves the change and it get merged.
Jan 30, 2014
Project Member #1 David.Os...@gmail.com
Two different approaches:

* in addition to DRAFT workflow: https://gerrit-review.googlesource.com/50254
* as a replacement for DRAFT workflow: https://gerrit-review.googlesource.com/54088
Status: ChangeUnderReview
Feb 28, 2014
Project Member #2 David.Os...@gmail.com
(No comment was entered for this change.)
Status: Invalid
Owner: ---
Jul 16, 2014
Project Member #3 David.Os...@gmail.com
(No comment was entered for this change.)
Status: ChangeUnderReview