What's New in Review Board

We have two new Review Board releases for you today!

Review Board 2.5.17 fixes a handful of issues, including:

• Posting changes containing Unicode characters to GitLab via the New Review Request page
• Regressions in showing closed review requests in the search field
• Crashes when getting a user's full name from LDAP when that name didn't include any spaces
• Creating drafts when editing the caption for file attachments
• Showing replies alongside reviews in the user page's list of published reviews

On top of those fixes, Review Board 3.0.1 has a few additional improvements:

• Capability flags have been added in the API's root resource indicating if JSON patching and symlinks in Git diffs are supported, helping clients make smarter decisions
• A newer user permission was added to let that user see invite-only review groups in the API, which is useful for in-house tools
• Avatar backends provided by extensions should no longer disappear

See the 2.5.17 and 3.0.1 release notes for the full list of changes. If you're upgrading to 2.5.17, please follow the installation instructions in the release notes so you don't end up on 3.0.1.

It feels like yesterday that we wrapped up the first release of Review Board 2.5. Surprisingly, it's actually been 2 years, and we've been busy in that time building the next major evolution of Review Board, 3.0.

That version is here, and with it comes new integrations for third-party services, automated code review support, new review capabilities, better discussions, and oh so much more.

It's a big release. Let's take a look at the major features.

Review Board now talks to your other services (like Slack!)

One of the focuses of this release was to help Review Board work with the other tools you use every day. For this, we've developed a new integrations feature that can talk to all sorts of things, like:

• Chat services (Slack, and soon Stride and Mattermost)
• Continuous Integration services (Travis CI and CircleCI)
• Automated code review services (Review Bot, coming soon)
• Project/task management services (Asana and Trello, also coming soon).

You can create as many integration configurations as you need, directing updates for different teams to different Slack channels, or using different tools for different repositories.

More integrations are coming soon, and extension authors can build their own.

Do more with reviews

Your reviews can contain general comments, which aren't tied to any particular file, and are useful for pointing out higher-level issues with a change (missing screenshots, typos in the description, architectural problems, or anything else).

We're introducing optional issue verification, which ensures an issue can't be resolved and the change landed until the reviewer has verified the fix.

Filed a Ship It! accidentally, or maybe it no longer applies? You can now revoke your Ship It! at any time.

Add some flavor to your comments with Emoji shortcodes. These work on any database (unlike Unicode Emojis), and are largely compatible with Slack and GitHub's Emoji sets.

To share a mockup, meme, or other images in your comments, you can drag-and-drop images into text fields. This works with any Markdown-capable text field in the product.

Need to hand off a review request to another developer? Owners of a review request (and administrators) can now re-assign ownership of a review request.

We've improved discussions and searching

New discussions or updates are highlighted in blue, letting you see what's new since you last looked at the page. If you've already seen everything interested in a review or an update, the box will be collapsed by default, letting you focus on what's most important.

Want to share part of a discussion in chat or in an e-mail? You can easily link to reviews, review request updates, and individual comments through the link icon on the side.

Finding review requests has gotten easier with new support for Elasticsearch and on-the-fly search indexing, ensuring that any new changes made to review requests can instantly be found. (Note that Elasticsearch 2.x is currently required.)

New extension capabilities

Working with the API or extensions? Integrating with your own in-house tools? We have some new toys to play with:

• Review Board now works as an OAuth2 Provider, letting your users easily connect your service to their account in a safe way
• Custom avatar backends for using your company's existing photo database instead of Gravatar.com.
• New fine-grained control for modifying extra_data in the API, and controlling access to data.
• A better way of adding customs fields, with built-in options for drop-downs, checkboxes, date fields, and more.

Did we mention it's a big release?

Whew, that's a lot, and doesn't even cover all the new features in the release.

Ready to get going with Review Board 3.0? We recommend installing on a test server first with a copy of your database, just to make sure it works for you.

Please let us know how Review Board 3.0 works for you, or what you're most excited about. You can also find us on Reddit at /r/reviewboard.

We've just wrapped up what should be the final release candidate for Review Board 3.0. This release polishes up some of the new features and visuals, improves performance throughout the product, enhances the API's capabilities, and fixes a handful of bugs and regressions.

