Review new versions

Review is the step between "someone published a version" and "anyone can install it". It applies to organisation artifacts. A version in your personal account is published at once, because there is nobody else to review it.

The Review queue

Open Review. Waiting on you lists versions you can decide on. Waiting on others lists versions you submitted that are still in review. People who can approve are notified when a version arrives.

Reviewing a version

Open a version from the queue. You see the author's note, Changes (every file compared with the previous version), a comment thread with the author, the Health report, any Prior decisions and Affected installs. Then choose:

• Approve: the version is published and can be installed.
• Request changes: it goes back to the author. A note is required.
• Reject: it is turned down. A note is required.

While a version waits, its author can Withdraw it and submit again later with changes.

Rules

• You cannot review a version you wrote. The page says "Someone else has to review it."
• You need permission to approve in that organisation. Without it you can read the review but not decide.
• Once a version is decided, it cannot be decided again. Publish a new version instead.

The review policy

Owners and admins choose, in the organisation's settings, whether projects may skip review (Allow projects to skip review). If allowed, an admin or the project lead can turn on Skip review for this project. Versions published that way are permanently marked unreviewed. Content imported from GitHub, and versions published by browser link (deftro publish --via-browser), always wait for review, even in such a project. Open your organisation from Organisations, then Settings.

Activity

Every decision, with its note, is recorded in Activity, so you can always see who approved what and when.