Jump to >
Review Board Power Pack Release Candidate

Updated 30-October-2013, 12:05PM PST: Fixed the minimum Review Board version required. You'll need 1.7.14 or higher.

We're pleased to announce a release candidate for the Review Board Power Pack. While previous beta releases have been limited to people who signed up for our beta program, his release candidate is public, and anyone who is using Review Board is welcome to try it out.

The Review Board Power Pack is a set of advanced features to help you get even more out of your peer review system. If you'd like to check out what's included, see the Power Pack page.

Installing and activating the Power Pack

If you're running a previous beta of the Power Pack, you should have received an email with detailed instructions on how to upgrade. If you're a new user, use the following instructions.

To get started, make sure you have Review Board 1.7.14 or newer installed. Then install the Review Board Power Pack by running:

easy_install -f http://downloads.beanbaginc.com/powerpack/ -U ReviewBoardPowerPack

Once that's installed, reload your web server, then browse to your administration interface and click "Extensions." You should see a single extension. Click "Enable" to activate it.

Once the extension is activated, you need to install a license. We've created a trial license which will keep things going until January 1, 2014. You can download this license at http://downloads.beanbaginc.com/powerpack/powerpack-trial.lic

Once you have the license file, click "Configure" on the extension. You should see a field where you can upload the license file to your Review Board server. Once you do this and save, you should see a trial license installed, and the Power Pack features will be enabled.

Using the Power Pack

Any PDF files that are attached to a review request (with "Upload File") will then have a "Review" button which will take you to a document viewer. To add comments, simple drag across a region of a page like you would with an image attachment.

To add GitHub enterprise repositories, go to the "Add Repository" section in the admin interface. You should now see a new hosting service called "GitHub Enterprise". Configuration works just like GitHub.com, but you'll put your GitHub Enterprise server name in the form.

Setting up multiple front-end servers is a complex task, and we're working on some documentation about it. In the meantime, if you're planning on using the Power Pack for this, get in touch and we'll help you out.

We'd like to hear your feedback, good and bad. If there are any features that would be important to your organization, please let us know that too.

For any questions or comments, you can reach us at any time at support@beanbaginc.com.

Review Board 1.6.20 and 1.7.16 released

Every once in a while, things just don't work the way they should. And with that, I bring you two new Review Board releases.

This fixes three main issues. First, the recent work on the API caused a breakage in the Review Group Users resource when looking up a user that was a member of more than one group. While this doesn't affect usage of Review Board itself, it does affect those who need that part of the API for their scripts.

Second, due to a regression in a tool we use for packaging, the Python 2.6 builds for Review Board 1.7.15 shipped with broken JavaScript files. We've reverted the version to the last known stable version.

Third, pagination in the dashboard was broken in 1.7.15. This was fixed last night with a new build of Djblets, and now this release depends on that newer version.

Along with these three fixes, 1.7.16 gained a couple new extension hooks for extension authors to play with, which add the ability to place menu items in the top-most bar, alongside the User and Support links. You can see this in action with the Review Board Chat extension.

Release notes for 1.6.20 and 1.7.16 are available.

New security releases: Review Board 1.6.19 and 1.7.15

Review Board 1.6.19 and 1.7.15 fix a few issues in the API where users could access certain data they should not have been able to access, if using the Local Sites feature, invite-only groups, or private repositories. It also fixes cases with invite-only groups where the group name and list of private review requests would show up on some pages (though the review requests themselves were not accessible).

These issues do not affect most of the installations out there, but we strongly recommend upgrading anyway. There are no known cases of anyone exploiting these bugs, and in fact we discovered these internally while building new tools to test for security vulnerabilities in our codebase.

There are also some other bug fixes, and important changes needed for extensions that provide their own REST APIs.

See the 1.6.19 and 1.7.15 release notes for more details on these releases.