What's New in Review Board

We have a new release of RBTools for you today. Version 0.7.11 brings a number of fixes and improvements for posting reviews and working with Git, Mercurial, Subversion, and Team Foundation Services repositories.

Here are some of the highlights:

• rbt post --diff-only, which used to be specific to Perforce and regressed there recently, now works for all types of repositories.
• Mercurial changes are now posted as Git-style diffs, leading to a better experience on Review Board.
• Crashes running svn info with certain locales when scanning the type of repository will no longer occur.
• Team Foundation Services support should work correctly when Visual Studio 2017 is installed.
• The help output for rbt post --tracking-branch is no longer incomplete and misleading.

The complete list of changes are available in the release notes.

See the RBTools Downloads page for installation instructions for your operating system.

We're working toward a release of RBTools 1.0, with many new features for working with automated code review, intelligently computing tracking branches for Git, landing sets of changes at once, and more. Stay tuned for that, and as always, if you hit any problems, please let us know on our community support forum or bug tracker.

This week's release of Review Board 3.0.2 fixes many bugs in our new features, from avatars and issue verification to automated code review and desktop notifications.

Here are some of the highlights of the release:

• The in-page bubble and browser's desktop notifications have been fixed, letting you see once again when a review request has been updated or has new discussions.

• Diffs with Unicode characters should appear once again alongside comments in reviews.

• Progressively updating automated code reviews no longer stops displaying the diffs for the comments.

• Files from Perforce containing Unicode BOMs should now patch correctly. If you were having this problem, you should also make sure you have a modern P4Python package installed.

• Gravatars once again display properly for users who have mixed-case e-mail addresses.

• Several compatibility regressions with extensions have been fixed.

• The "Download Diff" button should no longer go missing on the diff viewer.

• The User API no longer breaks if an avatar can't be loaded for a user.

There's a handful of other fixes as well. See the release notes for the full list of changes.

The next patch release of Review Board will be a feature enhancement release, focusing on reworked GitLab support (moving to their more stable API version 4), along with new integrations for Asana, Trello, and I Done This. We're aiming for a predicable schedule for releases, so going forward, look for Review Board releases on Tuesdays and RBTools releases on Thursdays.

Updated 6-January-2018, 2:12AM PST: We seem to be back up and running. It's not clear yet what happened, but we'd like to thank whoever at Google turned the group back on! We'll keep an eye on this over the coming days.

Today, we became aware that our community support group, hosted by Google Groups, was blocked due to a report of malicious content. We're not sure yet if this was a spam protection mechanism on Google's side determining that some content (such as a snippet of source code pasted as part of a support request) was malicious, or if someone intentionally or unintentionally reported the group to Google for abuse. We've reached out to Google and are investigating this.

Right now, since the portal is down, there are a few other option for support:

• You can post to the reviewboard-dev group. We typically use this for issues related to the development of Review Board or third-party extensions, but are opening it up for now to all discussion.
• You can post to the /r/reviewboard subreddit. This is a pretty new, low-activity subreddit we've been using for announcements, but is a fine place to ask more basic questions and have discussions.
• If you need private support, you can file a support ticket. We generally require a support contract for any support tickets here, but until this issue is resolved, we're accepting community support requests.

We know this is annoying, and we're looking into new options for community support going forward that would prevent this from ever happening again. Please reach out to us through any of the above methods if you have any questions. We'll keep this post updated when the support portal comes back online.