... | @@ -88,9 +88,13 @@ An example is given below: |
... | @@ -88,9 +88,13 @@ An example is given below: |
|
|
|
|
|
![image](uploads/c3faf3660e79df93360ce6fec36be228/image.png)
|
|
![image](uploads/c3faf3660e79df93360ce6fec36be228/image.png)
|
|
|
|
|
|
The [CR Author](Process/CR-Authors) includes the changes to the formal language schema as part of the CR form, using change-marked text as per the existing ETSI process. [CR Author](Process/CR-Authors)s are strongly encouraged to generate this change-marked text from the Forge, rather than attempting to keep the CR Form and Forge MR aligned manually.
|
|
The [CR Author](Process/CR-Authors) includes the changes to the formal language schema as part of the CR form.
|
|
|
|
|
|
> There is an experimental tool provided for delegates to generate change-marked text from Forge MRs - contact [@canterburym](/rep/canterburym) to find out more.
|
|
Changes are included in a change block which clearly indicates that it pertains to attachments, and which contains a standard diff format description of the changes to the attachments.
|
|
|
|
|
|
|
|
To populate this, the CR author downloads the "plain diff" changes from the Merge Request overview page. The diff sections for each attachment are given in a separate change block in the CR, with each change block clearly indicating to which attachment it applies. An example is given below.
|
|
|
|
|
|
|
|
![image](uploads/601f1b9906b6fcdfb28c973ff53f6136/image.png)
|
|
|
|
|
|
# Consideration of the CR at the meeting
|
|
# Consideration of the CR at the meeting
|
|
|
|
|
... | | ... | |