Lines Matching full:change

7 given API will not change in future releases. At the same time, developers
29 Experimental APIs denote that a feature was introduced recently, and may change
127 A breaking API change is defined as one that forces users to modify their
130 itself) is not considered a breaking API change.
132 In order to restrict and control the introduction of a change that breaks the
134 such a change is considered necessary in order to accept it in the project:
141       Title:     RFC: Breaking API Change: <subsystem>
143                    - Background information on why the change is required
144                  - Proposed Change (detailed):
145                    - Brief description of the API change
152                      to adapt out-of-tree users of the API to the change
156 #. The RFC issue must be labeled with the GitHub ``Breaking API Change`` label
167 opened on GitHub. It is left to the person proposing the change to decide
182 - The changes required to adapt in-tree users of the API to the change.
187 - The labels ``API``, ``Breaking API Change`` and ``Release Notes``, as well as
198 ``user`` mailing lists informing them of the change.
238   - The change needs to be atomic and bisectable