1. Purpose and scope
A released kit is used by many design teams at once, often on different releases and with different tool versions. Problems will be found: a rule coded too strictly or too loosely, a PCell that draws wrongly at the edge of its range, a library view that disagrees with its layout, or a model limit nobody noticed. Customer Support, Errata & Updates exists so that each problem is confirmed quickly, every affected user is warned, and the fix arrives as a controlled, regressed release that tells each design team whether it needs to act.
The stage also follows change from outside the kit. Process change notices from the process node lifecycle may alter models, rules or extraction. Tool suppliers release new versions that must be qualified before they are added to the tool support matrix. Each such change is assessed, regressed and released the same way as an erratum fix. The work is recurring: each cycle ends at a Kit update release gate and the next begins.
In scope: the customer issue log, the errata log, triage and reproduction, fixes in the owning lanes, regression against the previous release, impact statements, update releases with their notes, rule waiver guidance, and qualification of new tool versions. Out of scope: retiring kit versions, which belongs to PDK End of Life.
12 more sections for registered members.