If you start writing a review and save it as a draft, a revision is created. If you continue writing the review and saving it as drafts, additional revisions are created. When the review is published, you have the ability to see all of the revisions that were made while the the review was in a draft state.

I don't think that it's a good idea to expose a user's draft reviews to everyone. I wonder if we should have only a single revision while a review is in draft? We already exclude drafts from the dumps, but when a review is published we appear to include revisions from when the review was being drafted

Some options:

• Don't make revisions when a draft is continually edited. Positive: No revisions to take care of. Negative: User can't see old versions of their draft
• keep revisions while a review is in draft, but remove/merge them when published. Positive: A user can still see old versions of their drafts up to the point that they publish.
• Keep revisions from drafts, but don't dump them and don't show them to people who are not the author. Positive: Least amount of code changes.