Happy New Year, everyone!
Tonight's release of Review Board 2.0.12 brings about a large number of improvements to stability, performance, Markdown editing and rendering, e-mail control, repository compatibility, extension support, and more. It's one of our largest 2.0 releases yet.
Better Markdown support
We've completely overhauled our Markdown support. You can now disable Markdown when editing a field or a comment, which is useful when pasting or typing text that may not be Markdown-safe. All plain text fields will still be escaped for edit when you begin editing a field, so that you can easily add Markdown content.
We're smarter about how we escape content for Markdown now as well. You'll see fewer backslashes in your text.
If you prefer to edit all your fields in plain text by default, you can now do so by going into My Account -> Settings and unchecking "Always use Markdown for text fields." Any text fields saved as Markdown will still be loaded as Markdown, but now it'll be your choice.
Oh, and if you want to quickly spell check your text fields, just toggle Markdown off for a bit, and you'll get the browser's native spell checking back. You can then toggle Markdown back on when you're done.
The Markdown fields were a bit slow before, especially if the browser was bogged down. We've fixed this, and you should now have a much more comfortable typing experience.
Last, but not least, Markdown rendering is massively improved. We now preserve whitespace, blank lines, wrapping in lists, line breaks in lists, and the starting line numbers for lists. We have smarter language-based syntax highlighting (when using GitHub-style fenced code blocks), and we don't show unwanted backslashes in rendered text.
We've fixed over 30 bugs, including issues with multi-threaded server setups, text selection in the diff viewer, CVS keyword processing, Unicode encoding issues with some copy/pasted text in text fields, auto-complete usability, and much more.
A broken extension is now less likely to break Review Board. Much of the custom code in extensions are sandboxed, preventing their errors from breaking anything else.
Support for Kiln and FogBugz
Are you a Kiln or FogBugz user? Good news! You can now review your code on Kiln with Review Board and link to your bugs on FogBugz.
This post is already getting pretty long, so check out the release notes for the full list of changes in 2.0.12.