Lines Matching +full:build +full:- +full:disabled

10 Required for the deployment of _any_ OpenBMC build. Examples of this include the
27 one of these categories. For non-trivial feature additions, the commit message
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
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.
60 and generally will default to disabled. Features of this nature, when disabled,
62 feature is disabled. Company or feature specific functions, as well as the
64 disabled. Note, there are cases where _removing_ a feature might cause user
67 CI will generally enable all developer opt-in features to ensure the most
68 coverage of build configurations.
73 2. Entity-manager configuration