Re: post-review potentially confused about different repository addresses?

Hey Christian, What you can do in this case is to set your main repository URL to be your anonymous path (which Review Board will use for checkouts), and then set Mirror Path to be your developer SVN URL. When looking up a URL, it will check against both of those URLs, and should find the

Database Archival

First of all let me thank all developers and contributors for this wonderful project. I have been using Reviewboard for the past couple of months in my organization and found this extremely useful. This is a great improvement over an internal tool that we had that helped in generating pretty html

Re: exception after publishing review

Hi Cristian, Server version: Apache/2.2.10 (Linux/SUSE) Server built: Dec 3 2008 13:33:50 After a few fits and starts, the install was pretty straightforward. Almost by the book I think. At first I was trying to put reviewboard in a subdirectory, but I backed off of that and ran rb-site

Re: exception after publishing review

Here is my reviewboard.conf file. The only modification that I know if is that its running on port 8080. Let me know if there is another configuration file that would illuminating. VirtualHost *:8080 ServerName ilmwiki0.cup.hp.com DocumentRoot /srv/www/reviews/htdocs #

Re: Slow Performance On Large Diffs -- much better, but still a big issue for us.

The downloadable diff for the review is 1.6MB. The review has 138 different files (7 pages). Page 1 loads in ~1 minute in FireFox. The twenty files are on average 38 K. (max=118K, min=2K). Here all files have edit changes (no deleted files.) Page 3 loads in ~3 minutes in FireFox. The twenty

Re: Reviewboard CMSynergy

Hey David, Thanks for the response. I'm willing to help out on this. Sadly don't know where to start from. I looked at all the other scmtools in the repository. I guess I need to come out with another such interface for cmsynergy. Are there any docs that I can refer to? --aditya On Tue, Mar 17,

Re: Database Archival

Hi Raghu, Thanks for the nice words about the project! Screenshots themselves are stored in your site's htdocs/media/uploaded/images/ directory. They're referenced in the database but not stored there. There's no way to archive review requests from the database. I honestly don't know how we'd

Re: post-review potentially confused about different repository addresses?

Glad it works. I'm writing new docs that I hope to post before long (a couple pages to go through and they should be ready) and they'll address Mirror Path and talk about when it's useful. Yeah, go ahead and submit a bug for that. Our handling should ideally be less strict. Christian --

Re: Slow Performance On Large Diffs -- much better, but still a big issue for us.

We went with this method because it was similar to our existing method we used at VMware, and we wanted to provide a smooth transition. This actually works out quite well for us still. You can set 1 diff per page in the Diff Viewer settings in the admin UI, but the file listing only shows the

Issue 933 in reviewboard: Clicking expand triggers review comment

Comment #3 on issue 933 by chipx86: Clicking expand triggers review comment http://code.google.com/p/reviewboard/issues/detail?id=933 Issue 961 has been merged into this issue. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred

Issue 965 in reviewboard: Edit buttons on Review Request screen are not accessible

Comment #2 on issue 965 by brad.taylor: Edit buttons on Review Request screen are not accessible http://code.google.com/p/reviewboard/issues/detail?id=965 Additionally, the edit buttons are not focusable, so I'll have to figure a way to make that happen also. -- You received this message

Issue 965 in reviewboard: Edit buttons on Review Request screen are not accessible

Updates: Status: Confirmed Labels: Milestone-Release1.0 Component-Reviews Comment #3 on issue 965 by chipx86: Edit buttons on Review Request screen are not accessible http://code.google.com/p/reviewboard/issues/detail?id=965 Can you submit this to our Review Board server? --

Issue 965 in reviewboard: Edit buttons on Review Request screen are not accessible

Comment #4 on issue 965 by brad.taylor: Edit buttons on Review Request screen are not accessible http://code.google.com/p/reviewboard/issues/detail?id=965 Updated patch to make the button focusable (by using an a tag) and thus clickable via Firefox (when a user hits Enter, Firefox will

Issue 914 in reviewboard: API Broken Alpha2: api/json/reviewrequests/rid/reviews/

Comment #1 on issue 914 by ciaomary: API Broken Alpha2: api/json/reviewrequests/rid/reviews/ http://code.google.com/p/reviewboard/issues/detail?id=914 The fix for my issue was found. I needed to pass in id=$rid with the request. This is not documented in the API doc however. I request that

Issue 967 in reviewboard: repository hostname lookups are not really canonical

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 967 by psc...@vmware.com: repository hostname lookups are not really canonical http://code.google.com/p/reviewboard/issues/detail?id=967 Currently, post-review relies on calls to various socket module functions in order to