What's New in Review Board

Review Board 1.7.7 is out. It has a couple new features for admins, a series of bug fixes, and some worthwhile performance improvements that you shouldn't miss.

We did some profiling and found a couple common cases we were able to speed up considerably. The Dashboard and All Review Requests pages should be faster, as should any changes involving parent diffs.

There's also some additions in here that set things up for the upcoming PDF review extension. If you're interested in giving that a try, sign up for the beta..

Release notes are available.

The next major evolution of RBTools has been released!

RBTools 0.5 is a major undertaking that we're sure is going to make a lot of you happy. This release introduces several new scripts for working with review requests from the command line, and a brand new Python API for writing your own scripts and applications.

rbt

The new rbt tool serves as your launching point for any new tools that work with Review Board. It works like git, in that it takes a subcommand and options, which may do anything from post a new diff to query the statuses of your pending review requests. Here are the one we provide now:

• rbt attach - Attaches a file to an existing review request.
• rbt close - Closes a review request (either as submitted or discarded.
• rbt diff - Shows the diff that would be uploaded to a review request. This works like the old post-review --output-diff.
• rbt patch - Takes the diff from a review request and applies it locally to your tree. Useful for open source projects!
• rbt post - Posts or updates a review request. This is your new post-review script.
• rbt status - Displays all your pending review requests for the repository you're running this from.

We plan to add more in time, and to refine many of these. It's still largely considered a beta, but we'd love the feedback!

Now you may have noticed rbt post above. We're deprecating post-review, and plan to remove it sometime before RBTools 1.0. A lot of you probably are pretty used to typing post-review now, so now's a good time to start building new muscle memory!

Otherwise, post-review is pretty unchanged from 0.4.x, so you shouldn't run into any big regressions.

Python API

All of our new scripts make use of a central Python API that we have developed. This was written to make it easy to talk to a Review Board server. It supports our entire web API. We have a whole tutorial and reference guide on the new Python API.

Those of you maintaining your own forks of post-review or your own post-commit hooks or utility scripts should start moving over to the new API, give it a spin. Let us know how it works for you.

We still have a lot to do, but we hope this release is as exciting and useful to all of you as it has been to us.

We had a number of people contribute to this, but in particular I want to thank and congratulate Steven MacLeod on this release. Steven is a former UCOSP and Google Summer of Code student and the new lead developer for RBTools, and has done a fantastic job putting all this together.

Release notes are available, and cover all the new additions and the bug fixes that went into this release.

And tonight we have another release! One that is sure to please you Perforce administrators out there.

Review Board 1.7.6 has a number of bug fixes, some API additions, and a couple new features. One of those features is Perforce ticket-based auth support. It should now be dead-simple to get ticket-based auth working for all your repositories. Just check a box in the repository configuration, and you're good.

We've also bumped the minimum version of Django to 1.4.5, which is the latest security release in the 1.4.x series.

See the full release notes for all the changes.

Django just released a couple of new security updates, and we wanted to get them into your hands as fast as possible.

We've released Review Board 1.6.16. This uses the new Django 1.3.7 as the minimum required version. We have also backported several bug fixes from the Review Board 1.7 releases, which should particularly help with those of you who have had any crashes in the diff viewer. Well worth upgrading to.

See the release notes for the full list of changes.

Review Board 1.7.5 is out. It fixes a few, mostly small problems people have hit, and a major compatibility change with the newly released django-pipeline 1.3.

If you installed 1.7.4 in the past week, you may have had a crash when accessing most pages, possibly saying "CompilerError." This was due to some compatibility changes in django-pipeline 1.3 that we still need to investigate. However, that release also dropped Python 2.5 support, which means we'll be requiring 1.2.24 from here on out. My apologies to any packagers that this affects.

See the release notes for the full list of changes.

This week's release of Review Board 1.7.3, while otherwise awesome, had some regressions for users of Internet Explorer, old versions of Firefox, and some Windows users generating diffs.

1.7.4 fixes these issues. If you're using 1.7.3 at all, you should certainly upgrade. It's a small release, but an important one.

Release notes are available.

Another great release tonight! RBTools 0.4.3 is out, and fixes a handful of bugs and introduces some new features.

This release works with the new Review Board 1.7.3 release to better show moved files in diffs when using Perforce. It also adds the beginnings of Bazaar support. Along with that, many bug fixes to common and not-so-common problems people have hit.

This is probably the last big release in the 0.4.x series. Very soon, we will be releasing 0.5, which puts us on the path to the elusive 1.0. The 0.5 release introduces the beginnings of the Python API for working with Review Board, and a handful of useful command line tools for working with Review Board. This will in time replace post-review, though that will stay around in the 0.5.x releases as people migrate over to the new commands.

See the release notes for more information.

Review Board 1.7.3 is released! This is mostly a bug-fix release, with a new feature for optionally e-mailing when review requests are closed, and some compatibility improvements.

Several of the bug fixes in this release were fixed by our new batch of students joining us from UCOSP this semester. Congrats on your first shipped code in Review Board!

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

Review Board 1.7.2 is out, with a number of fixes to commonly encountered problems found in 1.7.x, and a few new features.

Some users of 1.7 and 1.7.1 encountered some confusing problems when attempting to upgrade from an older release, due to some of the upgrade instructions not always showing up, and due to confusing errors when trying to upgrade using the now unsupported Python 2.4. This release should make the process much more clear.

There's also a good number of fixes for various other bugs throughout the product.

On top of this, three new features!

• VersionOne bug tracker support was added.
• New-style SSL-backed Perforce repositories are now supported (please read the release notes for details on getting this working).
• Files moved in a Perforce repository using "p4 move" and posted with post-review in the upcoming RBTools 0.4.3 will now show up as moved in the diff viewer in a simpler, easier to read view.

See the release notes for more information.

There were a few headaches some of our users hit when upgrading to Review Board 1.7. Various edge cases we didn't see during testing, and we feel terrible about that. However, thanks to some great debugging and excellent feedback on our mailing list, we've been able to identify and fix some of these problems.

Review Board 1.7.1 is mostly a bug fix release that takes care of the following problems:

• Upgrading very old (1.0/1.5/early 1.6 sites).
• Upgrading sites using PostgreSQL.
• Lack of documentation covering an important part of setting up the new static media configuration.

There is, however, a new feature from one of this winter's UCOSP students, Karl Leuschen, which introduces a checkbox when configuring a GitHub repository that automatically associates the configured SSH key with the repository, simplifying setup. We plan to bring this feature to other hosting services later.

Full release notes are available.