-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Chat preview6: Add Chat Message Tags Support #14973
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 11 commits
b24a06c
1c3bce2
ac3c828
a09022d
22754b4
300c769
a0f2d88
92b085e
d6bf4a9
f9be0de
262fd32
28abaf2
911a105
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure about the version number. Would like some suggestions here. @xirzec @DominikMe @juancamilor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So pedantic SemVer would have it be a minor bump (1.1.x) for any feature additions and a patch bump only for fixes that don't change public surface (1.0.x).
However, in practice we don't always bump the minor number every time we add new surface, usually it's more when we make a substantial change (or have some new feature we want to do a beta release for.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The swagger is now a
-previewversion, so should this have a beta suffix like in1.1.0-beta.1?Leaving it up to Jeff about the minor bump. I tend to follow semver and would bump it, but ideally we could have more changes. How far along is enabling real-time notifications for browser?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no strong feelings one way or the other. I'm totally fine with following semver to the letter if that works for you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My main concern is that we have a GA version referencing a beta swagger
tag: package-chat-2021-04-05-preview6I think we have to fix that?
@juancamilor @LuChen-Microsoft
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I used 1.1.0-beta.1 instead