Thanks for your interest in RDK! Here are some ways that you can get involved 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 is the new CMF branch that the community will push changes to for review.
- CMF has initially synchronized the rdk-next branch with Comcast production branch code. Automated scripts running daily will identify new Comcast commits and push them for review to rdk-next branches on CMF Gerrit.
- rdk-dev-yymm is a new CMF integration branch, created monthly and baselined off rdk-next. This branch will be hosted per repository in conjunction with rdk-next, with the goal of incorporating community changes at the earliest juncture.
- Community changes, once approved, will be cherrypicked to rdk-dev-yymm and and will thus be available prior to the completion of Comcast down-streaming/ round-trip process.
- Approved contributions will be down-streamed to Comcast for predeployment 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
- Downstreamed Community changes, successfully merged to Comcast Sprint branches, will be cherrypicked to Comcast production branch.
- When downstreamed Community changes are merged to the Comcast production branch they can be merged immediately on the CMF Gerrit rdk-next branch.
- Comcast changesets, imported or contributed daily to rdk-next , will also be cherry picked to the rdk-dev-yymm branch throughout the monthly cycle (once they have passed the necessary gating criteria of scan, build). In this way, the rdk-dev-yymm branch will also keep sync with Comcast production branch.
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
- User will do code contribution to rdk-next branch. This will undergo:
- Code reviews
- Build verification
- License compliance scan
- Test validation
- Once successful, the change will get cherry-picked to rdk-dev-yymm (monthly dev) branch
- This code is then down-streamed to Comcast branch where pre-deployment test validation are done
- Once Comcast accepts, the change is merged to rdk-next.
- Thus the change gets merged to rdk-next
Image Modified