diff options
| author |  Asim Shankar <ashankar@google.com> | 2018-07-03 12:03:58 -0700 |
|---|---|---|
| committer |  TensorFlower Gardener <gardener@tensorflow.org> | 2018-07-03 12:06:42 -0700 |
| commit | 69fe072cb467c0723e8c5266c8b32288fb3104a8 (patch) | |
| tree | 5bd63eec57665392ed122d74c56c1d7925e8e7f5 /tensorflow/docs_src | |
| parent | 354603d2f4b2986300223ae2bef59b96a4f3a55d (diff) | |
[Docs]: Point to compat.forward_compatible() in the versioning doc.
PiperOrigin-RevId: 203161840
Diffstat (limited to 'tensorflow/docs_src')
| -rw-r--r-- | tensorflow/docs_src/guide/version_compat.md | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/tensorflow/docs_src/guide/version_compat.md b/tensorflow/docs_src/guide/version_compat.md index 72e427c5f8..d2e5e41190 100644 --- a/tensorflow/docs_src/guide/version_compat.md +++ b/tensorflow/docs_src/guide/version_compat.md @@ -301,8 +301,10 @@ existing producer scripts will not suddenly use the new functionality. #### Change an op's functionality 1. Add a new similar op named `SomethingV2` or similar and go through the - process of adding it and switching existing Python wrappers to use it, which - may take three weeks if forward compatibility is desired. + process of adding it and switching existing Python wrappers to use it. + To ensure forward compatibility use the checks suggested in + [compat.py](https://www.tensorflow.org/code/tensorflow/python/compat/compat.py) + when changing the Python wrappers. 2. Remove the old op (Can only take place with a major version change due to backward compatibility). 3. Increase `min_consumer` to rule out consumers with the old op, add back the |