aboutsummaryrefslogtreecommitdiffhomepage
path: root/doc/cpp
diff options
context:
space:
mode:
authorGravatar Noah Eisen <ncteisen@google.com>2016-10-12 15:04:45 -0700
committerGravatar Noah Eisen <ncteisen@google.com>2016-10-12 15:04:45 -0700
commitcece9c7368cab75444b3c34bb518a98d7f656759 (patch)
tree27cf83a0d9244b678d479531f9d32630e0aef727 /doc/cpp
parent2cef11c6674e67aea8e7f63f7ac2869e5d44a7c5 (diff)
parentd44144c3b2112ed61a21c08331bfe9e18664ceb3 (diff)
manually fixed merge conflict. caused by the addition of a different new interop test
Diffstat (limited to 'doc/cpp')
-rw-r--r--doc/cpp/pending_api_cleanups.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/cpp/pending_api_cleanups.md b/doc/cpp/pending_api_cleanups.md
new file mode 100644
index 0000000000..3e77b657c6
--- /dev/null
+++ b/doc/cpp/pending_api_cleanups.md
@@ -0,0 +1,15 @@
+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 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 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 major version
+number:
+
+- remove `ClientContext::set_fail_fast()` method from
+ `include/grpc++/impl/codegen/client_context.h` (commit `9477724`)