Lines Matching refs:will
7 given API will not change in future releases. At the same time, developers
71 Changes will not be announced.
91 minor changes. Backwards-compatibility will be maintained if reasonable.
110 will be merged
162 The RFC will then receive feedback through issue comments and will also be
164 community at large will have a chance to discuss it in detail.
170 proceed with confidence that it will be accepted.
192 Once the steps above have been completed, the outcome of the proposal will
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"
223 it will be ready to be removed in 4.2 at the earliest.
244 During the deprecation waiting period, the API will be in the ``deprecated``
245 state. The Zephyr maintainers will track usage of deprecated APIs on
247 will continue to provide warnings:
249 - API documentation will inform users that the API is deprecated.
250 - Attempts to use a deprecated API at build time will log a warning to the
260 The Zephyr maintainers will decide when to actually remove the API: this
261 will depend on how many developers have successfully migrated from the
264 If it's OK to remove the API, it will be removed. The maintainers will remove
268 If it's not OK to remove the API, the maintainers will continue to support