Update docs/process/breaking-changes.md.

Change-Id: I9f0313b0cc088fac982f058adbdb423f5fd93659
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/219745
Reviewed-by: Michael Thomsen <mit@google.com>
Commit-Queue: Devon Carew <devoncarew@google.com>
This commit is contained in:
Devon Carew 2021-11-09 16:53:12 +00:00 committed by commit-bot@chromium.org
parent 5ffec0e46e
commit a88c010f2c

View file

@ -65,8 +65,6 @@ to a change being released in a dev channel release.
* Clear steps for mitigating the change.
[TODO: Link to an issue template for this]
* Email Dart Announce (`announce@dartlang.org`):
* Subject: 'Breaking change [bug ID]: [short summary]'
@ -78,7 +76,7 @@ to a change being released in a dev channel release.
* A request that developers may leave comments in the linked issue, if this
breaking change poses a severe problem.
Once you have sent the announce email, please let @devoncarew know in order
Once you have sent the announce email, please let devoncarew@ know in order
to start the review and approval process.
### Step 2: Approval
@ -120,7 +118,7 @@ scope of compatibility, and for which either:
* The impact of the change was significantly larger than described in the
breaking change announcement
, then they may file a 'request for roll-back' using the following steps:
Then they may file a 'request for roll-back' using the following steps:
* Create an issue in the Dart SDK issue tracker labelled
`roll-back-request` containing the following:
@ -133,8 +131,6 @@ scope of compatibility, and for which either:
* A link to the program that was affected, or another program that illustrated
the same effect.
[TODO: Link to an issue template for this]
Upon receiving such an issue the Dart SDK team will either:
* Roll-back the change, or