Change Management

Workflows

todo: need to add standard links

Create/Discuss Change request		status: valid security: safety:
status: valid tags: change_management responsible: RL_contributor approving: RL_committer supporting: RL_technical_lead, RL_module_lead has output: WP_FEAT_REQUEST, WP_ISSUE_TRACK_SYSTEM has input: WP_POLICIES, WP_ISSUE_TRACK_SYSTEM has guidance: GD_GUIDL__Contr_Request_Guideline, GD_GUIDL__Pull_Request_Guideline, GD_GUIDL__Issue_Guideline
The change/contribution request is created and discussed. The request must be filled out based on the existing templates. The possible outcome is a contribution request from type change. Until the template is not filled out properly, the change request may be kept in “Draft” from the Committer (RL_committer). The possible outcome is either a change request with status “Draft” or “In Review”.
WF_CR_DC_ChangeRequest		Workflow

Review/Approve Change request		status: valid security: safety:
status: valid tags: change_management responsible: RL_committer approving: RL_technical_lead, RL_module_lead supporting: RL_safety_manager, RL_security_manager, RL_quality_manager has output: WP_FEAT_REQUEST, WP_ISSUE_TRACK_SYSTEM has input: WP_FEAT_REQUEST, WP_ISSUE_TRACK_SYSTEM has guidance: GD_GUIDL__Contr_Request_Guideline, GD_GUIDL__Pull_Request_Guideline, GD_GUIDL__Issue_Guideline
The change/contribution request is reviewed and approved. The final approval is done by the Technical Lead (RL_technical_lead) or the Module Project Lead (RL_module_lead) dependent on scope. The possible outcome is either a change request with status “Accepted” or “Rejected”. Only if the request is accepted, it will be merged.
WF_RV_AP_ChangeRequest		Workflow