Skip to content
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

[Release] sdk/resourcemanager/orbital/armorbital/2.0.0 #20365

Merged
merged 6 commits into from
Mar 24, 2023

Conversation

azure-sdk
Copy link
Collaborator

…m spec commit: 1e7b408f3323e7f5424745718fe62c7a043a2337
Copy link
Member

@RickWinter RickWinter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JeffreyRichter , @jhendrixMSFT Please review the breaking changes causing major version bumps. Major bumps are painful and doing them because something was removed feels icky. Could we find ways to deprecate via README.md directives?

@JeffreyRichter
Copy link
Member

JeffreyRichter commented Mar 10, 2023 via email

@RickWinter
Copy link
Member

Deprecating helps if they aren't using the type which could be very likely.

@JeffreyRichter
Copy link
Member

JeffreyRichter commented Mar 10, 2023 via email

@RickWinter
Copy link
Member

Agreed, Only true when they don't want any of the new features.

@JeffreyRichter
Copy link
Member

JeffreyRichter commented Mar 10, 2023 via email

@jhendrixMSFT
Copy link
Member

For cases where something has been removed, it's not simply a matter of emitting a // Deprecated doc comment during code generation. In order to know that something has been removed, we'd need to compare the current version against the previous version. This can get especially tricky to automate for cases where something wasn't removed but was renamed.

@tadelesh
Copy link
Member

For cases where something has been removed, it's not simply a matter of emitting a // Deprecated doc comment during code generation. In order to know that something has been removed, we'd need to compare the current version against the previous version. This can get especially tricky to automate for cases where something wasn't removed but was renamed.

I agree. Since swagger does not provide deprecation feature, we could not auto-generate the deprecation part correctly. I don't believe manual maintenance is practical.

@tadelesh
Copy link
Member

The breaking changes are introduced and approved in this swagger PR. @JeffreyRichter could you please approve this major version release with adding Approved Major Version label?

@tadelesh tadelesh dismissed RickWinter’s stale review March 24, 2023 06:02

Jeff has approved the major version.

@Alancere Alancere merged commit 73b7050 into main Mar 24, 2023
@Alancere Alancere deleted the release-orbital-armorbital-2.0.0-1678237911 branch March 24, 2023 06:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants