17
edits
Add-ons/Reviewers/Guide/Reviewing: Difference between revisions
Updated to reflect accurate reviewer actions for policy violations
No edit summary |
(Updated to reflect accurate reviewer actions for policy violations) |
||
| Line 134: | Line 134: | ||
Add-ons must be reviewed '''completely''', noting issues in the review comments field as you find them. We want to avoid sending multiple partial reviews to developers and give them an opportunity to address all policy violations at once in their next submission. | Add-ons must be reviewed '''completely''', noting issues in the review comments field as you find them. We want to avoid sending multiple partial reviews to developers and give them an opportunity to address all policy violations at once in their next submission. | ||
Depending on the severity of the issue, add-on versions can either be rejected, | Depending on the severity of the issue, add-on versions can either be rejected immediately or delayed rejected with the policy violations found. If any additional non-policy violation details need to be communicated, it can be done using a reviewer reply. | ||
In order to support you in communicating with developer, and making consistent review decisions, we have prepared a set of [[Add-ons/Reviewers/Guide/Review Decision|Review Decision Guidelines]] that you should take a moment to read right now. It contains important information on when a rejection is warranted and will explain how to complete the review. | In order to support you in communicating with developer, and making consistent review decisions, we have prepared a set of [[Add-ons/Reviewers/Guide/Review Decision|Review Decision Guidelines]] that you should take a moment to read right now. It contains important information on when a rejection is warranted and will explain how to complete the review. | ||