A few regressions were noted in RBTools 0.4.0. In particular, Python 2.4 support broke, and the --diff-filename= option broke with STDIN and --username and --password provided.

These have been fixed, and we've released 0.4.1. Give it a try, and please let us know of any more regressions.

Release notes are available.

A couple small bugs crept in to 1.6.4 that affected users sorting by the Review ID column in the Dashboard and the saving of cache backend settings. We've put out a small 1.6.4.1 release that fixes these problems.

Release notes are available.

Review Board 1.6.4 is out the door!

This is primarily a bug fix release, but with a few added goodies.

Administrators trying to move Review Board to a different type of database (for example, SQLite to MySQL) can now use new database dumping and loading management commands. These will store the database in a database-agnostic format and load them back in. It's not a fast process, but should make life a lot easier in these situations.

Some changes were made to the webapi for compatibility with future RBTools releases. The 0.5.0 release will end up requiring at least Review Board 1.6.4.

Along with these, there's a new hosting service entry for Codebase HQ, issue tracking checkboxes in the Review dialog, and diff viewer improvements for Objective-C++ .mm files. And, of course, a large number of bug fixes.

Release notes are available.

RBTools 0.4.0 is out! There's some great improvements that some of you will like, but more than anything, it's the first step toward a brand new, more exciting RBTools.

The highlights of 0.4.0 include:

• Most command line options can now be set automatically in .reviewboardrc files. This includes such things as the branch, Perforce configuration, --submit-as, and more.
• Added a -g (--guess-fields) that works as a convenience for --guess-summary --guess-description.
• The system's HTTP(S) proxy can be disabled with --disable-proxy.
• Numerous other bug fixes.

One of the big changes for this release is internal. We're starting to build a Python API that will talk to Review Board servers, which would be usable by other applications. It's not close to ready yet, but a couple of the large parts have been done for this release. In particular, the SCMClients, which talk to the various tools like Git and Subversion, have been refactored out into reusable classes. Down the road, it will be possible to have third-party modules that extend post-review's client support.

Before long, we'll be dropping support for the old Review Board API found in Review Board 1.0 and early 1.5 versions. This should be considered the last release to support the old API.

Release notes are available.