Review Board 2.0.11 released

Another week, another release for you!

Last week's release of 2.0.10, while otherwise fantastic, didn't play so nicely with certain MySQL configurations. This resulted in some people hitting errors during site upgrade. 2.0.11 addresses this issue, and brings a couple other improvements to the table.

Perforce users may notice that the "Change" field on a review request will now reflect the submitted change number, instead of the original (now useless) change number, once the change goes into Perforce.

We also fixed a crash for users in timezones not local to this planet. Unknown timezones will simply default to the server time.

See the release notes for all the details.

Review Board 2.0.10 released

We have another release for you this week! After a couple productive days of bug fixing and performance tuning, we're ready to bring you Review Board 2.0.10.

This release fixes a couple bugs in the new features from 2.0.9, as well as numerous other bugs that have been reported over the past month. If you're running 2.0.9, we strongly recommend upgrading.

We massively improved the load times for dashboards using the People, Groups, or To Me columns. We've also tweaked the Search box to search summaries a lot faster.

See the release notes for the full list of changes.

Review Board 2.0.9 released

We have a big release today, full of bug fixes, performance improvements, usability improvements, and a couple new features.

We fine-tuned the Markdown-capable text fields, helping them to feel more smooth and natural when typing. This is especially noticeable with lots of text, or for those of you who type really fast.

We also sped up the API, making many operations a lot faster, especially querying for review requests. This will benefit RBTools, the UI, and most third-party applications.

Ever want to copy text from a single column in the diff viewer? Now you can! Just select the text and hit Copy as usual. No more unwanted lines or line numbers messing up your pretty code.

Hate getting e-mails about actions you just performed? You can now turn this off in your My Account page.

Extension writers and API consumers, we've given you some new abilities that should help you better script your custom integrations. Remember to show off what you've written in the Package Store!

There are also nearly 20 bug fixes, including fixes for auto-completing users and groups, Markdown rendering and text escaping, incorrect open issue counts in the dashboard, crashes and rendering issues in the diff viewer when viewing some interdiffs, and much more.

See the release notes for the full list of changes.

Review Board 2.0.8 released

Review Board 2.0.8 fixes numerous bugs around the product, ranging from installation and upgrade woes to usability improvements to repository and patch compatibility fixes.

Just over a week ago, a new version of Python-Markdown was released that broke Review Board on Python 2.6. If you've installed Review Board or upgraded recently, and saw errors mentioning "importlib," you were bit by this. Upgrading to Review Board 2.0.8 will pull down a compatible version of Python-Markdown, fixing this problem.

We've also fixed some breakages in the New Review Request page with commits or patches containing certain types of Unicode characters, as well as Subversion commits that didn't contain a commit message.

Setting up a Bitbucket repository is now a bit easier. Errors are properly reported in more cases, and anything provided during configuration is now validated better.

There are several other changes as well. The full details are in the release notes.

Review Board 2.0.7 released

We've put out a new release of Review Board today, and it's a big one. We've fixed over 30 bugs, improved usability issues throughout the product, and made it much easier to configure the new per-repository incoming webhooks.

There are too many bug fixes to properly summarize, but they affect every user of Review Board. Browser compatibility fixes, repository fixes, API fixes, diff viewer fixes, you name it.

Review Board 2.0 introduced support for closing review requests referenced in pushed commits. This was available for GitHub, Bitbucket, and Google Code, and required providing these services with a webhook URL on Review Board.

If you're using this feature, make note: We've changed how it works, and your old hook URLs will no longer work.

If you want to update your hooks, or are setting them up for the first time, we've made this simple. The repository list in the administration UI will now show a "[Hooks]" link next to supported repositories. Click it and follow the easy instructions. (Note that your Review Board server must be to these services over the Internet for these hooks to work.)

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

Review Board 2.0.6 released

We have another big Review Board release for you today!

