Jump to >
Review Board 1.6.17 and 1.7.10 released

We have a pair of releases today for users of Review Board 1.6.x and 1.7.x. Both contain important security updates, and we recommend updating immediately.

This security vulnerability allows attackers to execute JavaScript under certain conditions. There are no known vulnerabilities in the wild. The latest 1.6.x and 1.7.x releases are susceptible to the flaw. We have released 1.6.x and 1.7.x updates. We recommend that all users upgrade their install to a modern release, particularly if you are running a version prior to 1.6.

Along with the security updates, Review Board 1.7.10 provides some new bug fixes, API enhancements (for comments and screenshots), and UI refinement.

See the 1.6.17 and 1.7.10 releases for more info.

Review Board 1.7.9 released

Some of our wonderful early adopters found a couple bugs in 1.7.8 and some missing API for the new Depends On feature. We decided to get these out before everyone else upgraded.

Thanks early adopters!

Review Board 1.7.9 has an installation fix for some MySQL configurations, new API for Depends On and Blocks fields on review requests, and fixes to the recommended cgit URL for Git repositories.

Release notes are available.

Review Board 1.7.8 released

Review Board 1.7.8 is out, and it's chock full of goodies.

Review requests have two new fields: Blocks and Depends On. Developers can mark that a review request depends on another review request, helping reviewers prioritize what to review first. This goes both ways. A review request depending on another will be shown as being blocked on the other.

We've increased performance across the board. Every page's load times should be reduced. Upload times for diffs will, in many cases, also be reduced, as we won't hammer your repository as hard. This will also help with those using GitHub who may worry about API limits. The dashboard's reloading is smoother and less prone to problems when the connection or server goes down.

Clicking "Get Support" now goes to an all-new support page with some helpful links. If you have a support contract with us, the support page will give you an easy way to contact us with a problem.

You can even change the page that "Get Support" points to, which is handy if you have your own support page in your company.

That's not all. There's several improvements to the extension framework, improved logging for error resolution, and several bug fixes.

See the release notes for the full list of changes.

RBTools 0.5.1 released

RBTools 0.5.1 is out, with many important bug fixes, some new features, and improvements to our API.

We've addressed the bulk of the problems people hit with the new commands in RBTools 0.5.0. In particular, several crashes with Perforce, Subversion and Bazaar have been addressed.

Most of the RBTools commands now have a --repository-type option, which can be used to specify the type of repository, instead of RBTools having to guess. This can also be set in .reviewboardrc by setting the REPOSITORY_TYPE setting. Setting this will dramatically speed up creating and updating review requests, and prevent problems with nested repositories.

You can use post-review --list-repo-types or rbt list-repo-types to see the valid values for this new setting.

To upgrade your copy of RBTools, just run:

easy_install -U RBTools

See the release notes for the full list of changes.

Review Board 1.7.7.1 releassed

1.7.7 introduced a crash during new site installations for some users. We apologize for anyone who hit this. The new release, 1.7.7.1, should take care of this and get you back on track!

Release notes are available.

Review Board 1.7.7 released

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.

RBTools 0.5 released

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.

Review Board 1.7.6 released

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.

Review Board 1.6.16 released

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 released

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.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 pages