...

• 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 Product Branch 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 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 is cherry picked to Product Branch.
5. Thus the change gets merged to Product Branch

...