Lines Matching +full:one +full:- +full:time

5 new features are developed, to ensure stability of systems over time. With that
6 as a goal, any given feature should fit into one of the following categories.
27 one of these categories. For non-trivial feature additions, the commit message
28 of the feature, as well as the design doc should explicitly state one of the
38 user-facing impact to function, although might do things like improve
41 Requires: Standards conformance, applicability to all flash-size systems, as
44 ### User opt-in features
46 User opt-in features are features for which an external user must explicitly
48 they may be configurable at compile time, are not required to be configurable at
49 compile time. Examples of this include Redfish query parameters, or IPMI OEM
52 Requires: Explicit, non-default user opt-in to execute the various features.
54 ### Developer opt-in features
58 non-standard interfaces, new command sets, or new APIs that might be applicable.
59 Features of this nature MUST be configurable at either compile time or runtime,
67 CI will generally enable all developer opt-in features to ensure the most
73 2. Entity-manager configuration