What's New in Review Board

RBTools 2.0 is out, bringing compatibility improvements and new features for all users. The biggest improvement is the support for Review Board 4.0's upcoming multi-commit review requests.

Multi-Commit Review Requests

Review Board 4.0 beta 1 is coming in the next few weeks, and with RBTools 2.0, developers will be able to post a series of commits to a review request so that they can be reviewed individually or as one squashed change, depending on what the reviewer chooses to do.

Those changes can also be landed, preserving their history or squashing them back into a single commit.

To stay with the old behavior and squash the commits before posting to a review request, you can pass --squash to rbt post or rbt land (or set SQUASH_HISTORY = True or LAND_SQUASH = True, respectively, in .reviewboardrc).

This is available for both Git and Mercurial, and will require Review Board 4.0.

RBCommons users will receive multi-commit review request support in 2021.

Custom Certificate Authorities

If your Review Board server uses a self-signed certificate backed by an in-house Certificate Authority, you can now configure RBTools to recognize it through the --ca-certs, --client-key, and --client-cert options (or CA_CERTS, CLIENT_KEY, and CLIENT_CERT in .reviewboardrc).

Easier Repository Setup

rbt setup-repo has been redesigned to better help people configure their local repositories to connect to Review Board. It offers a more helpful guided setup, making it easier to find the right repository and generate your .reviewboardrc file.

Default Branches in Git

RBTools now understands the init.defaultBranch configuration for Git, helping you transition your primary branch from master to something like main.

Better Mercurial Integration

Compatibility issues are fixed, repository detection is faster, and custom scripts can benefit from performance improvements by connecting RBTools to the Mercurial command server.

And Better Perforce Integration

RBTools can work with a wider mix of configurations utilizing SSL and brokers.

There's also a new reviewboard.repository_name Perforce counter that can tie a depot to a Review Board repository, which can be used if .reviewboardrc isn't an option.

Plus...

• Variety of improvements for Python 3 compatibility (including support for Python 3.9).
• Additional Git arguments for fine-tuning rename detection.
• Custom formatting for rbt status, which is useful for scripting.
• rbt land and rbt patch now accept a review request URL, instead of just an ID.
• rbt patch can print a patch from a review request without needing a local copy of the repository.

See the release notes for more information, or download RBTools 2.0 today.

Power Pack 3.0.3 is built to get you ready for Review Board 4.0 and for licensing changes in Power Pack 4.0. Plus, it fixes bugs and improves compatibility across the product.

Review Board 4.0 Compatibility

Review Board 4.0 will soon be out in beta, and you'll want to make your transition as smooth as possible.

Power Pack 3.0.3 works today with your current Review Board and with the Review Board of tomorrow.

(Not literally tomorrow. Sorry to get your hopes up.)

New Licensing Format

We're moving to a new license format, which will open the door to features we have planned for Power Pack 4.0. By upgrading now, you'll be ready for the new licenses when they're ready, giving you a head start on Power Pack 4.0.

Bug and Compatibility Fixes

• Installation is a bit easier on most Linux systems
• We've further enhanced rendering of PDFs
• Prepared for future GitHub Enterprise authentication changes
• Improved compatibility with AWS CodeCommit and Bitbucket Server
• Stopped a crash when exporting CSV files for some reports
• Fixed enabling or disabling some feature checkboxes, for customizing your install

Update Today

Prepare for tomorrow by upgrading to Power Pack 3.0.3 today.

To upgrade or install for the first time, see the installation instructions.

The new Review Bot adds new automated code review tools for Python source code, and brings some major enhancements to help you get the most out of automated code review.

Plus compatibility with the upcoming release of Review Board 4.0.

Introducing doc8 and pydocstyle

If you're a Python developer trying to keep your project's documentation in check, Review Bot can help you out through the new support for doc8 and pydocstyle.

doc8 checks your ReStructuredText-based documentation (used by Sphinx or docutils) for common problems, such as syntax or whitespace issues.

pydocstyle checks the Python side of your documentation, making sure your function, class, and module docstrings are all there and don't have any issues.

Automatically drop old issues from Review Bot

Review Bot can now be configured to drop any older issues it opened before it runs any tools again. No more massive lists of open issues to close every time you post an update to your change.

This can be configured for each automated code review tool individually.

Manually run and re-run tools

Tools can now be set to be run manually, instead of every time a new change is posted. This is especially useful for in-house tools that may take an extremely long amount of time to complete.

