...
- Code reviewed and Merged
- Release Notes updated
- Add Jira reference to relevant section (Features). The slogan does NOT have to be identical to the Jira, it often could/should be a better description of the change
- Highlight backward incompatibel changes if applicable
- Latest Yaml files copied to /docs folder (see step2 on CPS Release Process)
- Acceptance Criteria of the User Story have been met
- New functionality Demoed to Team and Stakeholders
- Uploaded recording of demo to CPS User Story Demos
...
- Consider cherry-pick for previous release(s)
- Add Jira reference to relevant section (Bug Fixes and possible Security Notes). The slogan does NOT have to be identical to the Jira, it often could/should be a better description of the change
Complete an Fault Slip-through Analysis (FSA) and add as a comment in Jira
Expand title FSA Template - Bug Category:
3PP
Critical Vulnerability
Documentation
Functional
High Availability
Install
Logging
Performance
Robustness
Rollback
Scalability
Security
Testware/CI
- Upgrade
- Reason for Slippage:
- Insufficient test coverage
- Intermittent Fault/Timing Issue
- Missed impact
- Missed in code review
- Missed in design analysis
- Missed in document review
- Missing requirement
- Unrealistic Development timeframe
- Late requirement: insufficient analysis
- Environment
- Action needed to prevent slippage: <free text>
- Phase it should have been found in:
- Design
- Review
- Automated (unit) Test
- Microservice CI (CIST)
- Release
- Category of test it should have been found in:
- Unit
- Integration Test
- Performance
- Description of test it should have been found in: <free text>
- Link(s) To JIRA improvement record: <free text>
- Bug Category:
...