Jump to >
Review Board 2.0.17 is released

2.0.16 may have come out just a few days ago, but it's old news now. We've made some fixes and tweaks to the improvements in that release, fixed up some small packaging issues, and added new extension-related enhancements.

We know a few of you have hit some of the bugs from 2.0.16 in your deployments, so we wanted to get this out to you fast.

The main highlights include:

  • Extensions can now set custom data on reviews through JavaScript hooks, and listen to publishing-related events.
  • Files that were copied but not modified will now appear in the diff viewer.
  • Publishing-related errors in the API will now show up again.
  • Errors with diff generation will show an error page, not a HTTP 500.
  • Users making heavy use of private user profiles and the Depends On field for review requests won't see API errors when modifying drafts.

See the full list of changes for more details.

In case you missed it, check out the announcement for last week's release of Review Board. We cover the new security fixes, performance improvements, bug fixes, and new installation methods available satrting in 2.0.16.

Review Board 2.0.16 is out! Safer, faster, and more stable

The new 2.0.16 release is a nice mix of security fixes, performance, and bug fixes.

First off, this release fixes a security vulnerability recently reported that allows a user to craft a string that can, under the right circumstances, execute a malicious script. If you're running 2.0.x, we highly recommend that you upgrade, particularly if your server is public on the Internet.

Okay, now on to the fun parts.

A faster Review Board

The diff viewer is now fast. Very fast. You'll find some major speed improvements in loading and expanding diffs and viewing diff comment fragments.

Most other pages are a bit faster too. We've fixed and improved client-side caching behavior across the site. The speed improvement should be noticeable.

Lastly, in the performance category, we've identified and fixed a bug that could trigger unnecessary reloads of extension configuration, particularly when using Power Pack.

A more stable Review Board

We've fixed over 25 bugs in this release, spanning search, Unicode conversion, diff navigation, interdiffs, the API, extensions, Bitbucket, Git, Subversion, and more.

There are compatibility fixes for the latest versions of Whoosh and Haystack (both needed for search).

New features!

We've added support for browsing and posting commits on GitLab for review on the New Review Request page.

Using Mercurial? We've added compatibility with Git-formatted Mercurial diffs, which contain more useful information that Review Board can work with.

Extension authors can now choose to block review requests from closing or reopening, and can add new UI to the top of the review dialog.

Better installation through pip and Wheels

Like with RBTools, we're now officially releasing Python Wheel packages for Review Board, supporting the latest versions of pip. To install Review Board, simply type:

$ pip install --allow-all-external ReviewBoard

