|
|
= OSI Branch Naming Conventions
|
|
|
|
|
|
Branch name template:
|
|
|
|
|
|
====
|
|
|
`<<change-type>>/<<group-name>>/<<branch-title>>`
|
|
|
====
|
|
|
|
|
|
|
|
|
== General Guidelines
|
|
|
|
|
|
- all lowercase
|
|
|
- hyphens not spaces
|
|
|
|
|
|
|
|
|
== Change types [[change-type,change-type]]
|
|
|
[horizontal]
|
|
|
feature:: branches that enhance the standard or add additional features
|
|
|
fix:: Bug fixes to contradictions or errors in the standard
|
|
|
doc:: Documentation changes only
|
|
|
experimental:: (advanced development) Branches where developers want to try out or demonstrate some ideas but don't expect their changes to be integrated directly
|
|
|
|
|
|
== Group names [[group-name,group-name]]
|
|
|
|
|
|
=== OSI
|
|
|
[cols='1,3']
|
|
|
|===
|
|
|
|Name | Description
|
|
|
|`sm` | Sensor modeling
|
|
|
|`tp` | Traffic Participants
|
|
|
|`ha` | Harmonisation
|
|
|
|`pp` | Performance & packaging
|
|
|
|`ge` | Any other, non-group specific developments
|
|
|
|===
|
|
|
|
|
|
== Branch Title [[branch-title,branch-title]]
|
|
|
- should be descriptive and make the change clear. i.e. not "update-sensor-model-x" but rather "initial-radarsensorviewconfig-support"
|
|
|
|
|
|
== Examples:
|
|
|
|
|
|
feature/tp/lane-subtype
|
|
|
|
|
|
feature/pp/support-for-flatbuffer
|
|
|
|
|
|
fix/ge/index-specification-of-trace-files |
|
|
\ No newline at end of file |