This document describes the general RDK development work-flow and related topics.

Code Management Facility (CMF)

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:

Detailed information on contributing code changes to RDK can be found here: C ode Management Documentation

Getting Support

Support tickets can be raised to get request support from RDK Community 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

Categories of support tickets are:

Issue type	Name	Description
General Support Issues	RDK_JIRA_<Company_Name>	Raise a JIRA ticket in your Company Specific Project. This project is accessible only to Preferred member companies.
Code Management Facility Support	RDKCMF	Code contributions to CMF as part of bug fixing or feature enhancement comes under this category. Updating of code from RDK to CMF is also tracked in these.
RDK Support	RDK	Anybody with RDK Support credentials can create this category of tickets.
Raspberry-pi (HDP) Support	RPI	Rapsberry-pi support tickets (only for Preferred members)
Default	RDK_JIRA_TRIAGE	By default, support type will be RDK_JIRA_TRIAGE. All normal users without RDK support credentials can create these JIRA tickets via mailing to support@rdkcentral.com. This will be filtered to appropriate category by triage team.

RDK Resources

[RDK Preferred]