... | @@ -7,6 +7,8 @@ The branching conventions for the TC LI Forge Repository are summarised as follo |
... | @@ -7,6 +7,8 @@ The branching conventions for the TC LI Forge Repository are summarised as follo |
|
| `meeting/{meeting number}` | Branch representing agreement of a meeting | `meeting/LI#54e`
|
|
| `meeting/{meeting number}` | Branch representing agreement of a meeting | `meeting/LI#54e`
|
|
| `cr/{spec}/{CR number}` | Branch representing a CR | `cr/ts_103280/77`
|
|
| `cr/{spec}/{CR number}` | Branch representing a CR | `cr/ts_103280/77`
|
|
|
|
|
|
|
|
![Branching strategy](img/swimlanes.jpg)
|
|
|
|
|
|
## Meeting branches
|
|
## Meeting branches
|
|
|
|
|
|
Meeting branches are created to represent the agreement of a meeting. The meeting branch is created by a Maintainer prior to a meeting, and serves as the source branch for CR branches for that meeting.
|
|
Meeting branches are created to represent the agreement of a meeting. The meeting branch is created by a Maintainer prior to a meeting, and serves as the source branch for CR branches for that meeting.
|
... | | ... | |