What's New in Review Board

Updated 25-April-2012 at 6:25PM: People have become concerned about the 1MB limit and how it will apply to binary files in your changesets. Don't worry! Binary files don't count to the 1MB limit. Just code changes.

Review Board 1.6.6 is out! The biggest change is that you can now fetch the API tokens for your private GitHub repositories directly on the repository configuration page. This is necessary as they've removed the API tokens listing on the GitHub account pages, in preparation for a move to the new API.

Another important change to note is that we've limited the size of uploaded diffs to 1MB. We've found that diffs that are larger than this tend to bog down the server, particularly on large deployments, and that diffs of that size are generally too difficult to review.

We suspect that for the most part, people won't hit too many problems with these. The exceptions are for very large, auto-generated bits of code, which probably aren't worthy of review anyway, and very large parent diffs. If you are hit by this for legitimate reasons, please let us know. We can still tweak this limit, but want to see how this goes.

Release notes are available.

As previously mentioned, GitHub is transitioning to a new API and will be soon deprecating the version that Review Board speaks. We've been hard at work on this move (which brings with it a better repository configuration experience and the groundwork for tighter integration with GitHub and other services).

In the meantime, new users have been unable to link with private GitHub repositories, since GitHub no longer supplies the required API Token anywhere on the account page.

But good news! There is a workaround. If you have curl installed (common on Linux), you can request your API token by doing the following:

    $ curl -u github_username https://api.github.com/legacy/token

Enter your password when prompted. The result should show you your API token, which you can paste right into your repository configuration page.

We'll be sending out a release soon that will make it easier to get your API token when configuring the repository, followed by a new release with the GitHub API v3 additions in the following week or two. We want to make sure it's rock-solid first.

If you have any questions, we're always available on our mailing list.

Hello everyone.

GitHub has recently announced that they will soon be removing their older version 1.0 and 2.0 APIs, in favor of the newer version 3 API. This is scheduled to take place on May 1st, 2012.

Some users have already noticed that they have removed the API Token field, meaning that new GitHub Private and Private Organization accounts can't be accessed by Review Board today. We are in contact with GitHub and I'm hoping we'll have a solution to that.

Review Board uses the version 2.0 API to fetch files from GitHub, meaning that any installations using GitHub will stop working on May 1st. We are hard at work on moving to the version 3.0 API, and will have an update as soon as we can verify things are working properly. This will be Review Board 1.6.6.

There will be some manual steps required to get your GitHub repositories working again in 1.6.6. It will involve editing the repository entry, re-selecting GitHub, and authorizing an account. This will fetch the new OAuth2 API tokens from GitHub. Once you've done this, your repository will work again.

Further details will be provided as soon as we have a release.

Review Board 1.5.x users will need to upgrade to 1.6.6 in order to use their GitHub repositories.

Please contact our mailing list if you have any questions or concerns.