| | 1 | = CodeReviewPlugin Concepts = |
| | 2 | |
| | 3 | == Basic idea == |
| | 4 | * Whenever a changeset is displayed, review information is available: |
| | 5 | * Reviewer |
| | 6 | * Review result description |
| | 7 | * Review result state: ACCEPTED or REJECTED |
| | 8 | * When the user has the permission CODE_REVIEW, this information is editable |
| | 9 | * A button named "Review" is saving the information and setting Reviewer to the current user |
| | 10 | * When the user lacks the permission CODE_REVIEW, this information is read-only |
| | 11 | * Reviews are also available from "View Tickets", if you add a report on the table CODEREVIEW. |
| | 12 | * To make this easier, besides the changeset revision, the changeset author is also redundantly store in this table. |
| | 13 | |
| | 14 | == Ideas == |
| | 15 | ( If approved, turn them to tickets and mark them here accordingly. ) |
| | 16 | |
| | 17 | * Send an email to the author, whenever a changeset is REJECTED. |
| | 18 | * (Somehow) give reviewers an overview on changesets not yet reviews. |
| | 19 | * Currently I accomplish this via the timeline. |
