What's New in Review Board

Tonight we put out a small bug fix release that fixes a few small bugs, including some dashboard rendering issues when adding/removing columns. It also allows support for handling log rotation, so that the web server doesn't have to be restarted in order to resume logging after a log rotate.

We're focusing our efforts now on wrapping up the 1.5 release. Beta 2 will be out soon, and barring any regressions, we likely won't put out any more 1.0.x releases for a while.

More information can be found in the release notes.

We've been fortunate enough to participate once again in the Google Summer of Code. This is an opportunity for students from around the world to work on interesting open source projects. This is our second year participating. Last year's efforts resulted in the upcoming Move Detection in the Diff Viewer, whitespace display toggling, Policy rule support (coming in probably 1.7), WebHooks (coming in 1.6), and Eclipse IDE integration.

This year we've selected three students with very exciting proposals:

• Distributed Version Control System support to allow for reviewing patch sets and checking remote branch status.
• Identifying repeated changes in a diff and summarizing or collapsing them, making it easier to review code where a function or variable has been renamed or changed in a consistent way throughout several files.
• Work on the Extensions branch to help get our in-development Extensions support into better shape for a release.
• A Linux installer making it easier to install Review Board on a variety of Linux distributions and keep it up-to-date.

We'd like to thank everyone who submitted a proposal this year, and we'd especially like to thank Google for once again accepting us into Summer of Code! Finally, we'd like to welcome our students into the project this year. It should be a great Summer.

It's release night! We have yet another one for you. We just released Review Board 1.0.7, which is a fairly small release with some further performance improvements for the dashboard.

After getting feedback from users of the 1.0.6 release, we discovered that, while the dashboard speed improvements did make a difference, the dashboard was still slower than it should have been on large deployments. We investigated this and found some further improvements we could make, which have massively reduced loading times on these large deployments.

It also restores compatibility with the betas of Django 1.2. Careful readers might note that we announced compatibility in 1.0.6, but as luck would have it, the following day we were broken again. We fixed the latest breakage, and hopefully won't see another.

More information can be found in the release notes.

Tonight we released the final build of RBTools 0.2.0. The is the first official stable release of RBTools and is compatible with both Review Board 1.0.x and the upcoming 1.5 release.

RBTools is a collection of a tools for working with Review Board. Right now, there is only one tool, post-review, which makes it easy to create and update review requests. It's useful for end users, automation, and as a way to integrate with other products.

Users of previous versions will find some good bug fixes in the final release. In particular, a couple crash bugs and a UTF-8 encoding bug in RBTools 0.2 RC 1 have been fixed.

We have many plans for future versions. Some new tools will be added for querying review requests and otherwise working with review requests. RBTools will also provide a Python module, allowing custom tools to be written. These new tools will likely require Review Board 1.5.

More information can be found in the release notes.

We have a pretty good point release out for everybody running Review Board 1.0.x. We just put out 1.0.6, which, among other things, has some huge performance improvements for the Dashboard, and what we believe is a solution to that pesky stale settings bug many of you have encountered.

The Dashboard has never been the fastest part of Review Board, and some companies have hit some serious speed issues with increased loads. During the 1.5 release cycle, we've looked hard into the problems plaguing the Dashboard, and have made many performance improvements. Not only do these increase loading times of the Dashboard, but it reduces stress on the web server and database server, which should contribute to overall performance of the site.

The stale settings bug has been a problem for many users. Depending on the server setup, setting changes in the Administration UI wouldn't necessarily take effect for all users until the web server was restarted. This has been an elusive problem, but we think we've identified a couple subtle bugs in the caching code used to synchronize the settings across across the web server threads/processes. We're going to watch carefully over time to see if new users still hit this bug, but for now, we think we've fixed it.

There are several other fixes as well, such as for the broken screenshot comment thumbnails problem some users have encountered.

More information can be found in the release notes.

Happy Valentines to everyone with someone special to share the day with. For the rest of you, spend the day with the all new Review Board 1.5 beta 1 release! Because Review Board <3 you.

What happened to 1.1, you may ask? The original intent was for the 1.1 release to be fairly small, with just a few new features. However, after our 1.0 release, we received a surge of new feature requests and enhancements, and had a few of our own that we wanted to get in as well. So over time, the release grew, and we decided that 1.5 was more appropriate.

There are many new, exciting features in this release, and we hope people will provide some good feedback on them as we get closer to the final 1.5 release. Among them are:

