-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Cognitive Services Ver.2.0.0 #3597
Conversation
1. Everything is re-generated with the latest AutoRest (by generate.cmd). 2. With the latest swagger file change, now Location is a parameter of the method, not a property of client class, this is a breaking change. 3. Change the UT accordingly. 4. Bump the version to 1.1.0.
@@ -7,8 +7,8 @@ | |||
[assembly: AssemblyTitle("Microsoft Azure Cognitive Services Management Library")] | |||
[assembly: AssemblyDescription("Provides Microsoft Azure Cognitive Services management functions for managing Microsoft Azure Cognitive Services accounts.")] | |||
|
|||
[assembly: AssemblyVersion("1.0.0.0")] | |||
[assembly: AssemblyFileVersion("1.0.0.0")] | |||
[assembly: AssemblyVersion("1.1.0.0")] |
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.
@felixwa this is not needed. We usually bump up assemblyverion on major version update.
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.
@shahabhijeet , you mean both AssemblyVersion and AssemblyFileVersion need not to be changed or only AssemblyVersion need not to be changed?
Note this PR introduced a breaking change (Location from property to method parameter) so we definitely need re-versioning.
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.
@felixwa what is the usual practice is, you only update AssemblyVersion when you update the major version.
If you have introduced a breaking change, then simply update
AssemblyFileVersion to 2.0.0.0
AssemblyVersion to 2.0.0.0
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.
@shahabhijeet , okay then I have reversioned everything to 2.0.0.0
@azuresdkci test this please |
Reversion to 2.0.0.0 as shahabhijeet suggested.
* Ver 1.1.0 initial commit 1. Everything is re-generated with the latest AutoRest (by generate.cmd). 2. With the latest swagger file change, now Location is a parameter of the method, not a property of client class, this is a breaking change. 3. Change the UT accordingly. 4. Bump the version to 1.1.0. * Reversion to 2.0.0.0 as shahabhijeet suggested Reversion to 2.0.0.0 as shahabhijeet suggested.
generate.cmd).
the method, not a property of client class, this is a breaking change.
Description
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
Testing Guidelines
SDK Generation Guidelines
*.csproj
andAssemblyInfo.cs
files have been updated with the new version of the SDK.