Let's dig in.

Smarter Collapsing of Review and Change Boxes

One of the major goals of Review Board 3.0 is to help you better follow along with any changes and discussions on review requests. To help with that, we've improved when boxes on the review request page start out collapsed.

If there's a new review or update to a review request, a new reply, an issue that needs to be resolved, or pending status updates, the box will be expanded, but if not, it will be collapsed. This really helps to see what's most important when working with large review requests.

Better API Support for JSON in extra_data

Most resources in the REST API provide a special field extra_data, which stores arbitrary JSON data that clients can write to and read from. Until now, clients could only store simple keys and values, and couldn't easily work with structured JSON content.

The API now supports using JSON Patches and JSON Merge Patches to modify extra_data, allowing for complex JSON structures to be stored, modified, and returned.

Better High-DPI Support

Screens are getting better all the time. MacBook Pro "Retina" displays arrived in 2012, and even higher-DPI screens have become more common since. Review Board has shipped artwork for "2x" DPI displays for years, but now we support "3x" and higher, with improved loading and no more transitions from low-resolution to high-resolution graphics. No matter what your display, Review Board will be nice and crisp.

And Loads More

This release is filled with polish and fixes for performance and stability. See the release notes for the complete list of changes, along with installation instructions.

We plan to ship the final 3.0 release this month, based on your feedback from this release. We expect that this will be the final release candidate, and that not much will change for the final 3.0 release, so now's the time to test and send us your feedback.

We're here today with another beta for Review Board 3.0. This introduces a large number of new features. For instance:

• Highlighting new discussions on a review request
• Ability to revoke Ship-Its
• Open issue verification
• Emoji shortcodes
• CircleCI and Travis CI integration
• OAuth2 Provider support

There's much more, but let's break these features down.

Highlighting New Discussions

Any updates, reviews, or replies made to a review request since you last looked at the page are now highlighted with a blue dot and a blue border, helping you to quickly catch up on what's new.

Revoking Ship-Its

Ever leave a Ship It and regret it? Maybe you realized you missed something important, or it just doesn't apply to the change anymore. Now you don't have to live with the regret. Clicking the "X" on the Ship It able to confirm you want to revoke it, and away it goes.

Open Issue Verification

Open issue tracking is a great way of communicating what changes need to be made before a change can go in, but sometimes an issue is so important that you really need to verify its resolution before it's closed.

Now, when filing the issue, you can mark that it needs verification. This will still allow the review request's owner to click Fixed or Dropped, but it won't be closed until you verify their resolution. You're also free to re-open, if you disagree with their change.

This also works well as a "Don't Ship It" feature. Simply never verify the issue until both sides are in agreement on the direction the change must take.

Emoji Shortcodes

Text fields with Markdown enabled now accept Emoji shortcodes. These are codes like :smile:, :thumbsup:, etc. that will show up as Emojis.

CircleCI and Travis CI Integration

Review Board can now integrate with your CircleCI or Travis CI build systems to perform automated tests when review requests are posted. This is a great way of verifying that code going up for review pass all unit tests, browser-based tests, and anything you have set up.

We're still working on the documentation for these, but the Integrations release notes go into the basics. You can find these integrations in the Administration UI -> Integrations page.

And that's just the beginning

• OAuth2 Provider support
• Easy linking to reviews, comments, and replies
• New visuals and infoboxes in the dashboard
• On-the-fly search indexing
• Dynamics reloading of pending status updates
• Performance improvements
• Lots of new extension functionality for the entries (boxes) on the review request page, better custom field support, and other enhancements.

For the entire list of changes, see the Review Board 3.0 beta 2 release notes and Integrations 0.5 beta 2 release notes.

Installing 3.0 Beta 2

Ready to try beta 2? Excellent. Just run:

$ sudo pip install \
    -f https://downloads.reviewboard.org/releases/ReviewBoard/3.0/ \
    -f https://downloads.reviewboard.org/releases/Djblets/0.10/ \
    -f https://downloads.reviewboard.org/releases/rbintegrations/0.5/ \
    --pre -U ReviewBoard

Or, if using easy_install:

