Today's release is the second in a series of releases built to improve the speed of the product, reducing the database work required in most pages and in the API. That's not all, though. We've fixed a few bugs, including an API regression from 2.0.12, and added a few new user-facing and administrative features.
More Fine-Tuning
We've further reduced the database work required by Review Board, particularly when it comes to loading and saving user-specific data, something we do on nearly every HTTP request.
Behind the scenes, we've made several improvements to our API testing infrastructure that will help us make the API more lean in future releases.
The Follow Menu
We've added a new menu to the top-right of Review Board that helps users find the Review Board News feed, Twitter, Facebook page, Subreddit, and YouTube channel. This is intended to help users follow the latest Review Board and RBTools updates and to read, watch, or discuss both code review tips and Review Board in general.
Improved E-Mail Support
If you're dealing with "this e-mail is suspicious" warnings in your e-mail client, you're running into problems with how Review Board sends e-mail on behalf of users.
While this can generally be corrected through proper domain records, you can now change how Review Board generates e-mails through a new option in the E-Mail Settings page.
Plus Some Other Improvements
-
We've fixed a regression in the review request draft API that caused unwanted groups to appear when emptying the field.
-
Those using custom X.509-based authentication schemes can now specify a custom username field without forking any code.
-
Search results now contain inactive users and closed review requests.
-
Condition fields for integrations no longer show any archived/hidden repositories or hidden groups, resulting in less noise when setting things up on older installations.
See the release notes for all the changes in 3.0.13.