This document describes the general RDK process flow and related topics.

Code Management Facility (CMF)

The goals of CMF are as follows:

• A vibrant, successful RDK community
• Streamlined and robust processes
• RDK source and documentation in safe hands
• Everyone getting what they need in the time they need it
• Efficiency built on the foundations of automation and scalability
• Protection for what is important, freedom for participants to be creative

On a periodic basis, RDK code is tested and released to the community as CMF releases. This will be generic RDK code without dependency to any platform. CMF code can be built for emulator or raspberry-pi or can be ported to a specific platform (RDK Porting).

Routine Releases

• Tagged every two weeks
• Built and tested
• Only tagged if Black Duck, Build and Test successful
• Changes pulled from Comcast every two weeks 

CMF Contributions

While working with CMF stack, one might find ways to enhance RDK code by adding new features or bug fixes as RDK contribution. The general CMF contribution workflow is as follows:

More information on contributing code changes to RDK can be found here:  Contributing code changes

Getting Support

Support tickets can be raised to get necessary information from RDK support team. This can be for the bugs you faced, doubts you have or any code contributions which you think might enhance RDK.

RDK Support ticket can be raised here: https://jira.rdkcentral.com/jira

Types of support tickets are:

More Information

For more information about the RDK Wiki Code Management Facility (CMF) process, navigate to below mentioned link(s)

• CMF workflow