We should have a 2.0 beta 1 set of release notes that are ready for pushing this week. I made some notes about a couple things that still need to be filled in for this, and things that should be removed.

That will have to be updated now.

This isn't ready for alpha.

Nor this.

Missing a trailing period.

Hmm, you shouldn't need this format. I always do:
* Blah blah
  blah.

* Blah blah..

"request"

Best to do Markdown_ and then have a block below like:
.. _Markdown: http://....

Easier to reuse, and no links in the text.

Should be consistent with using "Markdown".

We should link to the page describing GitHub's extensions.

Can we make this a little more explicit about how this was old behavior? Maybe just put "previously" in there.

"thumbnails"

Can you use :guilabel: for these?

This made it into 1.7.16, and is documented there.

Hmm, I believe this is in 1.7.5. Certainly, 1.7.x releases already do this.

Can you link to this resource? Should be able to do:
:ref:`Repository resource <webapi2.0-repository-resource>`

Same with Repository List resource.

Same with these resources.

We'll need these filled in for the beta.

Should link this resource.

"JavaScript"

These tags are on all pages we ship. I think it's confusing to have them in the release notes.

Can we have literal quotes around that path?

"one level of children" is a bit confusing to me. I don't remember what's in this hook, so I have no idea what this means.

We should have a blurb about this for the beta.

"a consolidated database representation" is kind of overly technical-sounding and doesn't mean anything to anybody who doesn't already know how this works. How about:
Starting in Review Board 1.7, newly uploaded diffs of files would be stored in the database only once, saving storage space if that particular file was used repeatedly in parent diffs or remained unchanged across several iterations of a change.

"have to make" or "has to make"? "have" sounds odd here.

"JavaScript"

We weren't using this jsmin. We were using a separate Python-based jsmin rewrite that did not include this term.
The main reason we're leaving the Python jsmin is because it's largely unmaintained and does not offer some of the benefits of UglifyJS.

Should use jsmin_ and have a .. _jsmin: http:// link below.

"JavaScript"

Should use UglifyJS_ and .. _UglifyJS: http://.

Given the above, it's not worth talking about the license here. Better to say it offers improvements over the version of jsmin we were using.

Can you use literal quotes for these fields?

Here, too: issue_opened, issue_status, open, null.

Should probably use :guilabel: here.

"offter"?

Should use literal quotes around /r/ here and in the description.

We're missing at least two names (Po-Chien Lin and Alessandro Menti). Should go through and make sure everyone is listed.

Let's not actually link this yet. I don't want to confuse people who view the release notes. We can just keep it in the tree instead.

Two blank lines.

1.7.18.

Now that 1.7.18 has this, we can remove it from these release notes.

Ship It!