Another week, another release for you!
Last week's release of 2.0.10, while otherwise fantastic, didn't play so nicely with certain MySQL configurations. This resulted in some people hitting errors during site upgrade. 2.0.11 addresses this issue, and brings a couple other improvements to the table.
Perforce users may notice that the "Change" field on a review request will now reflect the submitted change number, instead of the original (now useless) change number, once the change goes into Perforce.
We also fixed a crash for users in timezones not local to this planet. Unknown timezones will simply default to the server time.
See the release notes for all the details.