Errata are introduced and stored in the issue list of the group‘s GitHub repository. The workflow to add a new erratum is as follows:
ErratumRaised”.
It SHOULD also include the label corresponding to the document on which the erratum is raised, e.g., “@@@@” or “@@@@”. (Please, consult the list of available labels.) It is okay for an erratum to have several
labels. In some, exceptional, cases, i.e., when the erratum is very general, it is also acceptable not to have a
reference to a document.Editorial” are displayed separately, to make it easier to differentiate editorial
errata from substantive ones.Errata” is
added to the entry and the “ErratumRaised” label removed. A new comment on the issue MAY also be added,
beginning with the word "Summary:" (if such a summary is useful, based on the discussion).Errata” are displayed in this report, whether they are open or closed. Their
status is added to the report on the individual errata.Editorial”; editorial errata are listed separately from the
substantive ones.This report contains a reference to all open issues with the label Errata, displayed in the sections below. Each section collects the issues for a specific document, with a separate section for the issues not assigned to any.
If you have problems following this process, but you want nevertheless to report an error, you can also contact the staff contact of the Working Group, @@@@.