What's New in Review Board

Review Board 2.0.8 fixes numerous bugs around the product, ranging from installation and upgrade woes to usability improvements to repository and patch compatibility fixes.

Just over a week ago, a new version of Python-Markdown was released that broke Review Board on Python 2.6. If you've installed Review Board or upgraded recently, and saw errors mentioning "importlib," you were bit by this. Upgrading to Review Board 2.0.8 will pull down a compatible version of Python-Markdown, fixing this problem.

We've also fixed some breakages in the New Review Request page with commits or patches containing certain types of Unicode characters, as well as Subversion commits that didn't contain a commit message.

Setting up a Bitbucket repository is now a bit easier. Errors are properly reported in more cases, and anything provided during configuration is now validated better.

There are several other changes as well. The full details are in the release notes.

We've put out a new release of Review Board today, and it's a big one. We've fixed over 30 bugs, improved usability issues throughout the product, and made it much easier to configure the new per-repository incoming webhooks.

There are too many bug fixes to properly summarize, but they affect every user of Review Board. Browser compatibility fixes, repository fixes, API fixes, diff viewer fixes, you name it.

Review Board 2.0 introduced support for closing review requests referenced in pushed commits. This was available for GitHub, Bitbucket, and Google Code, and required providing these services with a webhook URL on Review Board.

If you're using this feature, make note: We've changed how it works, and your old hook URLs will no longer work.

If you want to update your hooks, or are setting them up for the first time, we've made this simple. The repository list in the administration UI will now show a "[Hooks]" link next to supported repositories. Click it and follow the easy instructions. (Note that your Review Board server must be to these services over the Internet for these hooks to work.)

For the full list of changes in 2.0.7, see the release notes.

We have another big Review Board release for you today!

Review Board 2.0.6 makes a number of improvements across the product, including:

• Fixes for numerous Subversion-related problems
• Internet Explorer compatibility fixes (note that if you use IE, you should use IE10 at a minimum)
• Extension installation fixes for multi-threaded servers
• Addition of OK/Cancel buttons on all fields on review requests
• Workarounds for broken file attachment mimetypes reported by the browser
• Smarter Markdown escaping
• The condensediffs command for reducing diff storage requirements now shows the estimated time until completion.
• and much more!

There are also a few important security fixes. Django just announced new security releases today, which may affect your server, especially if it's publicly accessible. By upgrading to 2.0.6, you'll get these fixes automatically.

If you're running Review Board 2.0.x, we strongly encourage you to upgrade to this release. It should make things run much smoother all around.

See the release notes for more information on this release.

Our focus for this release was to get a few crucial bug fixes backported from Review Board 2.0.x, and to also help in your migration to Review Board 2.0.x.

First, security fixes. Django just announced new security releases today, which may affect your server, especially if it's publicly accessible.

There are fixes for SVN keyword handling, broken file attachment mimetypes, and the ability to close another user's review requests (if you're an administrator).

We've also backported our optimized diff migration code from 2.0. Now, when you view older diffs, we'll flag them to be de-duplicated, helping to reduce your database size. If you view two revisions of a change and the diff content for a file is the same between both, we'll end up only storing that content once.

You can also run the following to go through and de-duplicate all your diffs, which will help reduce the migration time to 2.0.x:

sudo rb-site manage /path/to/site condensediffs

To upgrade to Review Board 1.7.28, run:

sudo easy_install ReviewBoard==1.7.28

See the release notes for more information on this release.

We've just released a new build of Power Pack, our premium set of features for Review Board. Power Pack includes support for GitHub Enterprise, PDF review, and more.

Power Pack 1.0.4 makes it easier to install a trial license for the first time, or to purchase a full license, removing one of the pains of getting up-and-running with Power Pack.

It also enhances PDF support by fixing several bugs, better handling edge cases, and improving performance.

There are also improvements to Review Board 2.0.x compatibility, and other assorted bug fixes.

See the release notes for more information.

To install or upgrade Power Pack, simply run:

sudo easy_install -U ReviewBoardPowerPack

Just a reminder, we're still taking sign-ups for the new Power Pack Reports beta!

Over the past few days, we noticed that some upgrades from pre-2.0 to 2.0.4 were failing. This was due to a bug in Django Evolution, a sister project that helps with our database upgrades. We since temporarily pulled the release to prevent any major problems from occurring.

