Send reminder mails to reviewers who have not responded after fixed time.

Hi, I would like to know if it is possible to Send Reminder Mails to reviewers who haven't responded to a review posted within a specified amount of time ? This will be helpful in case some reviewer has forgotten to review for some reason and overlooked the Dashboard. If it is not already avail

Re: Send reminder mails to reviewers who have not responded after fixed time.

There's nothing yet to do this automatically. What most people do is to just add a review to their own change with some kind of ping message. I personally prefer this solution because different changes often have different priorities, and people already get quite a bit of email from review board.

after code review, i can not submit code to svn repository

Hi, i encountered one issue, please help. i installed review board, also configured, i can submit review request, after reviewers review the request, when i click close- submitted, but the code can not submitted to the svn repository, please help me, thanks, will be appreciated. regards liting --

Re: after code review, i can not submit code to svn repository

Review Board does not automatically submit code for you. What's expected is that you'll commit your code as you have always done, and "close -> submitted" is just a way of marking the review request as being done because the code is committed (as opposed to closing because the change was abandon

LDAP Authentication

FYI, I had to add this to the backends.py for ldap authentication to work. It needs to happen both in the authenticate and the get_or_create_user function in the ldap backend class. ldapo.set_option(ldap.OPT_SIZELIMIT, 100) ldapo.set_option(ldap.OPT_REFERRALS, 0) Without

Re: Question about postreview.py get_repository_info

Here is a more accurate description: In ReviewBoardServer.get_repository_info, it calls ReviewBoardServer.api_get to fetch the repository info from sever, from my debug, it show the return json is something like (if the repository is svn) { "stat": "ok", "repository": { "path": "h

Re: Question about postreview.py get_repository_info

A more correct and readable json than last post, the indent for "name" in the last post is wrong. { "stat": "ok", "repository": { "path": "http://192.168.1.131/svn/Android";, "tool": "Subversion", "id": 2, "links": { "info": { "hre

Re: after code review, i can not submit code to svn repository

Hi, David thanks, appreciated. Best Regards liting 2011/1/12 David Trowbridge > Review Board does not automatically submit code for you. What's expected is > that you'll commit your code as you have always done, and "close -> > submitted" is just a way of marking the review request as being don

Clustered RB Instances ?

Hi ALL, I have been using RB since 1.0 and then I have successfully upgraded it 1.5.2. We have global teams which would like to use RB Server for their code reviews. The source code repositories are located in their respective geographies. Is it possible to have clustered instances of RB Servers

Re: Question about postreview.py get_repository_info

Hi Dan, You're correct, this is a bug, and your fix looks fine. We'll have to get that fix in. Want to post a review request? Christian On Wednesday, January 12, 2011, Dan wrote: > Here is a more accurate description: > > In ReviewBoardServer.get_repository_info, it calls > ReviewBoardServer.ap