If any tool has failed to run for any reason, you can also re-run it with the click of a button. No need to re-upload your change.

(This requires Review Board 3.0.19 or the upcoming 4.0.)

Simpler configuration for tools needing the full repository

Some tools (such as clang) require a full copy of the repository. This used to require telling each worker about each and every repository a tool may need to access.

Workers can now fetch this information directly from Review Board, if configured on the worker. This requires that the worker has access to the path configured for the repository in Review Board, and any SSH keys needed.

New capabilities for tools

Custom tools can now leave general comments on a review request, not tied to any particular change or file. This is useful if the comment is more about process and policy, or about the description or testing performed, rather than code.

Get Started

Review Bot is compatible with Review Board 3 and 4, and is an easy upgrade. Just follow our simple instructions.

To learn more about this release, see the release notes.

Review Board 3.0.18 is the culmination of months of work in just about every area of the product. There are compatibility updates and bug fixes, better performance, tweaks to usability, and improvements to extensibility.

Better Compatibility

• Dependencies have been updated to make installation easier on some systems.
• GitHub now uses Personal Access Token instead of a password when linking accounts. This will be required by GitHub in November.
• Bitbucket's Mercurial support was removed.
• GitLab commit browsing works better for public repositories, and is more helpful when things fail for private repositories (caused by GitLab API issues).
• Perforce SSL/stunnel repository setup is now rock-solid.
• Subversion filenames with certain special (but uncommon) characters can now be found.
• NIS authentication works again!

Better Performance

• Communicating with repositories over SSH is much faster.
• Need to migrate old pre-3.0 diffs using the condensediffs command? It should take a lot less time now, especially on MySQL, and you can schedule small batches of migrations over a period of time.

Better Usability

• We've polished mouse interaction in the dashboard and keyboard interaction in dialog boxes.
• Very long lines in diffs are now safely broken up in the diff viewer.

Better Stability

• Broken extensions are less likely to interfere with the rest of the product, and can more easily be diagnosed.
• The Markdown review UI doesn't get stuck anymore showing only rendered content.
• Fewer crashes from edge cases throughout the product.

Plus...

• The repository API lets you create/manage repositories on hosting services and store custom metadata.
• We've bumped up versions of the tools used to process JavaScript and LessCSS for custom extensions.

See the release notes for all changes in this release.

To keep up with what's happening every week in the land of Review Board, be sure to follow our ChangeLog posts on Twitter, Facebook, or Reddit.

Django released versions 2.2.13 and 3.0.7 today, fixing a couple of security issues. You can see their announcement for the issues addressed.

We maintain security-hardened builds of Django 1.6.11, the version series we use for Review Board 2.0 through 3.0. We've put out a new Django 1.6.11.9 release that contains these fixes.

To upgrade to this release, run:

$ pip install -U https://downloads.reviewboard.org/releases/Django/1.6/Django-1.6.11.9.tar.gz

Or:

$ easy_install -U http://downloads.reviewboard.org/releases/Django/1.6/Django-1.6.11.9.tar.gz

You can always keep up on the latest Review Board security announcements by subscribing to our Official Announcements mailing list, joining our Subreddit, or following us on Twitter.

Today's release of RBTools 1.0.3 is a big one, featuring enhancements for Mercurial support, a vastly improved commit editing experience when landing changes, and several compatibility fixes for Python 3 and various types of repositories.

Landing Commits on Mercurial

rbt land now supports landing commits on Mercurial repositories.

You can land a local change from a Mercurial branch or bookmark, or a remote change from a review request. This will first verify that the change has been approved on Review Board before allowing it to land. Once approved, a new merge commit containing the information and URL of the review request will be placed on your destination branch.

This can also close the branch/bookmark being merged in on your behalf. See the documentation for details.

Improved Commit Editing

Patching a commit with rbt patch -c, or landing a commit with rbt land -e has always let you edit the message for the commit, but the experience was sub-par.

Now RBTools will mimic Git or Mercurial's standard editing environment, helping your editor show the syntax highlighting or line length limits it would normally show.

Deleting all text in the editor and saving will cancel the patch/land operation.

You can also set a custom editor when working with RBTools by setting the new $RBTOOLS_EDITOR environment variable.

Compatibility Fixes

We've fixed a number of Python 3 compatibility issues. These largely centered around:

