-
-
-
This is maybe a little confusing. How about:
The thumbnails in the change description box include a "Review" link, to allow jumping to the review UI directly without needing to find the matching thumbnail at the top of the page.
-
Maybe mention here that this is especially important information in languages which use whitespace for blocks, like Python?
-
-
-
This should clarify that existing users won't see their columns change (and maybe list which columns we default to, in case they want to set it for themselves).
-
-
-
Add release notes for 2.0 beta 3.
Review Request #5507 — Created Feb. 19, 2014 and submitted
These are the release notes for the upcoming beta. They're larger than
the 1.7 release notes.Since that's pretty self-explanatory, I'd like to use the rest of my
time to provide some stats.Here's the top 6 largest release notes we've put together:
* 767 - 2.0-beta-3.rst
* 698 - 1.7.rst
* 697 - 1.6.rst
* 538 - 2.0-beta-2.rst
* 527 - 1.5.rst
* 526 - 2.0-beta-1.rstI think we're good on 2.0.
I've also changing the naming of the existing 2.0 beta images to
2.0-*.png and updated the older release notes. This is because Sphinx
dumps all images into a single directory, and this will help us
namespace that output in the future.
Built the docs and went through them.
| Description | From | Last Updated |
|---|---|---|
|
This should mention the bug number. |
 david
|
|
|
This is maybe a little confusing. How about: The thumbnails in the change description box include a "Review" link, to … |
david
|
|
|
Maybe mention here that this is especially important information in languages which use whitespace for blocks, like Python? |
david
|
|
|
This had a bug associated with it, didn't it? |
david
|
|
|
Should say "non-standard" instead of "non-default" |
david
|
|
|
This should clarify that existing users won't see their columns change (and maybe list which columns we default to, in … |
david
|
|
|
maybe s/the header is set/this header is included/ ? |
david
|
|
|
Trailing o. |
david
|
|
|
resultings? |
david
|
|
|
Can we include a screenshot of this? I'd like to start highlighting major new features with images. |
david
|
|
|
Can we include a screenshot of this? I'd like to start highlighting major new features with images. |
david
|
|
|
Can we include a screenshot of this? I'd like to start highlighting major new features with images. |
david
|
|
|
s/simply/simplify/ |
david
|
|
|
This should say "target users", not "target groups". |
david
|
- Change Summary:
-
Made all the changes requested in the initial review.
- Branch:
-
masterrelease-2.0.x
- Commit:
-
bb49e30e1b8272f6de6abadb13cf71c9eb6991ef046bed15ab2853ea7123e16c91d72de975705c80
- Change Summary:
-
Accidentally updated an older file. Reverted that.
- Commit:
-
046bed15ab2853ea7123e16c91d72de975705c80fcaacbf05837232c139924ee0f3af3fe97d20ac6
- Change Summary:
-
- Added a bunch of screenshots. Retina and non-retina.
- Renamed older 2.0 release note images to have a "2.0-" prefix, to help with namespacing outputted Sphinx images.
- Corrected some typos.
- Added release notes for changes committed since the last update.
- Description:
-
These are the release notes for the upcoming beta. They're larger than
the 1.7 release notes. Since that's pretty self-explanatory, I'd like to use the rest of my
time to provide some stats. Here's the top 6 largest release notes we've put together:
~ * 732 - 2.0-beta-3.rst
~ * 767 - 2.0-beta-3.rst
* 698 - 1.7.rst * 697 - 1.6.rst * 538 - 2.0-beta-2.rst * 527 - 1.5.rst * 526 - 2.0-beta-1.rst I think we're good on 2.0.
+ + I've also changing the naming of the existing 2.0 beta images to
+ 2.0-*.png and updated the older release notes. This is because Sphinx + dumps all images into a single directory, and this will help us + namespace that output in the future. - Commit:
-
fcaacbf05837232c139924ee0f3af3fe97d20ac6d7906d521295c73352577bab398278b28c1aa6f8
- Diff:
-
Revision 4 (+776 -5)