diff options
| author |  Mark D. Roth <roth@google.com> | 2016-09-16 07:34:08 -0700 |
|---|---|---|
| committer | Mark D. Roth <roth@google.com> | 2016-09-16 07:34:08 -0700 |
| commit | 311e7badb80cceac466b57f03094844a2c289cf4 (patch) | |
| tree | a1cfb4cc82439b072a14f6d5861c8d89d59decc6 /doc/core/pending_api_cleanups.md | |
| parent | 0e256107e812807967aa37ee1dc0ca5e954e9a2c (diff) | |
s/minor/major/ in API cleanups doc.
Diffstat (limited to 'doc/core/pending_api_cleanups.md')
| -rw-r--r-- | doc/core/pending_api_cleanups.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/core/pending_api_cleanups.md b/doc/core/pending_api_cleanups.md index a16d3bf778..6d30e0b0e6 100644 --- a/doc/core/pending_api_cleanups.md +++ b/doc/core/pending_api_cleanups.md @@ -1,14 +1,14 @@ There are times when we make changes that include a temporary shim for backward-compatibility (e.g., a macro or some other function to preserve -the original API) to avoid having to bump the minor version number in +the original API) to avoid having to bump the major version number in the next release. However, when we do eventually want to release a feature that does change the API in a non-backward-compatible way, we -will wind up bumping the minor version number anyway, at which point we +will wind up bumping the major version number anyway, at which point we can take the opportunity to clean up any pending backward-compatibility shims. This file lists all pending backward-compatibility changes that should -be cleaned up the next time we are going to bump the minor version +be cleaned up the next time we are going to bump the major version number: - remove `GRPC_ARG_MAX_MESSAGE_LENGTH` channel arg from |