|(2 intermediate revisions by one user not shown)|
|−|Branches are going to fall roughly into three categories: |+|
| || |
|−|* Core branches (main dev branch, documentation) |+|
, and also share branches .
|−|* 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. |+|
OEa the .
| || |
|−|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. |+|
Latest revision as of 10:20, 7 November 2012
OE-Core has six month development and release cycles, roughly being April and October each year. As each release is made, the release is given a name and its expected that other layers/repositories that would with the release use the same branch name to denote compatibility.
With the use of the git source control system, users are free and actively encouraged to create clones of the repositories to develop and submit changes against and they are also welcome to share branches in the contrib repositories as appropriate.
For OE-Core, a maintainer is generally appointed for the release branch at release time and this is recommended for other layers too.