... | ... | @@ -88,7 +88,7 @@ An example is given below: |
|
|
|
|
|
![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.
|
|
|
The [CR Author](Process/CR-Authors) includes the changes to the formal language schema as part of the CR form.
|
|
|
|
|
|
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.
|
|
|
|
... | ... | @@ -100,7 +100,7 @@ To populate this, the CR author downloads the "plain diff" changes from the Merg |
|
|
|
|
|
The [CR Author](Process/CR-Authors) presents both the CR form and the associated changes in the ETSI Forge to the meeting.
|
|
|
|
|
|
If the [CR Author](Process/CR-Authors) decides to revise the contribution, they makes any necessary changes by making additional commits to the CR branch. Draft CR forms may be created following the procedures above, and the uploaded to the drafts folder following the existing ETSI process.
|
|
|
If the [CR Author](Process/CR-Authors) decides to revise the contribution, they makes any necessary changes by making additional commits to the CR branch. CR forms are then updated following the procedures in clause 3.3, and the uploaded to the ETSI portal following the existing ETSI process. **It is the CR Author's responsibility to ensure that the CR form correctly reflects the current state of changes in the Forge**, including updated the commit hash and any change to the content of change blocks related to attachments.
|
|
|
|
|
|
CRs should pass automated checking before being accepted by the meeting, with exceptions being made at the Chair's discretion.
|
|
|
|
... | ... | |