... | ... | @@ -39,7 +39,7 @@ Create a new branch for your CR by clicking the [New branch](https://forge.etsi. |
|
|
The [New branch](https://forge.etsi.org/rep/li/schemas-definitions/-/branches/new) page allows you to specify details for your new branch. Fill in the fields as follows:
|
|
|
| Field | Value |
|
|
|
|-------|-------|
|
|
|
| Branch name | Follow the [branching convention](Conventions/Branching-convention) and choose a name of the form `cr/{deliverable/{CR number} `Case is important, and so are the rendering conventions - so cr/103221-1/0123 is correct, but CR/TS1032211/cr0123 is not! |
|
|
|
| Branch name | Follow the [branching convention](Conventions/Branching-convention) and choose a name of the form `cr/{deliverable/{CR number}`. Case is important, and so are the [rendering conventions](Conventions/Rendering-conventions) - so `cr/103221-1/0123` is correct, but `CR/TS1032211/cr0123` is not! |
|
|
|
| Create from | Pick the branch for the **plenary** meeting that will eventually approve the CR (e.g. `meeting/LI61`) |
|
|
|
|
|
|
> If you mess up, don't panic. You can't rename branches, but you can delete the branch you just created and try again. If you have changes you don't want to lose, you can use a [command line trick](Rename-a-Branch) or contact a [Maintainer](Process/Maintainers) for help.
|
... | ... | |