Motivation for GDP Master
Makes it easier for interested parties to know where the work / bleeding edge of GDP is being conducted, previously we've received feedback stating the branch structure / naming schema was confusing this should ease that.
Projected audience and users of the GDP Master
You should be using master if..
The Patch Submission Process
- Master: The default branch for genivi-dev-platform.git & meta-genivi-dev.git
Work during release cycles is completed in this branch, once a 'release' candidate is declared
master is branched to a 'release' branch, which becomes the current maintenance branch.
Currently (and following general yocto practices) the version of the GDP in master is linked by the underlying baseline (meta-ivi) and the yocto release below it (poky/OE). Once a release is
declared this inheritance is used to define the version. It is expected that any new package contributions
are sent as patches / PR's against master. Due to being a branch in constant flux in terms of yocto versioning,
situations may occur in which not all target hardware is supported due to the relevant BSP layer not supporting
the required version of yocto.
- Maintenance: The current maintenance branch of genivi-dev-platform & meta-genivi-dev.git
The maintenance branch is the name given to the currently supported 'release' branch of GDP
Once a new release is declared and branched from master, the maintenance title is transferred.
Only bug/security fixes or specific backport patches / PR's should be based against this branch.
It is expected that a user looking for a 'stable' GDP build (or requiring a certain version of a package)
would use the maintenance branch.
GDP Master lifetime
Where to find GDP Master
GDP Master is here
The remote head of the repo is set to the master branch, i.e master is the default branch.