(In the future, we're hoping to eliminate the need for --allow-all-external.)

Signed releases

As of this release, we're now signing all Djblets and Review Board builds with our official PGP key. We discussed this previously in the RBTools 0.7.3 release announcement, so check that out to learn how to take advantage of this.

Final notes

If you're using search today, make sure to do a full rebuild of your search index. We've made some changes to the index format, which will break search results until reindexed.

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

RBTools 0.7.4 is out

We're back with another RBTools update, this one focusing exclusively on bug fixes.

This release fixes compatibility problems with Python 2.6, a few more Unicode issues, diff generation problems on Team Foundation Server, and more.

To get the latest release, head over to the RBTools Downloads page.

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

RBTools 0.7.3 is out, with Unicode fixes and more

Have you been plagued by Unicode errors when posting changes? Subversion 1.7.x compatibility problems? SSL errors with self-signed certs on Python 2.7.9+? Well then, today's release of RBTools 0.7.3 is for you! ... and, well, everyone, really. There's a lot in here you're going to want.

First off, the Unicode fixes. We had some Unicode-related breakages in past releases, which have been almost entirely eliminated in this release. If you've hit any such error before, give 0.7.3 a try.

There are lots of compatibility and behavioral improvements for Bazaar, ClearCase, CVS, Subversion, Perforce, Plastic, and TFS. Patching, for instance, works a lot more reliably across the board. Subversion 1.7.x and lower should start working again as well.

It's not all bug fixes, though. We have some new features and command line options:

  • rbt post --stamp will auto-stamp commits with the review request URL.
  • rbt patch -R can be used to revert a patch from a review request.
  • rbt land and rbt stamp now work with Perforce.
  • Perforce supports changesets with imported files from remote depots.
  • API caching behavior and cookie storage can now be disabled/changed for any command. Useful for hooks and other scripts.
  • SSL certificate verification can be disabled on Python 2.7.9+ by using --disable-ssl-verification.

Those are the highlights! For the complete list of changes, see the release notes.

But wait, we have a couple more announcements concerning our releases:

Better installation through pip and Wheels

We're now officially releasing Python Wheel packages for RBTools, supporting the latest versions of pip. To install RBTools, simply type:

$ pip install --allow-all-external RBTools

(In the future, we're hoping to eliminate the need for --allow-all-external.)

Signed releases

As of this release, we're now signing all builds with our official PGP key. Using gpg, you can verify a build was produced by us by importing our public key and then verifying it against the .asc signature files from our downloads.

For example, to verify RBTools-0.7.3.exe was produced by us, download it along with RBTools-0.7.3.exe.asc and run:

$ gpg2 --recv-key 4ED1F993
$ gpg2 --verify RBTools-0.7.3.exe.asc

(Note that if it complains about the key not being certified with a trusted signature, it's just because you haven't signed our key. If you see that message, and the primary key fingerprint is 09D5 06DA BB62 A09E 891D A9F3 2852 91B3 4ED1 F993, it's good!)

We'll have documentation covering this in more detail soon.

Thanks everyone, and as always, feel free to reach out with any questions.

Announcing Power Pack 1.3 for Review Board, with TFS Git support

Power Pack 1.3 is out, and builds upon the recently-introduced integration with Microsoft Team Foundation Server by adding support for TFS Git repositories.

You can now add a TFS Git repository to Review Board simply by configuring a new repository, selecting "Team Foundation Server (git)", and entering your repository's clone URL. Seconds later, your team can begin posting changes using RBTools.

This release also contains a variety of bug fixes for licensing and for reviewing PDF documents. Highly recommended for all existing Power Pack users.

As a reminder, Power Pack is now free for up to 2 users. Get started with a 30 day trial license, and after 30 days, Power Pack will continue to work for any two users you choose.

See our installation guide for instructions on installing or upgrading Power Pack, and our release notes for more information on 1.3.

Review Board 2.5 beta 1 is a go!

For many months now, we've been hard at work on a new, major release of Review Board: Version 2.5. Finally, we're ready to share the first beta so you can break it play with it!

There's so much in here that I can't cover it all, so I've chosen a few of my favorite additions to talk about.

  • Expandable diffs in reviews

    When reading through a reviewer's comments on your code, sometimes it's just not clear what they're commenting on until you open the diff viewer. We've fixed that. Now, simply hover over the diff, and the familiar controls for expanding the diff will appear. You can now see more of the diff without switching pages.

  • Replace old file attachments and view their diffs

    File attachments on a review request can now be replaced with a new version of the file. You won't have to delete the old ones anymore.

    We also keep a history of each revision of the file, and allow you to see a diff between them. This works for both text files and images.

  • Image diffs for file attachments

    As I just pointed out, you can now view diffs between images uploaded to a review request. We have multiple ways available to see what changed in an image. Very handy for new artwork for a product.

  • Improved Review Dialog

    The Review Dialog is now instant-apply, meaning that when you make changes to a comment, you don't have to click Save to send those changes to the server. This is a life-saver when you're working on a large review and your computer crashes.

    It also now shows you how your Markdown text will look, so it's not a surprise when you publish your review.

  • Better bug tracker integration

    If you use JIRA, GitHub, or modern versions of Bugzilla for your bug tracking, we'll now show you the bug summary, status, and description when hovering over the bug number. You may need to reconfigure your repositories to enable this.

    This is the beginning of some deeper integration we have planned for bug tracking. Future releases will expand on this even further.

  • Webhooks

    Administrators can set up webhooks to notify other services when something interesting happens on Review Board. This currently includes publishing, closing, or reopening review requests, publishing reviews, and replying to reviews.

    Webhooks can be tied to review requests on specific repositories, or they can cover all repositories, or cover review requests not associated with repositories.

    A webhook will send a JSON payload similar to that of an API respons. If you have a service you're integrating with, and need a specific format for the payload, you can use a built-in templating language to structure your payload however you like.

  • API Tokens

    Scripts or services that talk to Review Board no longer need your username and password to use the API. Instead, you can now create multiple API tokens for this purpose. API tokens are a secure way of authenticating with the web API without needing your credentials, and they can be revoked at any time.

    Scripts or services using API tokens can also be restricted to performing specific operations on specific parts of the API, letting you keep things nice and secure.

  • Performance improvements for RBTools and the web UI

    Our API now allows clients to request only the data they need when making API calls. The result is that both RBTools (0.7 and higher) and the web UI are now much more efficient when communicating with Review Board.

  • Smaller database sizes

    We've changed how we're storing diffs, and the end result is a substantial reduction in our database storage needs (as much as 80%, from our tests). If you re-run condensediffs, or when viewing older diffs, we'll squash down those older diffs into a much smaller, more tightly-packed version. In the long-run, this means faster upgrades and backups.

There's quite a lot more in this release. Check out the release notes for the complete list of changes in beta 1.

To install this release, run:

$ sudo easy_install \
    -f http://downloads.reviewboard.org/releases/ReviewBoard/2.5/ \
    -U ReviewBoard

We don't recommend using this release for production purposes just yet, or against a production database, but please try it out and let us know how it works for you!

Review Board 2.0.15 is out, with improved search!

It may have only been a week since we released 2.0.14, but we just couldn't wait any longer. We're pretty excited about 2.0.15 for a couple of reasons.

First, many of you have encountered an annoying little bug where the review request counts in the dashboard would be out of sync with reality, occasionally dipping into the negatives. We've finally tracked this down, and can now say it's fixed. All you need to do is upgrade to 2.0.15 and you're set.

Second, we've massively improved searching for review requests. We've overhauled the look, usability, performance, and ordering of the search results. The results now include any matching user accounts (with some handy links) and private review requests (if the searcher's on the access lists for them). Results can be filtered to show only users or review requests.

If you're making use of Local Sites, you'll find search now works there as well. That means search is coming to RBCommons!

Please note that you'll need to do a full rebuild of your search index after upgrading to 2.0.15.

There's a handful of other bug fixes in this release as well.

See the release notes for the full list of changes in 2.0.15.

Review Board 2.0.14 is out!

We've been busy squashing Review Board bugs left and right, all in preparation for Review Board 2.0.14, which is out... now.

There are a bunch of bugs fixed throughout the diff viewer, making the experience of viewing diffs a bit better. We've also fixed some major API caching issues from 2.0.13 that manifested in different ways (so if you're running that release, definitely upgrade).

Review Board 2.0.14 was designed to work with the newly-released RBTools 0.7.2. With their powers combined, you'll have a faster, more reliable experience with many of the RBTools commands, and when coding against the RBTools API.

This release depends on Django 1.6.10, which includes a number of security improvements you probably want. A good reason to upgrade by itself.

There are lots of other fixes and improvements in this release. See the release notes for the full list.

RBTools 0.7.2 is here!

It's been just over a month since RBTools 0.7.1 arrived at stores near you (or probably not). That's a whole month spent not upgrading RBTools, and we can't have that. Plus, there were some good bug fixes and new commands we thought we'd send your way. So let's not waste any more time. Here's what's in today's release of RBTools 0.7.2.

First and foremost, Bitbucket/Beanstalk/Unfuddle fixes. We've heard reports from users that posting changes against their Git repositories hosted on these services that just resulted in failure, so we've gone ahead and fixed that all up.

We've also fixed up some API caching brokenness when running against Review Board 2.0.13 and older. If you've ever tried to land a change clearly marked Ship It!, with an error saying it's not marked Ship It!, then you were hit by this bug.

(Oh, we had to disable some optimizations when running against 2.0.13 and older. You'll probably want to upgrade to the soon-to-be-released Review Board 2.0.14 as soon as you can.)

There are also two new RBTools commands for you to play with:

  • rbt login will log into a Review Board server and store the cookie. rbt post and other commands will still do that, but it's sometimes handy to have new users log in once in order to ensure they're all set up properly.
  • rbt logout will log you out of your API session on Review Board, and delete the cookie.

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

Power Pack 1.2: Team Foundation Server, Flexible Licensing, and 2 Free Users Forever!

Power Pack 1.2 has been released with brand new support for Microsoft Team Foundation Server and an all-new flexible licensing scheme.

As a bonus, we're also now offering 2 free licensed seats of Power Pack to every Review Board server! See below for more information.

Microsoft Team Foundation Server

This release introduces support for reviewing code stored on Microsoft Team Foundation Server repositories. Team Foundation Server, or TFS, provides source code management, project management, automated builds, and more, and is deeply integrated with Microsoft Visual Studio.

With Power Pack, you can now configure all your TFS repositories quickly and easily, without any of the custom scripts, patches, or workarounds that were once needed. It's fully supported by the makers of Review Board.

Using RBTools 0.7.1 or higher, developers can post or update changes against configured TFS repositories with one command, without having to manually generate or convert diffs. Developers can also view commits in the Review Board web UI and post any existing commits for review with one click.

Note that currently, only TFVC repositories are supported. Git repositories stored on TFS will be supported in a future update.

Flexible Licensing

In prior releases of Power Pack, a license had to be purchased for the entire server. In larger companies, this made it difficult to justify Power Pack licenses when needed only by select teams.

We've made our licensing model much more flexible. A license can now be purchased containing a fixed number of seats, and those seats can be assigned in a number of ways:

  • Manually assigned to specific users.
  • Manually assigned to all users in one or more review group.
  • Automatically assigned to users in one or more review groups whenever they join the group.
  • Automatically assigned to all users on a server when they join.

It's easier and more affordable than ever to get started with Power Pack. Download a 30 day trial or purchase a license for your team today!

Two Free Seats Forever!

Starting with Power Pack 1.2.0, all Review Board servers will be eligible to receive two free, fully-licensed seats of Power Pack when downloading a 30 day trial license.

Once the 30 days are up, your license will convert to a full license for up to 2 people. This license will never expire, and supports all future releases of Power Pack.

Simply purchase a license at any time to bring the rest of your team or organization on board.

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 pages