Baseline Rules
From DDCIDeos
Jump to navigationJump to search
Baseline Rules
Over-all rule
In the absence of a need for a component to be designated to a specific baseline, it shall be designated to the oldest *applicable* baseline
(note: *applicable* means: 1. the baseline is active; and 2. the set of rules below).
Default customer rule
DDC-I wishes a customer to use the oldest baseline possible that meets their customer requirements.
Default R&D rule
DDC-I R&D features, if any, will be added to the newest baseline (i.e., the latest verification date - Kismet). Only an extremely compelling reason will change this default behavior (e.g., a customer pays us to get it done sooner).
- Jupiter: The superset of verified components for the Celestial and Durants programs. Capsule releases may occur to add cores/processors. Other components may be added *if* none of the existing primal things need modification.
- Europa: A modification to one, or more, of the "primal things" in the Jupiter baseline as *required* by a customer (e.g., Deos653p1 run-time to add TCE for Loewen). Capsule releases may occur to add cores/processors. Other components may be added *if* none of the existing primal things need modification.
- Kismet: 64bit ARM, Intel, & PPC with 32bit ARM & PPC *and* any additional R&D features DDC-I would like to add. Customers may be assigned to this baseline due to a required feature that does not fit in the Europa time frame.