We have since fixed the problem in Django Evolution, have restored 2.0.4, and are now bringing you 2.0.5.

2.0.5 requires the new Django Evolution, fixing the upgrade woes. It also fixes issues reported to us over the past few days with multi-line text fields, re-opening closed review requests as an administrator, and more. We've also added commit IDs/revisions to the list of commits in the New Review Request page.

See the release notes for the full list of changes.

We have two new Review Board releases for you tonight. Both fix a couple security vulnerabilities that came to our attention, as well as several other bugs. There are also a few new feature additions.

One of the security vulnerabilities allowed an attacker to construct a URL that would inject custom JavaScript into the page, which could then be passed to a user, allowing the custom code to run in their session.

The other vulnerability allowed users without access to a private review request to construct a URL for accessing original or patched files from the repository, if they knew the right series of database IDs.

Feature-wise, 1.7.27 gained a few of the recent additions to review UIs, support pages, and API that were introduced in 2.0.3.

2.0.4 gained support for uploading parent diffs in the New Review Request page.

If you're upgrading to 1.7.27, you'll need to run:

sudo easy_install ReviewBoard==1.7.27

For the full list of changes, see the 1.7.27 and 2.0.4 release notes.

We have two exciting announcements for you today!

Review Board 2.0.3

The first, which you've already guessed, is a brand-new Review Board release. In 2.0.3, you'll find a number of long-requested bug fixes, and some new features.

The highlights include:

• Empty files can now be posted for review.
• Users can now log in with their e-mail addresses instead of their usernames.
• Long, unbreakable lines in the diff viewer now wrap properly in all cases.
• GitLab v6.8+ servers with over 100 repositories now work.
• Far more useful sample crontab files, which are now auto-generated when upgrading your site.
• Counters in the dashboard should finally be fixed!
• Interdiffs are more reliable.
• Lots of Unicode-related bug fixes for diffs and Subversion have been squashed.

All-in-all, there are 23 bugs fixed in this release, and a few more new features we didn't even mention.

See the release notes for the full details.

Oh, and it also links to the new Package Store. And that brings us to:

The Review Board Package Store!

Today, we're happy to introduce the all-new Review Board Package Store, the new home for extensions and software that work with Review Board.

Administrators and end-users can browse the store for software to see what's out there to improve their Review Board experience.

Developers can post what they've made, show it off with screenshots, and let users know what's new with new release announcements.

The store is brand new, so we only have a few things up there right now. If you're a developer writing software that integrates with Review Board on any level, we'd like to encourage you to add it to the store.

We welcome any feedback on the new store. Bug reports, category suggestions, new features, or anything else that would make your life easier.

This evening's release of RBTools 0.6.2 fixes several bugs throughout rbt post and rbt patch.

Mercurial users will find that rbt patch now behaves as expected especially for Git diffs. No need to manually fetch and patch by hand anymore.

We've fixed some breakages that users hit with error messages coming from Review Board under certain conditions, and some compatibility issues with Perforce, ClearCase, and Git.

See the release notes for the full list of changes.

Today's release of Review Board 2.0.2 brings a couple new features, some performance improvements, and several important bug fixes.

Earlier this week, we introduced per-user e-mail options in 1.7.26, which has now made its way into the 2.0 series. You can also now upgrade from a 1.7.26 release to 2.0.2 (sorry about that!).

We made some improvements to the API response times, which will benefit RBTools and much of the Review Board website. Along with this, we've done a lot of work to massively reduce the time it takes to update the search index.

The stars of this release, though, are the bug fixes:

• Clicking links and selecting text in editors now works as you'd expect.
• Replying twice to a review no longer keeps that draft banner sticking around.
• Solved some issues with fetching files on Mercurial repositories.
• Added some bullet-proofing for repository encodings.
• Attempting to reset user passwords no longer results in expired links.
• Lots of fixes to the administration UI.
• Much more!

Subversion in particular got a lot of love in this release:

• Verifying SSL certificates for HTTPS-based repositories now works again.
• The New Review Request page has been updated to properly filter commits based on the selected branch.
• PySVN is now the default backend again, but it's possible to choose your preferred backend.

See the release notes for the full list of changes.