|
|
The following branching conventions should be followed:
|
|
|
## Summary
|
|
|
|
|
|
The branching conventions are summarised as follows:
|
|
|
|
|
|
| Branch name | Description | Example
|
|
|
| ------ | ------ | ------ |
|
|
|
| `meeting/{meeting number}` | Branch representing agreement of a meeting | `meeting/LI#54e`
|
|
|
| `cr/{spec}/{CR number}` | Branch representing a CR | `cr/ts_103280/77` |
|
|
\ No newline at end of file |
|
|
| `cr/{spec}/{CR number}` | Branch representing a CR | `cr/ts_103280/77`
|
|
|
|
|
|
## Meeting branches
|
|
|
|
|
|
Meeting branches are created to represent the agreement of a meeting. CRs
|
|
|
|
|
|
## CR branches
|
|
|
|
|
|
CR branches are created to represent the formal-language part of a CR. |
|
|
\ No newline at end of file |