379: Shouldn't allow commenting on unpublished diffs.

rde***@vmwar***** (Google Code) (Is this you? Claim this profile.)
May 4, 2008
My first time using reviewboard today, I used a process very similar to
vmware's current process of running perforce diffhtml and sending out a url
to reviewers. I:
- created the review using post-review
- sent this url to some colleagues who added inline review comments
- when I saw the comments, I changed my code and re-ran post-review

When I ran post-review the second time, it overwrote the original diff,
which is fine, but it didn't keep any of the comments!

The problem is that I didn't 'publish' the review, so it had not yet been
saved permanently or given a version number. Since it was in a draft state,
the second run of post-review just overwrite the diff and the comments as
well, which were stored with it.

One possibility would be to make it impossible to comment on an unpublished
review.

This is a very nice tool. Thanks and keep up the good work.
chipx86
#1 chipx86
Thanks. We should definitely prevent commenting on unpublished diffs. I'm actually
surprised anyone was able to see it. We need to fix that as well.
  • -Priority-Medium
    +Priority-Low
    +Component-DiffViewer
  • +Shouldn't allow commenting on unpublished diffs.
david
#2 david
  • +Milestone-Release1.0
david
#3 david
Fixed as r1337.  Thanks!
  • +Fixed