Lines Matching full:changes
65 When the API changes status to unstable API, mark the API version in the headers
71 Changes will not be announced.
91 minor changes. Backwards-compatibility will be maintained if reasonable.
104 #. A Pull Request must be opened that changes the corresponding entry in the
113 When the API changes status to stable API, mark the API version in the headers
119 Introducing breaking API changes
147 - Function call changes
148 - Device Tree changes (source and bindings)
149 - Kconfig option changes
154 Instead of a written description of the changes, the RFC issue may link to a
155 Pull Request containing those changes in code form.
175 - The actual changes to the API
177 - Changes to the API header file
178 - Changes to the API implementation(s)
179 - Changes to the relevant API documentation
180 - Changes to Device Tree source and bindings
182 - The changes required to adapt in-tree users of the API to the change.
185 - An entry in the "API Changes" section of the release notes for the next
200 The API version shall be changed to signal backward incompatible changes. This
202 include minor and patch level changes. Patch and minor versions MUST be reset to
207 Breaking API changes will be listed and described in the migration guide.
215 Deprecation and removal of APIs will be announced in the "API Changes"
234 - Include the deprecation in the "API Changes" of the release notes for the