\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
- Pavlo Smahin Create Karate ticket to cover MODELINKS-242
- Pavlo Smahin Create Karate ticket to cover MSEARCH-777
- Christine Schultz-Richert needs to update Default MARC Bibliographic to Inventory Instance mappings
- Khalilah Gambrell to provide test data for Valery in scope of
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIQM-631 - create a Perf ticket to test MARC Validation for at least 30 simultaneous users ECS and Non-ECS and link it to
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4549 - link
to Ramsons release notesJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-2970 - Khalilah Gambrell - will figure out about MARC validation configuration permissions for Ramsons release
- Khalilah Gambrell - confirm LCCN duplicate checking permissions handling
- Christine Schultz-Richert - confirm date migration approach with Folijet, Locate, and etc.