Skip to content

Commit d8e8d2b

Browse files
Merge pull request tensorflow#26043 from lc0:patch-3
PiperOrigin-RevId: 235603003
2 parents 6799f6e + ef29c4a commit d8e8d2b

File tree

1 file changed

+22
-18
lines changed

1 file changed

+22
-18
lines changed

CONTRIBUTING.md

+22-18
Original file line numberDiff line numberDiff line change
@@ -55,24 +55,28 @@ TensorFlow coding style.
5555

5656
#### General guidelines and philosophy for contribution
5757

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)
72-
typically will live in
73-
[tensorflow/contrib](https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib)
74-
to get some airtime before decision is made regarding whether they are to be
75-
migrated to the core.
58+
* Include unit tests when you contribute new features, as they help to a)
59+
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
65+
[tensorflow/core](https://github.com/tensorflow/tensorflow/tree/master/tensorflow/core)
66+
and
67+
[tensorflow/python](https://github.com/tensorflow/tensorflow/tree/master/tensorflow/python).
68+
TensorFlow has reached version 1 and hence cannot make
69+
non-backward-compatible API changes without a major release. Reviewers of
70+
your pull request will comment on any API compatibility issues.
71+
* When you contribute a new feature to TensorFlow, the maintenance burden is
72+
(by default) transferred to the TensorFlow team. This means that benefit of
73+
the contribution must be compared against the cost of maintaining the
74+
feature.
75+
* Full new features (e.g., a new op implementing a cutting-edge algorithm)
76+
typically will live in
77+
[tensorflow/addons](https://github.com/tensorflow/addons) to get some
78+
airtime before decision is made regarding whether they are to be migrated to
79+
the core.
7680

7781
#### License
7882

0 commit comments

Comments
 (0)