Skip to content

CR form conventions · Changes

Page history
Update CR form conventions authored by canterburym's avatar canterburym
Hide whitespace changes
Inline Side-by-side
Conventions/CR-form-conventions.md
View page @ 1b0b72ac
...@@ -11,9 +11,13 @@ The "Clauses affected" field should reference each attachment that is being chan ...@@ -11,9 +11,13 @@ The "Clauses affected" field should reference each attachment that is being chan
> **EXAMPLE** > **EXAMPLE**
> >
> A CR proposes adding a new field to TS 102 232-1. This involves adding a new clause to section 6, and making a change to the ASN.1 module in attachment **LI-PS-PDU.asn**. > A CR proposes making a change to TS 103 120 which involves:
> >
> The "Clauses affected" field should therefore read "New clause 6.X, LI-PS-PDU.asn" > * adding some new text to clause 8.2,
> * changing **ts_103120_Task.xsd**
> * changing **ts_103120_ETSIDictionaryDefinitions.xml**.
>
> The "Clauses affected" field should therefore read "**Clause 8.2, ts_103120_Task.xsd, ts_103120_ETSIDictionaryDefinitions.xml**"
Changes to attachments should be given in the CR, as a single change block containing a plain diff of the changes to the attachments. Changes to attachments should be given in the CR, as a single change block containing a plain diff of the changes to the attachments.
......