Jump to >
Review Board 4.0.1: Bug Fixes for WebHooks, Admin, Markdown

Review Board 4.0.1 is a small bug fix release that fixes a few regressions and add some new polish.

Highlights:

  • WebHooks once again dispatch correctly in all configurations.
  • rb-site manage no longer breaks with custom commands in the $sitedir/commands/ directory.
  • All administration database browser pages now load without problems.
  • Extra whitespace in inline Markdown code literals is now preserved.
  • Code highlighting in Markdown is now more consistent between edit and render modes.

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

Introducing Review Board 4.0

We've been working toward Review Board 4.0 for some time now, and we're happy to announce that it's finally here!

This is a big release with a lot of user-facing, behind-the-scenes, and administrative changes. Let's dig into the highlights.

Multi-Commit Review Requests

When working with Git or Mercurial, review requests now track each and every commit that went into the change.

This provides reviewers with the freedom to review code in the way that makes the most sense to them. They can review each commit individually or select a range of commits to see and review at once.

Review requests can be landed to a repository or applied locally in either a squashed (single commit) form, or preserving each individual commit.

Screenshot of the Review Board 4.0 commit list

Support for Python 3

Review Board 4.0 is the first version to support Python 3. As of now, Python 3.6 through 3.9 can be used.

Python 2.7 is still supported. However, we will be dropping support in Review Board 5.0, so we recommend that people prepare an upgrade to Python 3 soon.

If you're an extension author, please be aware that you may need to update your extensions for both Python 3 and Django 1.11 compatibility. See the release notes for more information.

Jenkins Integration

The Jenkins integration can run automated tests and builds any time a new review request is posted or updated.

To get set up, follow the documentation and make sure you set up the Review Board plugin for Jenkins.

Discord Integration

The new Discord integration will post activity and discussions on review requests to your Discord channel. Teams using Discord can now stay informed on what's out for review, and what feedback's coming in.

Screenshot of the new Discord integration in use

Dashboard Overview Tab

The new "Overview" tab on the dashboard will show you all the review requests you have out for review, along with all the review requests that are in your review queue.

Screenshot of the dashboard's Overview section

Publish Review And Archive

There's a new "Publish review and archive the review request" option available when reviewing a change. Click this to publish your review and then hide it from your dashboard until you get a reply.

Screenshot of the Publish Review and Archive option

Read-only Mode

Preparing for some downtime? Administrators can now place their Review Board server in read-only mode. This will prevent people from uploading new review requests, reviewing code, or changing their profiles, while you take care of your maintenance tasks.

New Administration UI

We've completely rewritten the administration UI to give you a better experience. It's mobile-friendly, with simpler navigation, a cleaner administrative dashboard, and screen reader support.

Screenshot of the Review Board 4.0 administration dashboard

Smoother Installation and Management

It's now easier than ever to install optional dependencies for Review Board. We've added several special packages that will help install the right versions of the right dependencies:

  • ReviewBoard[ldap]
  • ReviewBoard[mercurial]
  • ReviewBoard[mysql]
  • ReviewBoard[swift]
  • ReviewBoard[p4]
  • ReviewBoard[postgres]
  • ReviewBoard[subvertpy]
  • ReviewBoard[s3]

Site installation and management has also been revamped, making it easier and faster to create new Review Board sites and to run common management tasks (like search index updates).

Plus...

  • Live video thumbnails for video file attachments
  • Improved support for screen readers (more improvements to come)
  • New extension and API capabilities
  • New automation options for site creation and management

Ready to upgrade?

First, make sure you have a backup of your database and site directory, and have tested an upgrade on a test server.

Please be aware that an upgrade can take time. You should also make sure your extensions have been updated to work with Review Board 4.0.

Then follow the upgrade instructions.

To learn more about Review Board 4.0, please read the release notes.

Power Pack 3.0.5: Fixes for PDF Review

Power Pack 3.0.5 is a small bug fix release that addresses an important issue with PDFs.

PDF Rendering Fixes

Depending on the Review Board setup, a crucial file used to process PDFs would sometimes fail to load. This would result in a blank thumbnail or an empty PDF review UI.

We've tracked down this corner case and fixed it once and for all (hopefully). If you encounter any issues with PDFs, please reach out to us for support. Power Pack licenses entitle you to free support for any and all Power Pack features.

If you haven't upgraded lately...

In recent releases, we've added compatibility with the upcoming Review Board 4.0 release, fixed CSV export for Reports, and improved PDF compatibility.

Now's a great time to upgrade, or to start using Power Pack for the first time.

We're working on Power Pack 4.0, with new authentication features and database import/export. We should have more to show in a few months.

Learn more about Power Pack or upgrade your copy today!

Review Board 3.0.22: Markdown Fixes

Updated May 5th: We've followed this up with 3.0.23 to fix another regression impacting users who hadn't yet upgraded to 3.0.21.

This release fixes regressions in Markdown rendering, introduced by the security fix in 3.0.21.

The following Markdown features have been restored:

  • Syntax-highlighting for code blocks
  • Tables
  • Emoji short codes (such as :thumbsup:)

Any broken Markdown introduced on 3.0.21 will render correctly after upgrading.

See the release notes for more details.