Thanks for your interest in RDK! Here are some ways that you can get involved on code contribution process and help us improve RDK. 

Recent Upgrades

...

A new deployment ready branch “rdk-next” has been created with higher standards of test qualification

...

rdk-next branch

...

rdk-dev-yymm branch

...

 Quarterly releases

 Deployment ready code

 Pre-Deployment tests

...

 Monthly Iteration releases

 Reviewed by component owners

 Tested with Reference platforms

Upgraded work-flow

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 rdk-dev-yymm (monthly dev) branch
3. This code is then down-streamed to Comcast branch where pre-deployment test validation are done
4. Once Comcast accepts, the change is merged to rdk-next.
5. Thus the change gets merged to rdk-next

...