Odin Release Readiness Checklist - Poppy
Two sprints before feature freeze (173)
Action | Responsible | Status |
|---|---|---|
Update Features' statuses Identify which features are at risk and the "at-risk" label to the feature and escalate to stakeholders Clean up Poppy backlog | Charlotte, Product owner | Done |
All user stories tied to features should be written and estimated. | Charlotte, Product owner | Done |
Testing Identify features that require e2e tests Identify features that require Karate tests | Charlotte, product owner together with Niels Erik as Dev Lead | TBD |
Conduct user acceptance testing |
| UAT environment: https://orchid-dev2.folio-dev.indexdata.com/ |
Conduct or create user stories for performance/load testing. See | N/A | - |
Document Potential Risks and Risk Mitigation Plan | N/A | - |
One sprint before feature freeze (174)
Action | Responsible | Status |
|---|---|---|
Update Features' statuses Identify which features are at risk and the "at-risk" label to the feature and escalate to stakeholders Clean up Poppy backlog | Charlotte, Product Owner | Done |
Prepare data for Bugfest Create user stories for Kitfox that outline your needs and instructions Please consider how to test long lists/tables | Florian, Nina and Sabrina from the Odin team | Done |
Migration/module upgrade documentation checklist Migration PlanStep by Step instructions for module upgrade New Infrastructure: N/A Config Changes: Schema Changes: JIRA issues created Data Migration: Migration TestingWhat are the configuration Changes? What are the schema Changes? How do we test? | Index Data | Charlotte has written up DEVOPS ticket.
|
Any breaking changes? | Team | No |
Re-Indexing for release upgrade? For bugfest Poppy? | - | No |
| Charlotte, as product owner together with Florian as project manager | Has begun adding notes. Florian will schedule time for demo for the RA-SIG |
Accessibility Testing Run automated accessibility testing IF you have RTL/JEST tests review (https://github.com/nickcolley/jest-axe)' OR conduct manual accessibility testing with Deque aXe | - | - |
Conduct or create user stories for performance/load testing. See Types of tests | N/A | - |
Document Potential Risks and Risk Mitigation PlanRisks: | N/A | - |
Feature freeze sprint (175)
Action | Responsible | Status |
|---|---|---|
Update Features' statuses Identify which features are at risk and the "at-risk" label to the feature and escalate to stakeholders | Charlotte as Product Owner | Done |
Prepare data for Bugfest Create user stories for Kitfox that outline your needs and instructions FWIW - I think settings needs to be cleaned Please consider how to test long lists/tables | Odin Team | In progress. Nina and Florian is working on this |
| Charlotte, as Product Owner, together with Florian as project manager | In progress |
Accessibility Testing Run automated accessibility testing IF you have RTL/JEST tests review (https://github.com/nickcolley/jest-axe)' OR conduct manual accessibility testing with Deque aXe | - | - |
Conduct or create user stories for performance/load testing. See | N/A | - |
Sprint before Bugfest (aka Business Acceptance Testing) period (176)
Action | Responsible | Status |
|---|---|---|
Update Features' statuses Identify which features are at risk and the "at-risk" label to the feature. | Charlotte, Product Owner |
|
User stories: update Release field for those stories/bugs/tasks/etc that will not be done for the release. | Charlotte, Product Owner |
|
Generate Release Artifacts (see Orchid) and link to Release notes | Odin team |
|
Add release notes Include any previous release notes that still relate to the release flag any known items with the label known-issue-<<release>> | Charlotte, Product owner |
|
Modules Ready for deployment Deployment information is provided in launchDescriptor section of module descriptor. Review test status - Unit, Integration, e2e tests Tickets will be created automatically for each failure. | Odin team |
|
Team meets with Kitfox to review upgrade instructions. Team's accept Bugfest build. Teams must conduct smoke tests to verify key functionality works as expected BEFORE Bugfest is made available to community Teams must document App/module not ready for testing Issues yet to be resolved Deployment verification? | N/A | - |
Regression testing? | QA? |
|
Conduct performance/load testing. See | Charlotte, Product Owner writes user stories. TBD who will conduct. |
|
Sprint before GO-Live (178)
Action | Responsible | Status |
|---|---|---|
Action | Responsible | Status |
Update Features' statuses There should be no at-risk feature | Charlotte, Product Owner |
|
Add/Review release notes Include any previous release notes that still relate to the release flag any known items with the label known-issue-<<release>> | Charlotte, Product owner, and Niels Erik as Dev Lead |
|
Complete remaining performance/load testing. See | Charlotte, Product Owner writes user stories. TBD who will conduct. |
|
Go-Live sprint
Action | Responsible | Status |
|---|---|---|
Teams must conduct smoke tests to verify key functionality works as expected | Odin Team |
|
Testing: All Karate tests and e2e tied to release functionality should be done and running | Odin Team |
|
Add/Review release notes Include any previous release notes that still relate to the release flag any known items with the label known-issue-<<release>> | Charlotte as Product owner |
|