What's New in Review Board

We're inching closer to the finish line with Review Board 1.7 beta 2!

The big highlight is a brand new style for Review Board. We've kept the same basic style since we first introduced Review Board, and decided it was time for a change. The new style is slicker, more polished, more consistent, fits better on the screen, and yet is still familiar.

There's also some fixes for problems people have encountered with beta 1, and of course all the fixes and enhancements in the latest 1.6 release.

This will not be the last beta. We are introducing two new pieces of architecture soon that will allow for really awesome things in future releases. The first is support for writing custom review UIs for different file types (the beginnings of which will land in beta 3). The second is a new JavaScript architecture that extension developers will be able to take advantage of to better integrate with Review Board and plug into our browser-side UIs.

Those who are interested in writing extensions should discuss their needs on the reviewboard-dev mailing list. We have a limited number of hook points right now, and need your help to prioritize.

Full release notes are available.

RBTools 0.4.2 is out!

This releaase is full of bug fixes of many kinds, and is worth upgrading to. There are fixes for Git, Subversion, Mercurial, and Clear Case, along with various other compatibility fixes.

We've added improved debug output, so it'll be easier to diagnose problems when they occur.

Full release notes are available.

Update 25-Sep-2012 2:16AM: There was a small regression with the display of function headers on some comments. No crashes or anything, just displaying content wrong. We've re-released 1.6.12 with this fix.

Review Board 1.6.12 has been released, and is full of long-requested goodies.

We have fixed a number of key issues with parsing diffs. In particular, SVN diffs with property changes no longer totally break, and Git diffs no longer have the useful information like the summary and author stripped away.

We also introduced a new feature by popular request: Incremental expansion for diffs. You can now expand 20 lines at a time or up to the listed function or class, instead of expanding an entire collapsed region at once. You can also re-collapse the expansion. NetApp, Inc. sponsored the development of this feature.

There's also many other fixes and improvements in the release.

See the release notes for the full breakdown.

The first beta for the next big Review Board release is out now. We've just released 1.7 beta 1, which brings with it a number of new and exciting features.

First up is our new extension support. For a long time now, we've been developing a branch with support for loadable extensions that can enhance the features of Review Board. This is finally ready to ship in an experimental form. There's basic documentation on writing an extension, and we'll be working on some sample extensions people can install. As I said, the extension support is experimental, and will likely change and improve over time.

Administrators will see a new administration UI in this version, complete with fancy graphs of what's happening on the server. The administration UI now features an enhanced dashboard with widgets full of various bits of information. New widgets can be provided by extensions (though there's not yet a way to customize which widgets are shown).

Reviewers and developers will better be able to track what issues remain with the new issue summary table. This is a filterable list of issues that have been filed, shown on every review request. You can quickly check what's been opened, discarded, or resolved, and jump to the comment in question. We'll be integrating this more tightly into review request updates in the future.

We have better file attachment previews for certain file types. Right now, this includes text files, which will show snippets of text, and image files, which will show thumbnails.

You can look forward to smaller databases from here on out. Previously, every new upload of a diff would create new copies of each per-file diff, even if it didn't change since the last revision, taking up unnecessary space. No longer! We consolidate these now, reducing the amount of space that's needed. This will only apply to new diffs, though.

For those who have users spread across the world, we now localize dates and times. Users can set their timezone in their My Account page and all dates and times will be based on that timezone.

There are many more changes. You can see the full details in the release notes.

Please note, this is a beta, and not intended for production use. We do recommend testing it and making sure it works for you, though, and we are actively dog-fooding it.

Also, note that Python 2.4 is no longer supported. You will need Python 2.5 or higher. We recommend installing 2.6 or 2.7 to ensure the highest compatibility going forward.

Contact our mailing list if you have any problems, or file bugs for any regressions you find.

