Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Sign in
A
AMC FMC Carrier AFC
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 15
    • Issues 15
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Wiki
    • Wiki
  • image/svg+xml
    Discourse
    • Discourse
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • Projects
  • AMC FMC Carrier AFC
  • Issues
  • #181

Closed
Open
Opened Jun 07, 2021 by Mikolaj Sowinski@msowinski
  • Report abuse
  • New issue
Report abuse New issue

Branches and tags

This issue is to make an agreement on the way manufacturers publish modifications made to satisfy requirements of the PCB manufacturers.

Some ideas:

  • 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. v4.0.2_ts_batch452 or v4.0.2_cti_batch199)
  • 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)
Assignee
Assign to
AFC v4.0.2
Milestone
AFC v4.0.2
Assign milestone
Time tracking
None
Due date
No due date
0
Labels
None
Assign labels
  • View project labels
Reference: project/afc#181