Another project is gerrit2 has the workflow you are looking for. But it is
heavy and tricky to find that
perfect workflow. Reviewboard is much more simple and elegant, to the
point, easier to use, and
setup (contrary to my blunders). But to have that source "gatekeeper", the
project is gerrit2.
On Wednesday, June 13, 2012 3:22:55 AM UTC+2, Christian Hammond wrote:
> Hi Soumen,
> Review Board isn't in the source code management business. We actively
> stay away from it. It won't commit for the user, and doesn't have built-in
> support for approving commits. Some people (probably a few on this list)
> have developed pre-commit hooks that will check Review Board for approval
> before allowing a commit, but there's nothing sanctioned by our project to
> do that.
> The reason for that is that every company has a slightly different policy.
> What does approval mean? Does it mean at least 1 Ship It, or does it mean a
> certain percentage? Does it require certain people to approve it? Certain
> This is a company policy problem, and a social problem, and not something
> Review Board attempts to solve.
> The typical flow is that a person will first put a change up on Review
> Board, and people will approve it. When that change meets whatever criteria
> is required by the company/team, then the user can commit the change.
> Review Board will never commit for the user. It doesn't have the
> credentials, or checkouts of the tree to do so. That's all left up to the
> individual, and would be too complex, resource-intensive, insecure, and
> problematic for Review Board to handle, especially for all the types of
> repositories we support.
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
> On Tue, Jun 12, 2012 at 4:50 AM, Soumen Hajra <soumen.sn...@gmail.com>wrote:
>> Hi All, Soumen here from snaps technology. We installed reviewboard
>> web application in jacklehost.org . This is hosted in Amazon Server.
>> Now we wanted to integrate this with SVN. The next phase of using
>> reviewboard is when we make changes to our project in our local
>> and we want to do a SVN commit those changes first go into
>> reviewboard. Then reviewer will review and approve the changes in
>> reviewboard. And upon approval, the changes get added to SVN and
>> commit happens. So, somehow, reviewboard needs to intercept SVN
>> Our code changes first should go to the reviewboard. Then approval
>> sends them to SVN.
>> I'm not sure how to configure. Is it possible in reviewboard?
>> Thanks, Soumen
>> Want to help the Review Board project? Donate today at
>> Happy user? Let us know at http://www.reviewboard.org/users/
>> To unsubscribe from this group, send email to
>> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at