Yesterday, we released Review Board 1.6.11, which required the new Django 1.3.2 security release. Unfortunately, as some users have noticed, Django 1.3.2 breaks Python 2.4 compatibility. We have filed a bug against Django, but in the meantime, if you're using Python 2.4, you may need to downgrade back to Django 1.3.1.

To downgrade, first locate the Django-1.3.2*.egg directory in your Python path. Delete that, and then install 1.3.1 by doing:

$ sudo easy_install Django==1.3.1

We are hoping this will be addressed soon, at which point we'll update our 1.6.11 package with a hotfix that requires the new version.

Review Board 1.6.11 is out, with some fixes to regressions in 1.6.10 and further optimizations If you're running 1.6.10, you'll want to upgrade.

We also are now requiring Django 1.3.2. This is a security release that the Django project put out yesterday. We recommend that all Review Board 1.6.x users upgrade to this release. If you're not intended to upgrade to 1.6.11 right away, you can upgrade Django by typing:

$ sudo easy_install Django==1.3.2

You can read more about the security releases.

Full release notes are available.

Welcome to the fastest version of Review Board yet.

1.6.10 is chock full of performance enhancements. It's lighter on your web servers and on your database and noticeably faster. Review requests load almost instantly and the diff viewer renders diffs faster.

You know those "X minutes ago" timestamps? They weren't very cache-friendly, and required a reload to update. Now they're live, even when viewing a cached page. The timestamps everywhere in the UI will update as time ticks away.

There are also some fixes for diffs with very long lines (generally for datasets or minified files), fixes for Mercurial repositories, and fixes for excessive update checks on a review request.

There was a lot of internal work done for these optimizations. We have been dogfooding this pretty heavily, but please let us know if you find any regressions.

Full release notes are available.

Another day, another release! We've been working to shake out the bugs from the hosting service change, and following the ol' open source mantra, "Release early, release often." Fixing regressions is important to us, and the reports people have been filing have been very helpful, so we'll continue to do this quick releases as long as necessary.

That said, things are looking pretty good, and our test suite is only growing.

Tonight's release fixes some problems some users have had with GitHub private repositories, a regression in key input on the diff viewer page, and creating new review requests not tied to a repository.

We also now log when you're getting low on GitHub API calls remaining, as determined by GitHub's rate limiting system.

Release notes are available.

Thanks to people's quick feedback, we've made some important fixes to the new hosting service support. This covers the configuration of repositories, and some fixes in error reporting and diff uploading using the New Review Request form with GitHub. We recommend that everyone on 1.6.7 updates to this release.

Release notes are available.

Today we bring you a very important release, especially to those of you on GitHub. Please read this post carefully.

We've been doing major work on new hosting service integration support in Review Board. This provides, for the first time, direct knowledge of repository hosting service APIs and account linking, removing the need for copy-and-pasted API tokens and hacks.

This feature is critical for GitHub users, as sometime soon (likely this month or next), GitHub will be switching off their old v2 API (which Review Board has traditionally used to fetch files) and moving to the new v3 API.

If you are a GitHub user of any sort, you must upgrade! Failure to do so will mean your repositories may not work soon.

Once you have upgraded, you will need to go into each configured repository and set it up again as a GitHub repository. This will have you link an account on GitHub to your repository. Unfortunately, this is not something we can automate, but you shouldn't have to do this again. Once you've finished, you should be set for when GitHub terminates their old API.

This is a large change to Review Board, and we have been careful to test it thoroughly, but lab testing and real-world testing don't always show the same results. If you have any problem with your repository, please contact us.

If you feel more comfortable, you can create a new, temporary repository, link it to your account, and ensure that works. If there is a problem, report it, and you can continue to use your old repositories until GitHub switches off the API.

In the future, this new support will allow us to provide a more seamless repository configuration process and features specific to hosting services, as well as deeper bug tracker integration.

Along with the hosting service code, this release also provides compatibility with Plastic SCM v4.0, makes the max diff size limit configurable, and fixes a few bugs in the product.

See the release notes for more information.