• Move detection in the diff viewer. The diff viewer will now show whether a block of code has moved within the file, instead of just showing inserts/deletes. This feature is still young and may need some fine-tuning before release, but it's already proving to be a powerful aid in code review.
• Function/class headers in the diff viewer. When looking at a collapsed section of a diff, the diff viewer will now show the function or class that most closely precedes that section, in order to give you some idea as to where you are in the file. These headers are also shown in the comments on a review and in the HTML e-mails. This supports C, C++, C#, Objective-C, Java, JavaScript, Perl, PHP, Python, and Ruby files.
• Screenshot drag-and-drop for HTML 5-capable browsers. Newer HTML 5-capable browsers, such as Firefox 3.6, support the ability to drag-and-drop files from a file manager into a webpage. We can take advantage of this to allow users to upload screenshots by drag-and-drop. This has so far only been tested with Firefox 3.6, but we'd welcome some help in testing with other newer browsers.
• Support for private GitHub repositories. It's now easy to link up a Review Board installation with a private GitHub repository. See the release notes for more information.
• Speed improvements in the diff viewer and dashboard. Much work has been done to reduce the overhead in the diff viewer and dashboard, leading to speed improvements in many cases.

More information can be found in the release notes.

RBTools 0.2 RC 1 is now available for download. This is one of the last releases before the final 0.2 release, and everyone should upgrade to it soon, particularly if you're using the Review Board 1.1 alphas or nightlies.

Git users will benefit from the improved branch detection in this release. Previously, diffs were generated based on "master," regardless of whether the current branch was even based on "master" or whether "master" was tied to the right origin. Now post-review properly determines what the branch is based on. The new --tracking-branch option can be used to explicitly specify the branch as well.

post-review has gained a new --diff-filename option for specifying a diff file to upload, instead of generating a new diff. This can be useful for automation and third party integration purposes. Passing "-" as the filename will cause post-review to read from stdin.

There are also various bug fixes and compatibility improvements for Mercurial, Subversion, and Perforce.

This release is essential if you're using the 1.1 alphas or nightlies. It has some API compatibility changes that will be needed for one of the upcoming Review Board betas.

Full release notes are available.

Just in time for the holidays, we've released Review Board 1.1 alpha 2. This is a pretty significant release with many new features that users have been asking for for some time. We'd like to get this release heavily tested, but remember that it is an alpha release, and is best set up on a non-production system.

Some of the new features in this release include:

• HTTPS Subversion repository support
• SSH-backed repository support for Bazaar, CVS, Git, Mercurial, and Subversion
• Amazon S3 storage for screenshots
• Captchas for new user registration, to reduce spam

Full release notes are available.

Going forward, we're hoping to have a beta out by mid-December. This may be pushed out to January, depending on holiday schedules and how much testing this release gets. We may sneak another feature or two for the beta, but after that the focus is on a solid release.

We'd also like to dedicate this release to Vinay Venkatesh, a good friend and co-worker of ours who passed away earlier this month. He was a long-time supporter of the project, helped us keep our sanity during difficult times, and helped with ideas and suggestions for the project. Thanks for everything, Vinay.

Tonight we released Review Board 1.0.5, a small bug fix release that fixes a handful of issues reported in some installations.

The main issue fixed that affected most people was that a previous version of Djblets, one of our dependencies, broke compatibility with Internet Explorer 6 and up. Review Board 1.0.4 required this version, meaning that users of Internet Explorer faced problems with anything involving a text area. We now require the newer version, 0.5.5, which resolves this problem.

Binary files and diff expansion were broken in previous releases, but are now fixed in 1.0.5. There are a handful of other fixes for Active Directory, the administration UI, and large bug numbers.

The one new "feature" in this release is that we now inform users on the New Review Request page about the existance of post-review, with a brief description and a link to the documentation. We're hoping more people will start to use post-review, improving their experience with Review Board.

Full release notes are available.

Updated: A bug was found making the New Review Request page unusable. A 1.0.5.1 release has been made to fix this issue.

An announcement was made yesterday that the Django 1.0.3 and 1.1 releases contained a security vulnerability that may impact some users. We recommend that users upgrade to the latest version of Django immediately. This is especially important to open source projects with public Review Board servers.If you're running an older Review Board server with Django 1.0.x, you should download Django 1.0.4 and install it. If you're running a newer version, you can upgrade by typing:

easy_install -U Django

Once you've upgraded, re-run rb-site upgrade on your installed Review Board sites.