Tool: PEP8 Style Checker
Ignored Files:
    docs/releasenotes/index.rst
    docs/releasenotes/3.0-beta-1.rst



Tool: Pyflakes
Ignored Files:
    docs/releasenotes/index.rst
    docs/releasenotes/3.0-beta-1.rst

Tool: Pyflakes
Ignored Files:
    docs/releasenotes/index.rst
    docs/releasenotes/3.0-beta-1.rst



Tool: PEP8 Style Checker
Ignored Files:
    docs/releasenotes/index.rst
    docs/releasenotes/3.0-beta-1.rst

"from"

Tool: PEP8 Style Checker
Ignored Files:
    docs/releasenotes/index.rst
    docs/releasenotes/3.0-beta-1.rst



Tool: Pyflakes
Ignored Files:
    docs/releasenotes/index.rst
    docs/releasenotes/3.0-beta-1.rst

Tool: Pyflakes
Ignored Files:
    docs/releasenotes/index.rst
    docs/releasenotes/3.0-beta-1.rst



Tool: PEP8 Style Checker
Ignored Files:
    docs/releasenotes/index.rst
    docs/releasenotes/3.0-beta-1.rst

We should credit Shuai Shao for starting this work off, I think.

We should note the new user infobox.

A few more things that are in this release that aren't (yet) in a shipped 2.5:

Bitbucket has been updated to use the 2.0 API, fixing compatibility problems in some setups (3b9c6c5)
Fixed confirming before leaving the page when there's unsaved work (176916d)
Fixed errors saving a group when there's inactive users (6897531)
Fixed a compatibility issue with Mercurial (4735e27)
Several fixes for move detection (151e986, 2f9f515, dde9df0, eb3c939)
Fixed the whitespace changes only banner being duplicated when expanding/collapsing headers. (4f5e2f5)

We might also want to say a little bit about feature checks and how admins will be able to use that going forward to opt into new experimental features.

We should prefer pip now, with a fallback to easy_install. See https://reviews.reviewboard.org/r/8848/diff/

Can we have bullet points for both of these?

Let's link Review Bot to the GitHub repo.

Let's say "administrator" instead of "superuser." it's less Django-y and more correct when it comes to RBCommons (assuming that's been implemented right for Local Sites).

This is the only one that doesn't say "Improvements".  Though, I'm not sure we need "Improvements" on any of those (we don't typically do that in the release notes, and these are under New User Features anyway).

Should be in sentence casing with a trailing period.

Should be in sentence casing with a trailing period.
I would also put this into Review Improvements. I know this can be done for the review request text fields as well, but it's probably more likely for reviews, and having it there would help highlight this feature better.

Should be in sentence casing with a trailing period.

Let's move this into a Search section, and include the on-the-fly indexing.

It's just "Elasticsearch".

Let's move this into a Review Request section, along with reassigning ownership.

Let's move this into a New Administration Features section.

I don't know that we need the history here. Most people don't care about Google Code anymore. Let's instead say something like:
"Splat is a new bug tracker service we currently have in development, designed to be flexible in its usage and to tie into other project management tools. It's being used to track bugs and features for Review Board, and will in time be available for others to use."

It took me a moment to realize what we were talking about (I was thinking a users list on a review request). Maybe say the "users list page".

Let's move this into a New Administration Features section.

This is in 2.5.

Needs to be added to AUTHORS.

Needs to be added to AUTHORS.

Needs to be added to AUTHORS.

Needs to be added to AUTHORS.

Two blank lines.

Let's also put up a section announcing Slack support. I know we say it here, but highlighting it as its own section would also be good. People will be excited about that :)

I think the last thing in here we'll need to add is something about the Bazaar changes. Can keep it simple by saying we've rewritten the Bazaar support to use the command line tool, improving compatibility and ensuring we stay license-compliant, and that 2.0 and 2.5 will soon be receiving this fix as well.

Ship It!