Branches and tags
This issue is to make an agreement on the way manufacturers publish modifications made to satisfy requirements of the PCB manufacturers.
- main development takes place in master branch
- releases are tagged
- every manufacturer has his own branch originating from the project release (e.g. v4.0.2) and publishes there its modifications
every manufactured commit gets its own tag consisting of project release, manufacturer abbreviation and batch id, that is manufacturer specific (e.g.
- as modifications will depend on PCB manufacturer, one may want to have several to have several batches for a single project release
- if a manufacturer's modification introduces an upgrade that is not "PCB-house specific", it can be merged to master and generate a new patch release (e.g. 4.0.3)