Code reviewed and Merged shall follow the code review process as listed in CPS Ways of Working (WoW)

All Acceptance Criteria of the User Story have been met

Latest Yaml files copied to /docs folder (see step2 on CPS Release

Process)

Consider necessary documentation

Consider Release Notes updates

1. Add Jira reference to the relevant section ('Features'). The slogan does NOT have to be identical to the Jira, it often could/should be a

1. better description of the change

2. Highlight backward

1. incompatible changes if applicable

Consider new functionality Demoed to Team and Stakeholders

1. Uploaded recording of the demo to CPS User Story Demos

Update Jira with comments even if it's just a 1 line of code that was input for the story

Add Jira reference to the relevant section in read the docs (RTD) ('Bug Fixes' and

possibly 'Security Notes'). The slogan does NOT have to be identical to the Jira, it often could/should be a better  description of the change

Move Jira to submitted when code is being reviewed by other team members

Ensure Jira tickets is updated at least once a day with a comment about the progress that day.

Log hours worked in Jira

Consider cherry-picking for previous major release

Complete a Fault Slip-through Analysis (FSA) and add as a comment in Jira

Agree with the Customer the FSA especially if there are any follow-up actions needed BEFORE closing the bug

Agree with the reporter that bugs can be closed.

Consider End2End Demo for the epic

Doublecheck necessary documentation and release notes

End2End integration/acceptance testing must have been done and completed according to CPS Ways of Working (WoW)

Agree delivery of overall epic with stakeholders in planning meeting 

PO to state overall/summary of the value each feature added during epic completion. Create a link for PO and PTL use in release note updates for external stakeholders