Page History

...

• For features - open a RDKDEV (for video or generic contributions) or RDKBDEV (for Broadband contributions)
• Clone the component code from rdk-next branch
• Apply changes 
• Push the patch to Gerrit for review
• Trigger reviews and handle review comments
• Change set trigger: Use TDK for validation and BlckDuck BlackDuck scan for license compliance

...

Reviewers can comment on and score a given change.
• The default set of rules for enabling a code change for submission requires a Code Review score of +2 and a +1 score on any mandatory Gerrit labels configured for the project.
• The result of the scoring process and validation rules is to enable the Submit action on the Gerrit Web UI and subsequent merge capability to the target branch.
   +2 Value approval
   ‐2 Do not submit.
   +1 Enables a submit
   ‐1 Block a submit

Step X:JIRA ticket status update

• Update the JIRA ticket status in  https://jira.rdkcentral.com/

Image Added

Step 8 Submit change

...