Branching Policy

Revision as of 00:06, 28 July 2008 by Laibsch (talk | contribs) (Protected "Branching Policy" [edit=sysop:move=sysop])
Jump to: navigation, search

Branches are going to fall roughly into three categories:

  • Core branches (main dev branch, documentation)
  • Topic branches (stable branch, openmoko branch, etc. - anything with an entity behind it and also specific development targets if long running e.g. packaged-staging)
  • User branches (personal branches where users can share hacks, request pulls into other branches, request testing of new features etc.)

Any OE developer is free to request a personal user repository. User branches should clearly be identified as such and we'd caution about having large groups of users depending on them. Effort should be made by everyone concerned to get useful changes into the Core or Topic branches.

Core and Topic branches should only be created after discussion and consensus.

Mirrors should mirror the Core and Topic branches but the user branches should not be mirrored to encourage use of the core/topic branches.