Issue 683: global name 'ClientError' is not defined
http://code.google.com/p/reviewboard/issues/detail?id=683
Comment #1 by chipx86:
Though the error isn't very clear, this sounds like you don't really have
pysvn
installed.
You can check by running the following on the command line:
python
Issue 684: web services calls return incorrect Content-Type
http://code.google.com/p/reviewboard/issues/detail?id=684
Comment #1 by chipx86:
Fixed in Djblets r11900.
Issue attribute updates:
Status: Fixed
Owner: chipx86
Labels: Djblets Component-API Milestone-Release1.0
Issue 648: Comment in unchanged code appears, but not clickable
http://code.google.com/p/reviewboard/issues/detail?id=648
Comment #1 by chipx86:
This will probably be fixed in the UI rewrite. This code has all been
rewritten from
scratch.
Issue attribute updates:
Status: Started
Issue 497: Easy to forget to save/publish comments
http://code.google.com/p/reviewboard/issues/detail?id=497
Comment #6 by chipx86:
(No comment was entered for this change.)
Issue attribute updates:
Labels: Milestone-Release1.0
--
You received this message because you are listed in
Issue 688: Don't see comment button in review page
http://code.google.com/p/reviewboard/issues/detail?id=688
New issue report by skip.montanaro:
I submitted a review request to our local (test) reviewboard instance:
http://our.internal.server:8000/r/4/
One of my colleagues commented with
Issue 688: Don't see comment button in review page
http://code.google.com/p/reviewboard/issues/detail?id=688
Comment #1 by skip.montanaro:
Duh... Wasn't logged in. :-} (sheepish grin)
--
You received this message because you are listed in the owner
or CC fields of this issue, or because
Issue 688: Don't see comment button in review page
http://code.google.com/p/reviewboard/issues/detail?id=688
Comment #2 by skip.montanaro:
Can I close this issue somehow?
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this
Issue 689: review request emails don't contain change info
http://code.google.com/p/reviewboard/issues/detail?id=689
New issue report by eyal.lin:
What steps will reproduce the problem?
1. Create a review request and publish it.
2. Make a change in the review request (modify branch field), and