Review Board 2.0.6 makes a number of improvements across the product, including:

  • Fixes for numerous Subversion-related problems
  • Internet Explorer compatibility fixes (note that if you use IE, you should use IE10 at a minimum)
  • Extension installation fixes for multi-threaded servers
  • Addition of OK/Cancel buttons on all fields on review requests
  • Workarounds for broken file attachment mimetypes reported by the browser
  • Smarter Markdown escaping
  • The condensediffs command for reducing diff storage requirements now shows the estimated time until completion.
  • and much more!

There are also a few important security fixes. Django just announced new security releases today, which may affect your server, especially if it's publicly accessible. By upgrading to 2.0.6, you'll get these fixes automatically.

If you're running Review Board 2.0.x, we strongly encourage you to upgrade to this release. It should make things run much smoother all around.

See the release notes for more information on this release.

Review Board 1.7.28 released

Our focus for this release was to get a few crucial bug fixes backported from Review Board 2.0.x, and to also help in your migration to Review Board 2.0.x.

First, security fixes. Django just announced new security releases today, which may affect your server, especially if it's publicly accessible.

There are fixes for SVN keyword handling, broken file attachment mimetypes, and the ability to close another user's review requests (if you're an administrator).

We've also backported our optimized diff migration code from 2.0. Now, when you view older diffs, we'll flag them to be de-duplicated, helping to reduce your database size. If you view two revisions of a change and the diff content for a file is the same between both, we'll end up only storing that content once.

You can also run the following to go through and de-duplicate all your diffs, which will help reduce the migration time to 2.0.x:

sudo rb-site manage /path/to/site condensediffs

To upgrade to Review Board 1.7.28, run:

sudo easy_install ReviewBoard==1.7.28

See the release notes for more information on this release.

Power Pack 1.0.4 is released

We've just released a new build of Power Pack, our premium set of features for Review Board. Power Pack includes support for GitHub Enterprise, PDF review, and more.

Power Pack 1.0.4 makes it easier to install a trial license for the first time, or to purchase a full license, removing one of the pains of getting up-and-running with Power Pack.

It also enhances PDF support by fixing several bugs, better handling edge cases, and improving performance.

There are also improvements to Review Board 2.0.x compatibility, and other assorted bug fixes.

See the release notes for more information.

To install or upgrade Power Pack, simply run:

sudo easy_install -U ReviewBoardPowerPack

Just a reminder, we're still taking sign-ups for the new Power Pack Reports beta!

Review Board 2.0.5 released

Over the past few days, we noticed that some upgrades from pre-2.0 to 2.0.4 were failing. This was due to a bug in Django Evolution, a sister project that helps with our database upgrades. We since temporarily pulled the release to prevent any major problems from occurring.

We have since fixed the problem in Django Evolution, have restored 2.0.4, and are now bringing you 2.0.5.

2.0.5 requires the new Django Evolution, fixing the upgrade woes. It also fixes issues reported to us over the past few days with multi-line text fields, re-opening closed review requests as an administrator, and more. We've also added commit IDs/revisions to the list of commits in the New Review Request page.

See the release notes for the full list of changes.

Review Board 1.7.27 and 2.0.4 security releases

We have two new Review Board releases for you tonight. Both fix a couple security vulnerabilities that came to our attention, as well as several other bugs. There are also a few new feature additions.

One of the security vulnerabilities allowed an attacker to construct a URL that would inject custom JavaScript into the page, which could then be passed to a user, allowing the custom code to run in their session.

The other vulnerability allowed users without access to a private review request to construct a URL for accessing original or patched files from the repository, if they knew the right series of database IDs.

Feature-wise, 1.7.27 gained a few of the recent additions to review UIs, support pages, and API that were introduced in 2.0.3.

2.0.4 gained support for uploading parent diffs in the New Review Request page.

If you're upgrading to 1.7.27, you'll need to run:

sudo easy_install ReviewBoard==1.7.27

For the full list of changes, see the 1.7.27 and 2.0.4 release notes.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 pages