\uD83D\uDCAD Checklist
Testing
Identify tickets that require UI load testing for long lists/tables.
Identify tickets that require Karate tests.
Identify tickets that require performance testing.
Review list of e2e tests created and verify the status of tests
Add label = release-notes-required for issues that require release notes
Release notes and documentation
Review completed tickets and decide if release notes should be updated | Ramsons release notes
Required migrations
Config changes
New/changed permissions
Breaking schema changes
Re-indexing changes
Known issues
MARC mappings changes
What else?
Update GitHub documentation
Delivery
Document potential risks and risk mitigation plan
Review the Definition of Done document
PO activities
- Update features' status
- Link stories to features
- Create epics
- Create recordings/presentations for customers
- Customer friendly documentation or contact documentation working group.
✅ Action item
- Christine Schultz-Richert needs to update Default MARC Bibliographic to Inventory Instance mappings
- Khalilah Gambrell to provide test data for Valery in scope of UIQM-631 - Getting issue details... STATUS
- Kalibek Turgumbayev create a Perf ticket to test MARC Validation for at least 30 simultaneous users ECS and Non-ECS and link it to UXPROD-4549 - Getting issue details... STATUS
- Khalilah Gambrell - will figure out about MARC validation configuration permissions for Ramsons release
- Khalilah Gambrell - confirm LCCN duplicate checking permissions handling → add to release notes
- mark MODINVSTOR-1232 - Getting issue details... STATUS , MSEARCH-842 - Getting issue details... STATUS is needed for Ramsons release notes
- Pavlo Smahin to create a ticket for migration documentation
- Valery_Pilko to test UIIN-3021 - Getting issue details... STATUS
- mark MODINVSTOR-1271 - Getting issue details... STATUS with Ramsons release notes
- Entire team: Review previous release notes and confirm if we need to add these release notes to current release notes