• Changes in Python 3.8
• Windows environment differences
• Editing or processing commits containing non-ASCII characters
• Normalizing URLs and paths for Subversion
• Loading in Perforce metadata
• Passing --help as the last argument

There's also a fix for looking up available Git remotes for a branch when a tracking branch isn't set. Thanks to Joshua Olson for this fix!

See the release notes for the full list of changes.

Review Board 3.0.17 provides compatibility fixes for GitHub (which addresses the deprecation warning e-mails that GitHub may have sent you), removes some legacy hosting service options for repositories, and fixes a few bugs with repository configuration.

GitHub Changes

GitHub has deprecated some old APIs and methods for authenticating with those APIs, which Review Board has historically used. You can read more about this deprecation in last week's ChangeLog post on the Beanbag Blog. If you've linked your GitHub account to Review Board, you may have received e-mails from GitHub warning you about this deprecation.

We've updated how we authenticate with the API in this release, which will keep you from being bombarded with those e-mails every few days. We'll be working to address more of the deprecations in coming releases, changing how we link new GitHub accounts.

You will not need to re-link your GitHub account. The changes are all automatic.

Removing Legacy Hosting Services

We've cleaned house a bit, removing Google Code and Fedora Hosted from the repository hosting services list. These services have been gone for a long time, but we've kept support for the few users who have repositories with review requests sitting around. These are now hidden for any new repositories.

Keeping Up-To-Date

See the release notes for all changes in this release.

To keep up with what's happening every week in the land of Review Board, be sure to follow our ChangeLog posts on Twitter, Facebook, or Reddit.

Today's release of Review Board 3.0.16 brings some key administrative enhancements to the API and to the repository configuration page, plus an assortment of bug fixes.

Updating users via the API

The User API now allows user information, such as full names and e-mail addresses, to be modified. Users can modify their own user information, and administrators (or users with the special auth.change_user permission) can modify any user's information.

Administrators can also deactivate or re-activate user accounts by setting the is_active flag on users. This can help organizations keep the list of active users up-to-date as personnel changes.

Repository form and architectural updates

The repository configuration form has received a few user-facing improvements, and a whole lot of behind-the-scenes improvements.

• Browsers should no longer fill in the Username and Password field with your Review Board login credentials
• Inactive or removed users that were added to a repository's access control list no longer cause problems when saving the repository
• Custom extra_data values set via the API or extensions are no longer lost when saving repositories
• Repository types provided by extensions can now provide their own configuration forms, instead of using the hard-coded fields like Path and Mirror Path.

There's actually a lot that has changed here over the past few months, and we're particularly interested in hearing about any unexpected changes in behavior.

We'll be taking advantage of this new functionality in the coming months as part of work on a brand-new ClearCase implementation.

Compatibility and bug fixes

We've improved parsing of Subversion diffs, communicating with Subversion repositories hosted on Beanstalk, and improved performance and reliability when handling Bitbucket WebHooks.

We also have fixes for search indexing of users, Dashboard sidebar counters, and dependency conflicts on new installs.

See the release notes for all the changes in this release.

To keep up with what's happening every week in the land of Review Board, be sure to follow our ChangeLog blog on Twitter, Facebook, or Reddit.

Django released the versions 2.2.4, 2.1.11, and 1.11.23 today, fixing a handful of security issues. You can see their announcement for the list of issues addressed.

We maintain security-hardened builds of Django 1.6.11, the version series we use for Review Board 2.0 through 3.0. We've put out a new Django 1.6.11.8 release that contains these fixes, plus some additional backports from newer releases.

To upgrade to this release, run:

$ pip install -U https://downloads.reviewboard.org/releases/Django/1.6/Django-1.6.11.8.tar.gz

Or:

$ easy_install -U http://downloads.reviewboard.org/releases/Django/1.6/Django-1.6.11.8.tar.gz

You can always keep up on the latest Review Board security announcements by subscribing to our Official Announcements mailing list, joining our Subreddit, or following us on Twitter.

Power Pack 3.0.2 improves integration with Microsoft's Team Foundation Server:

• Copied files containing non-ASCII filenames can now be diffed
• Compatibility between various versions of Review Board, Python, and Team Foundation Server has improved

There's also several behind-the-scenes changes preparing Power Pack for new features we have in the works, and for the upcoming Review Board 4.0 release.

Update Today

Power Pack 3.0.2 is recommended for all Power Pack users reviewing code over Team Foundation Server.

To upgrade, or to install for the first time, see the installation instructions.