Page Comparison

Checklist

Testing

1. Identify tickets that require performance testing by adding label firebird-ramsons-perf-testing.

2. Review list of e2e tests created and verify the status of tests

3. Review the status of Karate tests

4. Add label = firebird-release-notes-required for issues that require release notes

Release notes and documentation

1. Review completed tickets and decide if release notes should be updated | Ramsons release notes

   1. Required migrations

   2. Config changes

   3. New/changed permissions

   4. Breaking schema changes

   5. Known issues

   6. What else?

2. Update GitHub documentation

Delivery

1. Document potential risks and risk mitigation plan

2. Review the Definition of Done document

All

•  Update empty FixVersion field
•  Update empty RCA

PO activities

•  Update features' status
•  Link stories to features
•  Update empty Release field
•  Create epics/features
•  Create recordings/presentations for customers
•  Customer friendly documentation or contact documentation working group.

✅ Action item

•  Magda Zacharska review stories with that will require release-notes-required label
•  Magda Zacharska review stories that will require perf testing
•  Magda Zacharska specify requirements for PTF identify stories for the Documentation group