Review Board 2.0.12 Release Notes¶

Upgrade Notes¶

• This release contains database schema changes to the reviews_review, reviews_reviewrequest, reviews_reviewrequestdraft, and accounts_profile tables for the new Markdown support.

New Features¶

• Added support for toggling Markdown per-field.

  In 2.0, we introduced support for Markdown. All text fields in the UI were Markdown-capable, and all new text was sent in Markdown.

  Now, Markdown is optional and is stored per-field. When editing text, you can toggle whether Markdown will be used for that field. This applies to all review request fields, comments, reviews, and replies.

  When in Markdown mode, the text fields will continue to be syntax-highlighted. When in text mode, Review Board will use the browser’s standard textarea widget, enabling usage of spell-checking capabilities if supported by the browser.

  Custom fields provided by extensions will gain this support automatically.

• Added a user option for setting whether to use Markdown by default.

  The My Account page now has an Always use Markdown for text fields setting for choosing whether text fields will edit in Markdown by default. If set, all text fields, regardless of the type of text stored on the review request, will begin editing in Markdown mode. If unset, Markdown will only be used if the text field already contained Markdown text, or if Markdown is chosen when editing the text.

• Reduced e-mail recipients when adding reviewers to review requests.

  When adding new reviewers (either users or groups) to a review request without updating any other fields, Review Board will now only send e-mails to those new reviewers, rather than to all existing reviewers. This helps to limit the number of e-mails going out when bringing people into the review process.

• Added support for adding repositories on Kiln.

• Added support for adding bug trackers on FogBugz.

Usability Improvements¶

• The log in page now focuses the username field by default. (Bug #3643)

  Patch by Jessica Yuen.

Extensions¶

• Added a new hook for registering hosting services.

  The new HostingServiceHook allows an extension to register a new hosting service. It will handle registering when the extension is enabled and unregistering when disabled.

  Patch by Justin Maillet.

• Extensions can now take advantage of the features available in LessCSS 1.7.5.

  Previously, Review Board was using LessCSS 1.5.1. We now ship 1.7.5, which provides a number of enhancements.

• Callbacks attached by a SignalHook are now provided with an extension parameter pointing to the extension instance.

  Patch by Justin Maillet.

• Improved sandboxing throughout the product.

  Most hooks and other integration points are now properly sandboxed, preventing Review Board from crashing if an extension raises an exception.

  Patches by Justin Maillet.

Web API¶

• Added support for fine-grained text types for text fields on several models.

  Review Request Resource, Review Request Draft Resource, Review Resource, and Review Reply Resource all have new fields associated with text fields that indicate the text type of that field. For example, body_top_text_type indicates the text type of the body_top field.

  Previously, a single text_type field indicated the text types of all fields. This is now deprecated, and will not contain a value in the resulting payload for these resources.

  However, setting text_type, for compatibility reasons, will update the fine-grained text type fields.

• Added ?include-text-types= for many resources to include alternate text conversion in payloads.

  This takes a comma-separated list of text types (html, markdown, plain, or raw). The payload will contain a type_text_fields dictionary for each type, with all text fields represented and converted to the requested type.

  Specifying raw will provide the original values for the fields. This is useful when using this in conjunction with ?force-text-type=.

  When issuing a PUT or POST request, the caller can POST/PUT an include_text_types= field instead.

  This replaces the now deprecated ?include-raw-text-fields=, which was added in 2.0.9.

• Group display names are no longer valid values when updating a review request draft’s target_groups field.

  This was never documented as being a supported value, and can cause errors when a display name matches another group name.

• Attempting to add invalid users to a review request draft’s target_people field no longer causes the field to be emptied.

• Errors involving commit IDs now say “commit ID” instead of “change number.”

Bug Fixes¶

Contributors¶

• Andrew Hong

• Azad Salahli

• Christian Hammond

• David Trowbridge

• Dmitry Vasiliev

• Erik Lattimore

• Jessica Yuen

• Justin Maillet

• Yanjia Xin