$ sudo easy_install \
    -f https://downloads.reviewboard.org/releases/ReviewBoard/3.0/ \
    -f https://downloads.reviewboard.org/releases/Djblets/0.10/ \
    -f https://downloads.reviewboard.org/releases/rbintegrations/0.5/ \
    -U ReviewBoard

Make sure you're deploying on a test server with a copy of your database in case anything goes wrong! You can't downgrade.

What's Next?

Now that we're finished with feature development, we'll be focusing on bug fixes and polish. We plan to have one more pre-release (Release Candidate 1) in just a couple weeks, with a final release to follow shortly after. Aiming for early November.

Your feedback will be invaluable to ensure we have a high-quality final release. If you're able to try beta 2, and have anything to report, please reach out to us on the community support forum or our bug tracker.

We have two new security releases for you today, both fixing security issues reported to us by security researcher Dylan Ayrey. There's also a few bug fixes for GitLab and Subversion, and some improvements for the Administration UI's Security Checklist.

Security Fixes

Dylan reported two vulnerabilities that could be used to execute JavaScript code on a user's behalf:

1. If a text field contains a plain-text javascript: URL, it would be turned into a link that, when clicked, would execute JavaScript on the user's behalf. These links would be pretty long and were easily identifiable, making it less likely that users would be tricked into clicking them (and could not be masked using Markdown links). We've altered the linking behavior to only link certain known types of safe URLs.

2. When clicking Download on a file attachment, the browser may choose to render certain file types in the browser. This includes SVG files, which can include JavaScript. If the media files are served up on the same domain used for Review Board (which is the default behavior), as opposed to a CDN or dedicated domain, then users could be at risk when downloading SVG files.

   We now generate Apache configuration files that add a Content-Disposition: attachment header to all media files, forcing them to download. If you're not using a standard Apache setup, you may need to modify your configuration to add this header.

   You can visit the Security Checklist to make sure this header is being set.

GitLab and Subversion Fixes

Review Board 2.0.31 and 2.5.16 include fixes for working with changes on GitLab. Both fix issues viewing diffs against files containing Unicode characters, and 2.5.16 includes a fix for creating/modifying repositories for self-hosted GitLab servers.

2.5.16 also includes a fix for the New Review Request page when there are problems talking to Subversion repositories. Errors are now reported, instead of the page reporting a generic "Internal Server Error."

See the 2.0.31 and 2.5.16 release notes for more information on these releases, along with upgrade instructions.

Today's release of Review Board 2.5.15 is a small bug fix release taking care of a problem that came up in last week's release of 2.5.14, along with fixing an annoyance some users have hit when loading diffs in the diff viewer.

In last week's release, we made some changes to the Quick Search field and API for security purposes. One of the changes resulted in a crash that could occur using the API, breaking the Quick Search field in the process. If you were bit by this in 2.5.14, an upgrade should fix this for good.

We also fixed a bug in the diff viewer where attempting to switch diff revisions while still loading diffs would result in a crash and a failure to load the new revision.

It's a pretty small release. As always, release notes are available.

We have two new releases for you today, both fixing a couple of undisclosed security bugs, along with providing other bug fixes and feature enhancements.

Security fixes

We discovered an information leak in one of our APIs, allowing a request to be crafted that would reveal some details of review requests otherwise intended to be private. This affects you if you use invite-only review groups or private repositories for access control.

We were also informed of a XSS vulnerability allowing a particular URL to be crafted that would execute JavaScript on your user's behalf.

Both of these issues have been fixed, and additional unit tests have been added to ensure these never regress. We recommend that everyone upgrade to this release at their earliest convenience.

If you locate a security problem in Review Board, please contact security@beanbaginc.com, or file a bug and choosing "Security issue".

New Markdown table support

Review Board 2.5.14 introduces support for GitHub-Flavored Markdown tables. You can now provide tabular data in review request descriptions or in comments.

Commit IDs are now searchable

If you're running Review Board 2.5.14 and have search enabled, you'll now be able to search for review requests based on their commit ID, which is useful if you're using Git or Bitbucket.

This will require a full re-index after upgrade.

And a handful of other fixes in 2.5.14

