1. Purpose of the gate
Maintenance release is the first proof that the software can be kept working after it has shipped. The production release showed that the update service was ready. This gate shows that it works in practice: field issues have been gathered and fixed, security updates prepared, the fixes validated by the regression on silicon, and a signed update installed and rolled back on test devices before it is offered to customers.
The gate criteria are fixes and security updates validated by the regression on silicon, update delivery shown by a signed update installed and rolled back on test devices, and security advisories published for fixed vulnerabilities as the disclosure policy says. Later maintenance releases follow the same pattern, but they are not each reviewed as a gate; the first one is, because it sets the routine that every later one follows.
Two hardware gates are linked. In the AI accelerator lifecycle, the Maintenance software release is held together with this one, because firmware and driver updates ride in the accelerator's regular software releases. In the automotive lifecycle, Start of production waits for this gate in the sense that after start of production every software update is a controlled change, notified to customers and approved before it ships; this review must show that the change process is in place.
10 more sections for registered members.