Code Contribution Process

• 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 Release Branch. This branch will be hosted per repository in conjunction with Release 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 Production/Release branch. 

Workflow Diagram

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 Release Branch. This branch will be hosted per repository in conjunction with Release 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.