Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The Patch Submission Process

Why patches 

Content

  • 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.

 

Github

GDP Master lifetime

 

Where to find GDP Master

...