• Keyboard navigation in the diff viewer should no longer get stuck or fail to navigate to file headers.
• A regression in extension building/packaging when using LessCSS and UglifyJS has been fixed.
• Failure to load files from a repository when viewing diffs no longer results in huge entries in the log files.
• Sending test e-mails should now properly report any errors that come up when communicating with the mail server.
• The styling for buttons on Firefox should now be more consistent.

See the 2.0.30 and 2.5.14 release notes for more information on the release, along with upgrade instructions.

Updated: We had a breaking bug in these packages, so we've put out 2.0.29.1 and 2.5.13.1 releases that fix it. You'll want to upgrade to these instead.

We have two new releases for you today, both fixing a security vulnerability discovered in-house that affects self-installed Review Board servers that make use of private repositories, invite-only review groups, or Local Sites. This vulnerability allowed a URL to be crafted that could expose portions of a diff commented on in other review requests. There are no known cases of this vulnerability being used in the wild.

This vulnerability affects all 2.0.x and 2.5.x releases. Older releases may also be impacted, but those still using 1.7.x or older should upgrade to 2.5.x to continue receiving security updates.

Both releases also now display additional help when encountering a Version Mismatch error page after an upgrade, which can occur when switching from one package installer (such as yum, pip, or easy_install) to another, or when upgrading the version of Python on the system.

Along with this, 2.5.13 now allows credentials to be specified in WebHook URLs, and 2.0.29 includes a performance optimization for the Diff Size column in the dashboard.

See the 2.0.29 and 2.5.13 release notes for more information and installation instructions.

We identified a pretty major regression in 2.5.11, and wanted to quickly get a follow-up release out for you. Some changes to our repository communication code resulted in a crash when forming a HTTP header used for several hosting services. This has been fixed, and things should work well once again.

We've also fixed an issue that could occur when sending e-mails for review requests that modify large numbers of files. We send a X-ReviewBoard-Diff-For header that lists the files, for filtering purposes, but some e-mail servers had issues with the length of this header. We've now capped this to ensure e-mails are sent reliably.

It's a small release, but the release notes are available.

If you missed it, check out the 2.5.11 release notes for all the performance improvements, bug fixes, and features we shipped last night.

We spent the past month going through Review Board and finding ways we could make the product faster and feel smoother. Posting and reviewing changes, being the sole purpose of the product, seemed like a pretty good place to start, so we got cracking.

Along the way, we've improved our support for LDAP, Perforce, and touchscreens, and fixed a handful of bugs.

Faster diff uploads

With today's release of Review Board 2.5.11, we've rewritten our diff parsers to be able to handle very large diffs (10 megabytes in size) in a second or two, using less memory in the process. This used to take a lot longer for some diffs. These performance benefits of course extend to smaller diffs as well.

If you're posting existing commits for review in the New Review Request page, you'll find that what used to take seconds is now nearly instantaneous. We've substantially cut down on the work needed here.

Using Perforce? We've changed how we're managing login sessions and fetching information about files in the repository. On larger Perforce installations, you'll see a huge performance benefit here.

A faster, smoother diff viewer

We've polished up the diff viewer, fixing a lot of perceived and actual performance problems. Large diffs that used to swamp the browser can now be viewed without problems. Resizing the window, which used to feel choppy in some browsers, is now silky-smooth.

Firefox users will especially notice an improvement here, as we've cut down on the work the browser needs to do in order to render the page.

Faster search indexing

Some nasty performance bugs in search indexing have been squashed. Indexes that used to take 30 minutes may now only take 2-5 minutes.

Fixed touchscreen support when reviewing changes

We've fixed a lot of bugs with our touchscreen support. Using an iPad or another tablet, you can now make comments spanning multiple lines of a diff, position and resize the comment dialog, and leave comments without triggering key bindings (oops).

And there's plenty more

• Better support for Assembla repositories
• Fixes for user lookups on LDAP
• API improvements
• Performance and usability enhancements in the dashboard
• Fixes for regressions in the search field
• Stability fixes for extensions and repository communication
• Fixed issues upgrading from Review Board 1.7 or older

See the release notes for the entire list of changes, and let us know how the release is working out for you!