Updates:
Status: Fixed
Comment #11 on issue 1277 by trowb...@gmail.com: Comment Types
http://code.google.com/p/reviewboard/issues/detail?id=1277
The issue-tracking branch was merged for 1.6
--
You received this message because you are subscribed to the Google Groups
reviewboard-issues
Comment #8 on issue 1277 by trowb...@gmail.com: Comment Types
http://code.google.com/p/reviewboard/issues/detail?id=1277
Issue 1951 has been merged into this issue.
--
You received this message because you are subscribed to the Google Groups
reviewboard-issues group.
To post to this group,
Comment #9 on issue 1277 by trowb...@gmail.com: Comment Types
http://code.google.com/p/reviewboard/issues/detail?id=1277
Issue 1941 has been merged into this issue.
--
You received this message because you are subscribed to the Google Groups
reviewboard-issues group.
To post to this group,
Comment #7 on issue 1277 by trowb...@gmail.com: Comment Types
http://code.google.com/p/reviewboard/issues/detail?id=1277
Issue 2000 has been merged into this issue.
--
You received this message because you are subscribed to the Google Groups
reviewboard-issues group.
To post to this group,
Comment #4 on issue 1277 by vi...@djgraphite.com: Comment Types
http://code.google.com/p/reviewboard/issues/detail?id=1277
I think that while this is a good idea in spirit, I'm not sure it would
work in practice. I don't think severity is
useful in the case of code reviews in the same way
Updates:
Status: NeedInfo
Labels: Component-DiffViewer Component-Reviews
Comment #2 on issue 1277 by chipx86: Comment Types
http://code.google.com/p/reviewboard/issues/detail?id=1277
We're having some discussions and debates about how far to go with this
feature. We
have
