What's New in Review Board

It was brought to our attention today that Review Board 1.5.x and 1.6.x had a security vulnerability involving browser-side script injection in the diff viewer and screenshot pages. We take such things seriously, and are putting out a couple of releases to fix it. We strongly advise everyone to update, especially if you're running a public server.

Review Board 1.5.7 and 1.6.3 have been released. If you're running 1.6.x, just upgrade as normal, but if you're running 1.5.x, you need to upgrade by doing:

$ sudo easy_install -U ReviewBoard==1.5.7

Otherwise, you'll automatically upgrade to 1.6.x.

Thanks to Damian Johnson for letting us know about this vulnerability and providing a patch to fix it.

Review Board 1.6.2 is out. It's a bug fix release that takes care of several issues people have hit. In particular, it should have a proper Apache WSGI configuration for subdirectory installs out of the box, some SCM integration fixes, browser compatibility improvements, and various other things.

We also have a couple bits of new API for those who want to automate review group creation, or archive deprecated repositories.Check out the release notes for the full list.

RBTools 0.3.4 is out. It features an authentication fix for users on RBCommons, fixes for --guess-summary with newlines on Git, solves diff uploading problems on Python 2.7, and adds a new --change-description parameter.

Full release notes are available.

Hot on the tails of 1.6, we have an important security update and bug fix release. 1.6.1 bumps our required Django version to 1.3.1, which contains a number of important security fixes.

It also fixes the counters bug that many people have noticed in the dashboard, where the number of review requests is listed as 0 or a negative number. This was caused by an incorrect default value set when upgrading. Upgrading to 1.6.1 will fix this default, and reset the counts for all users. You should see correct values the next time you use the dashboard.

Release notes are available.

That's a wrap, people. Review Board 1.6 is done, and ready to be installed.

1.6 is a major release, which focuses on better review workflows, faster reviews, access control, generic file attachments, speed improvements, and much, much more. The entire list of features are covered in our release notes.

Before upgrading, we recommend that you back up your database and your site directory, in case anything goes wrong. If you do have problems, you can reach us on our mailing list.

From here on out, we'll be focusing on Review Board 1.6.x releases alongside the upcoming 2.0 release, which will feature support for using third party extensions.

Note: If you're staying with Review Board 1.5.x releases, you will need to be careful how you upgrade to new 1.5.x releases. Instead of the usual:

$easy_install -U ReviewBoard

$ easy_install -U ReviewBoard==version

Where version would be 1.5.6 or whatever version you're upgrading to. Otherwise, you will end up upgrading to Review Board 1.6.

Again, let us know if you hit any issues. A lot has changed in this release, and we'll probably be shaking out a few bugs with the new features over the next few point releases.

Review Board 1.5.6 is out the door, packed with some good fixes and a couple small feature additions. Many of these are fixes backported from the in-development 1.6 releases.

Of note are fixes for caching large diffs/files, fixes for screenshot captions on drafts, performance improvements in syntax highlighting (if you haven't installed recently or upgraded Pygments), and support for Fedora Hosted as a hosting service.

See the release notes for the complete list.

RBTools 0.3.3 is out the door, and it's a biggie. There's fixes and goodies for pretty much everybody.

Git received a lot of fixes in this release, as did post-review itself. One of the biggest set of changes, though, that I'd like to call to attention is Jan Koprowski's wonderful work in rewriting our Clear Case support. He put in a lot of effort and fixed a number of problems with the old implementation. Thanks Jan!

We're hard at work on some large-scale changes to RBTools. The 0.4.0 release is in progress, and it'll form the foundation of the 1.0 release. Soon we'll have a new set of tools that can be used to interact with Review Board, and a Python API that developers can use to talk to Review Board. Exciting stuff! Stay tuned.

For now, see the release notes for the full list of changes.

So.. close..

Review Board 1.6 RC2 is out the door and packed full of fixes, polish, and a few new features that snuck in.

Yes, we may have done a bit more in this release than we anticipated, but it's turned out really well, and will make for a strong final 1.6. We've fixed a number of usability problems (losing changes when leaving the page or accidentally canceling), added some great new features, improving the API, and fixing a good handful of bugs.

Some of the new features include:

• File attachment drag-and-drop. Files can now be dragged and dropped onto the page and uploaded as either screenshots or file attachments. The UI for drag-and-drop has greatly improved.

• Close descriptions. After discarding a review request or marking it as submitted, you can leave a description. You can use this to tell what revision it was committed in, or why the change was discarded. Up to you!
• Confirmation before accidentally losing changes. Ever accidentally hit cancel or navigate away from a page when typing a new description? Now you'll be prompted before you lose what you worked on.

Those are a few of the user-facing improvements made, but there are many improvements for administrators as well, including HTTP Basic Auth support when accessing Git repositories, Perforce stunnel support, and better instructions when things go wrong (new Manual Updates pages).

For the full list, see the release notes.

We're frozen at this point for the final release. Only critical bug fixes will go in. Otherwise, we're working on docs, and should be done with the release soon. So if you're planning to upgrade to 1.6, please give RC2 a try, because it won't be much different from the final 1.6.

One step closer to the finale. Tonight we released Review Board 1.6 RC1, which is full of bug fixes and some fantastic new features.

The highlights of this release are file attachments, private profiles, Private GitHub Organizations, and performance enhancements. Let's break a couple of those down.

The file attachment support makes it possible to upload any type of file to a review request. Tarballs containing important resources to commit that can't appear in the diff viewer, log files, sample data, or anything else. Reviewers can add a comment on the file, which will show up in the review.

Private profiles allow users to prevent other users from seeing their e-mail address on their user page or through the API. The name is also stripped from both locations, though not from review requests themselves. This feature is mostly geared toward open source projects.

There's also many bug fixes and improvements. All of which can be found in the release notes.

We'll be polishing things up, fixing a couple more bugs, and then getting the final 1.6 out the door hopefully soon. Stay tuned, and let us know if you hit any problems!

UPDATE: 1.6 beta 2 is re-released! We had to pull the update due to some PostgreSQL regressions and an annoying visual problem on every page. Whether you downloaded 1.6 beta 2 before or are on 1.6 beta 1, grab this update!

Fresh out of the oven is the new 1.6 beta 2 release. It smells of warm chocolate chip cookies and awesome new features. Some of the key highlights:

• Basic issue tracking. Reviewers can mark a comment as a defect in the code, and reviewers will get a handy UI under the comment for quickly marking that defect as resolved. It's like replying with "Fixed," but with less typing!
• Quick search. Every install now has a search field with quick search enabled. Type some part of a user's name, a group name, a review request summary, or a review request ID, and immediately search results will appear below the box.
• Better review draft banners. The draft banners now stay on screen while any part of a review is being shown. No more hunting for the top of the review for the banner.

There's way more in this release, but those are some of the most common user-visible changes. Much work has been put into this beta, from us and from many contributors, so please check it out.

See the release notes for more information.

We plan for one more beta/RC before the final release with a few more features and fixes.