Today we bring you a very important release, especially to those of you on GitHub. Please read this post carefully.
We've been doing major work on new hosting service integration support in Review Board. This provides, for the first time, direct knowledge of repository hosting service APIs and account linking, removing the need for copy-and-pasted API tokens and hacks.
This feature is critical for GitHub users, as sometime soon (likely this month or next), GitHub will be switching off their old v2 API (which Review Board has traditionally used to fetch files) and moving to the new v3 API.
If you are a GitHub user of any sort, you must upgrade! Failure to do so will mean your repositories may not work soon.
Once you have upgraded, you will need to go into each configured repository and set it up again as a GitHub repository. This will have you link an account on GitHub to your repository. Unfortunately, this is not something we can automate, but you shouldn't have to do this again. Once you've finished, you should be set for when GitHub terminates their old API.
This is a large change to Review Board, and we have been careful to test it thoroughly, but lab testing and real-world testing don't always show the same results. If you have any problem with your repository, please contact us.
If you feel more comfortable, you can create a new, temporary repository, link it to your account, and ensure that works. If there is a problem, report it, and you can continue to use your old repositories until GitHub switches off the API.
In the future, this new support will allow us to provide a more seamless repository configuration process and features specific to hosting services, as well as deeper bug tracker integration.
Along with the hosting service code, this release also provides compatibility with Plastic SCM v4.0, makes the max diff size limit configurable, and fixes a few bugs in the product.
See the release notes for more information.