Branches Naming: Difference between revisions
Jump to navigation
Jump to search
m (Yambowikiadmin moved page Branches-naming to Branches Naming) |
m (Added fixes category) |
||
| Line 5: | Line 5: | ||
If however this branch aims at be merged with the develop the following naming convention should be respected | If however this branch aims at be merged with the develop the following naming convention should be respected | ||
* '''maintain | * '''fixes/XXX''': Fix specific (groups of) bugs. To be used for extended fixes, otherwise there is the branch bug-fixes | ||
* '''phys | * '''maintain/XXX''': Maintenance of specific modules/procedure/.... Limited modifications. No revolutions. Examples: maintain-RIM, maintain-cutoff | ||
* '''refact | * '''phys/XXX''': New physics. Examples: phys-ph-dyn, phys-raman, phys-vertex... | ||
* '''tech | * '''refact/XXX''': Deep refactorization of specific procedures/modules. Examples: refact-FFT, refact-parallel-IO, refact-msg... | ||
* '''tech/XXX''': New technical aspects/modules/procedures. Examples: tech-CUDA, tech-FFTW, tech-SLK | |||
Revision as of 14:07, 23 March 2023
Of course the developers can use any name for their branch.
If however this branch aims at be merged with the develop the following naming convention should be respected
- fixes/XXX: Fix specific (groups of) bugs. To be used for extended fixes, otherwise there is the branch bug-fixes
- maintain/XXX: Maintenance of specific modules/procedure/.... Limited modifications. No revolutions. Examples: maintain-RIM, maintain-cutoff
- phys/XXX: New physics. Examples: phys-ph-dyn, phys-raman, phys-vertex...
- refact/XXX: Deep refactorization of specific procedures/modules. Examples: refact-FFT, refact-parallel-IO, refact-msg...
- tech/XXX: New technical aspects/modules/procedures. Examples: tech-CUDA, tech-FFTW, tech-SLK