You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+22-18
Original file line number
Diff line number
Diff line change
@@ -55,24 +55,28 @@ TensorFlow coding style.
55
55
56
56
#### General guidelines and philosophy for contribution
57
57
58
-
* Include unit tests when you contribute new features, as they help to
59
-
a) prove that your code works correctly, and b) guard against future breaking
60
-
changes to lower the maintenance cost.
61
-
* Bug fixes also generally require unit tests, because the presence of bugs
62
-
usually indicates insufficient test coverage.
63
-
* Keep API compatibility in mind when you change code in core TensorFlow,
64
-
e.g., code in [tensorflow/core](https://github.com/tensorflow/tensorflow/tree/master/tensorflow/core) and [tensorflow/python](https://github.com/tensorflow/tensorflow/tree/master/tensorflow/python).
65
-
TensorFlow has reached version 1 and hence cannot make
66
-
non-backward-compatible API changes without a major release. Reviewers of your
67
-
pull request will comment on any API compatibility issues.
68
-
* When you contribute a new feature to TensorFlow, the maintenance burden is (by
69
-
default) transferred to the TensorFlow team. This means that benefit of the
70
-
contribution must be compared against the cost of maintaining the feature.
71
-
* Full new features (e.g., a new op implementing a cutting-edge algorithm)
0 commit comments