Add JS release notes for June #1386
Conversation
jeremymeng
requested review from
alzimmermsft,
czubair,
kyle-patterson,
loarabia,
ShivangiReja and
xiangyan99
as code owners
jeremymeng
force-pushed
the
js-2020-june-relnotes
branch
from
cce019e to
eade7f5
Compare
jeremymeng
requested review from
ramya-rao-a,
chradek,
richardpark-msft,
sarangan12,
willmtemple and
sophiajt
Co-authored-by: chradek <51000525+chradek@users.noreply.github.com>
Co-authored-by: Richard Park <51494936+richardpark-msft@users.noreply.github.com>
releases/2020-06/js.md
Outdated
|
|
||
| #### Key Bug Fixes | ||
|
|
||
| - Fixed an issue where a `TypeError` was sometimes thrown as an uncaught exception. |
There was a problem hiding this comment.
@chradek Am thinking a generic statement on connection reliability should be good enough?
|
|
||
| #### Preview | ||
|
|
||
| - _Add packages_ |
There was a problem hiding this comment.
This is the GA release of Text Analytics.
There was a problem hiding this comment.
@willmtemple other languages list both preview.5 and GA. Should we do that? Feel free to submit suggestion if needed.
Co-authored-by: Richard Park <51494936+richardpark-msft@users.noreply.github.com>
Co-authored-by: Richard Park <51494936+richardpark-msft@users.noreply.github.com>
Co-authored-by: Richard Park <51494936+richardpark-msft@users.noreply.github.com>
releases/2020-06/js.md
Outdated
|
|
||
| #### Breaking Changes | ||
|
|
||
| - TODO |
There was a problem hiding this comment.
There is a breaking change coming in for Identity:
- Switch to using CredentialUnavailable to differentiate from expected and unexpected errors during DefaultAzureCredential startup. PR #8172. Note: this changes the original behavior for ManagedIdentityCredential, which previously would return
nullinstead of throwing an exception.
releases/2020-06/js.md
Outdated
|
|
||
| #### New Features | ||
|
|
||
| - TODO |
service bus Co-authored-by: Harsha Nalluru <sanallur@microsoft.com>
Identity
Co-authored-by: chradek <51000525+chradek@users.noreply.github.com>
|
@ramya-rao-a and team, any additional feedbacks? |
|
Generic feedback not on this PR specifically and something to check with @adrianhall Should we change the header Also, we do call out in the beginning whether something is a preview or a bug fix over a GA. But, people who would generally skip the initial wall of text and go to the headers would have nothing in the individual section telling them whether it is a preview or not. Can we consider a standard one liner below each service that says whether it is a first time GA, a preview or a bug fix release? |
|
Another generic feedback: Can we have "New features" appear before "Breaking changes"? As a user, it is nice to first be enticed with new features that would convince me whether to upgrade or not than looking at breaking changes |
|
Nevermind, logged #1448 |
change to "Breaking Changes from Last Preview"
No description provided.