Lines Matching full:features

11 balance of the latest technologies and features and excellent overall quality. A
13 the features that have actually been implemented, allowing the project to
15 features that are not ready yet.
69 new features has passed, and that the time to stabilize the next release of the
79 On occasion, more significant changes and new features will be allowed, but such
117   architecture/architecture variant/Hardware features)
168      - Finalize target milestones for features in flight.
176      - No new features after RC1, ONLY stabilization and cosmetic changes, bug and doc
177        fixes are allowed. New tests for existing features are also allowed.
181 …- No new features after RC2, ONLY stabilization and cosmetic changes, bug and doc fixes are allowe…
249 An LTS includes both mature and new features. API and feature maturity is
251 as we move from one LTS to the next giving users access to bleeding edge features
270 This guarantees that we release many of the highlighted and core features with
277     with additional features, but the core implementation is not modified. This
286   - New APIs for experimental features can be added at any time as long as they
287     are standalone and documented as experimental or unstable features/APIs.
289   - No new features or overhaul/restructuring of code covering major LTS features.
292     - Additional advertised LTS features
294   - Auxiliary features on top of and/or extending the base OS and advertised LTS features
341 features only.
350 features and will be limited in scope. The LTS,  development tree, and the
352 but with a more rigorous process in place for adding new features into the audit
355 This process will be applied before new features move into the