Skip to content

doc: revise deprecation semverness info in Collaborator Guide #26232

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.

Sign up for GitHub

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

Closed
Trott wants to merge 2 commits into from
Closed

doc: revise deprecation semverness info in Collaborator Guide #26232

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
64f7b9c
doc: revise deprecation semverness info in Collaborator Guide
Trott Feb 21, 2019
9152145
squash: Apply suggestions from code review
vsemozhetbyt Feb 21, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
squash: Apply suggestions from code review 
Co-Authored-By: Trott <[email protected]>
  • Loading branch information
@vsemozhetbyt @Trott
vsemozhetbyt and Trott authored Feb 21, 2019
commit 9152145c7c5f282facf0deaa79472e04f0864202
2 changes: 1 addition & 1 deletion COLLABORATOR_GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -344,7 +344,7 @@ Documentation-Only Deprecations. Such deprecations have no impact on code
execution. Thus, they are not breaking changes (`semver-major`).

Runtime Deprecations and End-of-life APIs (internal or public) are breaking
changes (`semver-major`) . The TSC may make exceptions, deciding that one of
changes (`semver-major`). The TSC may make exceptions, deciding that one of
these deprecations is not a breaking change.

All Documentation-Only and Runtime deprecations will be assigned a unique
Expand Down