Skip to end of metadata
Go to start of metadata

Code Contribution Workflow

  • Deployment ready Product Branch has been created for RDK components that the community will push changes to review & It is with higher standards of test qualification

  • Monthly Sprint Branch (rdk-dev-yymm) is a new CMF integration branch, created monthly and baseline off Product Branch Branch. This branch will be hosted per repository in conjunction with Product branch with the goal of incorporating community changes at the earliest juncture.
  • Community changes, once approved, will be cherry-picked to Monthly Sprint branch (rdk-dev-yymm) and will thus be available prior to the completion of down-streaming/ round-trip process.
  • Approved contributions will be down-streamed to Regression Branch for pre-deployment validation using their test process
    • Defects will be planned in monthly sprints
    • Features will be presented for Architecture Review to be scheduled to an upcoming sprint. Sprint timelines to be published to contributor.
    • Contributions pending validation will be available in monthly development iteration branches
  • Down streamed Community changes, successfully merged to Regression branch, after pre-deployment test validation, the code changes will be cherry-picked to Product Branch

Code Contribution Workflow Diagram

  1. User will do code contribution to rdk-next branch. This will undergo:
    1. Code reviews
    2. Build verification
    3. License compliance scan
    4. Test validation
  2. Once successful, the change will get cherry-picked to Monthly Sprint Branch (rdk-dev-yymm)
  3. This code is then down-streamed to Regression Branch where pre-deployment test validation are done
  4. Once Comcast accepts, the change-set is cherry picked to Product Branch.
  5. Thus the change gets merged to Product Branch



Component owners/reviewers/approvers, defined as specific groups in Gerrit, will be added to the review by default. You may request additional feedback by specifically adding reviewers via the Gerrit web GUI. 

Product Branch

Product branch is a deployment ready branch is created for RDK components that the community will push changes to review.

Refer to Product Branch for the Components hosted in CMF Gerrit (https://code.rdkcentral.com)

Refer to RDK Central GitHub Components & its Branches hosted in https://github.com/rdkcentral/

Monthly Sprint Branch

Monthly Sprint Branch (rdk-dev-yymm) is a new CMF integration branch, created monthly and baseline off Product Branch. This branch will be hosted per repository in conjunction with Product branch with the goal of incorporating community changes at the earliest juncture.

Once community changes is  approved, will be cherry-picked to Monthly Sprint branch (rdk-dev-yymm) and will thus be available prior to the completion of down-streaming to Regression Branch / round-trip process.

Regression Branch

Regression branch is the branch used for validation of the contributions. Approved contributions will be down-streamed to Regression Branch for pre-deployment validation using their test process.

  • Defects will be planned in monthly sprints
  • Features will be presented for Architecture Review to be scheduled to an upcoming sprint. Sprint timelines to be published to contributor.
  • Contributions pending validation will be available in monthly development iteration branches

Down streamed Community changes, successfully merged to Regression branch, after pre-deployment test validation, the code changes will be cherry-picked to Product Branch. 

Code Submission Process

Code Submission Process - RDK Central Gerrit

Code Submission Process - RDK Central GitHub


  • No labels

7 Comments

  1. Pradeepta Kumar Das where can we (Liberty Global or any RDK community member) find this Regression Branch ?

      1. You are answering with link to Product Branch, that one is clear and I have no problem with, my question is to get access to Regression Branch. you did not answer this

        1. Currently RDK is partnering with the Comcast test team for conducting regression testing on contributions. As part of this process, RDK down streams contributions to the Comcast sprint branch to run regression test cases and additional test cases required to get the contribution merged to the product branch. The active Comcast sprint branch is currently functioning as the regression branch.

  2. We have updated the details about the main branch for each of the components where we receive the code contributions. 

  3. Pradeepta Kumar Das  we are unable to locate aamp rdk-next branch. Could you help to locate it or explain the flow in that case?

    1. Hi Lukasz Wasylyk , For aamp component, please use the stable2 branch for submitting your code changes. This is mentioned in the following Document (click here)