Add draft release notes for 5.0 beta 1.
Review Request #12374 — Created June 15, 2022 and submitted
Information | |
---|---|
david | |
Review Board | |
release-5.0.x | |
Reviewers | |
reviewboard | |
This adds the release notes draft covering everything that we're
shipping in beta 1.
Built HTML and checked the output.
Summary | |
---|---|
Description | From | Last Updated |
---|---|---|
Two small changes to add: Extensions that failed to load had the wrong text for reloading extensions. Fix problems that … |
|
|
I have one more thing that needs to go in (/r/12437), which will need to be included in here. (That … |
|
|
Let's reference the doc: :doc:`4.0.7` |
|
|
pip3 |
|
|
I don't think we need this now that this is all on https. |
|
|
http -> https in these. |
|
|
Also: oauth2_provider_accesstoken oauth2_provider_application oauth2_provider_grant oauth2_provider_idtoken oauth2_provider_refreshtoken reviewboard_oauth_application |
|
|
Let's be explicit about the beta status of each. |
|
|
"or higher" isn't quite right, since there's explicit ranges that are supported. |
|
|
We can use :pypi: here. |
|
|
Only one blank line needed between parent and child sections with no content. |
|
|
Let's move "Review Board now ..." to its own paragraph so it's less buried. |
|
|
Let's link to these. We should probably draft integration pages on https://www.reviewboard.org/integrations/ for each by release. Helps with references and … |
|
|
Two blank lines before reference definition blocks. |
|
|
No need for the trailing period in the section header. |
|
|
Let's switch these to pip3. |
|
|
We should probably tell people where to go to find this. |
|
|
Typo: Pyments -> Pygments |
![]() |
|
We can say that this is the start, and that we have further improvements coming in beta 2. |
|
|
This needs to be double backticks in ReST. The table name is scmtools_tool though. |
|
|
Same here. |
|
|
Should be Title Case. |
|
|
Should be Title Case. |
|
|
Let's put these in alphabetical order. |
|
|
So I wasn't going to make this a beta, but now I'm wondering if we should... And if we should, … |
|
Change Summary:
Added changes that have gone in since the last revision.
Commits: |
|
|||||||||
---|---|---|---|---|---|---|---|---|---|---|
Diff: |
Revision 2 (+546) |
Checks run (2 succeeded)
-
-
Two small changes to add:
- Extensions that failed to load had the wrong text for reloading extensions.
- Fix problems that could occur with setting up an environment for running
brz
for Breezy (more likely to affect unit tests, but still).
-
-
-
docs/releasenotes/5.0-beta-1.rst (Diff revision 2) I don't think we need this now that this is all on https.
-
-
docs/releasenotes/5.0-beta-1.rst (Diff revision 2) Also:
oauth2_provider_accesstoken
oauth2_provider_application
oauth2_provider_grant
oauth2_provider_idtoken
oauth2_provider_refreshtoken
reviewboard_oauth_application
-
-
docs/releasenotes/5.0-beta-1.rst (Diff revision 2) "or higher" isn't quite right, since there's explicit ranges that are supported.
-
-
docs/releasenotes/5.0-beta-1.rst (Diff revision 2) Only one blank line needed between parent and child sections with no content.
-
docs/releasenotes/5.0-beta-1.rst (Diff revision 2) Let's move "Review Board now ..." to its own paragraph so it's less buried.
-
docs/releasenotes/5.0-beta-1.rst (Diff revision 2) Let's link to these.
We should probably draft integration pages on https://www.reviewboard.org/integrations/ for each by release. Helps with references and SEO. Wanna put a task in Asana for this?
-
docs/releasenotes/5.0-beta-1.rst (Diff revision 2) Two blank lines before reference definition blocks.
-
docs/releasenotes/5.0-beta-1.rst (Diff revision 2) No need for the trailing period in the section header.
-
-
docs/releasenotes/5.0-beta-1.rst (Diff revision 2) We should probably tell people where to go to find this.
-
docs/releasenotes/5.0-beta-1.rst (Diff revision 2) We can say that this is the start, and that we have further improvements coming in beta 2.
-
docs/releasenotes/5.0-beta-1.rst (Diff revision 2) This needs to be double backticks in ReST.
The table name is
scmtools_tool
though. -
-
-
Commits: |
|
|||||||||
---|---|---|---|---|---|---|---|---|---|---|
Diff: |
Revision 3 (+596) |
Checks run (2 succeeded)
-
-
I have one more thing that needs to go in (/r/12437), which will need to be included in here.
(That change targets 5.0 beta 1 for now, and will be backported to 4.0.8 after.)
-
-
docs/releasenotes/5.0-beta-1.rst (Diff revision 3) So I wasn't going to make this a beta, but now I'm wondering if we should...
And if we should, we'll need this in the
pip
instructions above.
Commits: |
|
|||||||||
---|---|---|---|---|---|---|---|---|---|---|
Diff: |
Revision 4 (+596) |
Checks run (2 succeeded)
Commits: |
|
|||||||||
---|---|---|---|---|---|---|---|---|---|---|
Diff: |
Revision 5 (+606) |
Checks run (2 succeeded)
Change Summary:
Switch back to django-evolution beta.
Commits: |
|
|||||||||
---|---|---|---|---|---|---|---|---|---|---|
Diff: |
Revision 6 (+606) |