Gutenberg Release Readiness Checklist - Poppy

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	Product owner
All user stories tied to features should be written and estimated.	Product owner
Testing Identify features that require e2e tests Identify features that require Karate tests	Team	Need unit tests
Conduct user acceptance testing	Charlotte, as Product owner work together with Axel and Kathrin from the Gutenberg team ID devops has setup an environment for UAT	UAT environment: https://orchid-dev1.folio-dev.indexdata.com/
Conduct or create user stories for performance/load testing. See	Product Owner writes user stories.
Document Potential Risks and Risk Mitigation Plan	Team

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
Prepare data for Bugfest Create user stories for Kitfox that outline your needs and instructions Please consider how to test long lists/tables	Axel and Katrin from the Gutenberg team
Migration/module upgrade documentation checklist Migration Plan Step by Step instructions for module upgrade New Infrastructure: N/A Config Changes: Schema Changes: JIRA issues created Data Migration: Migration Testing What 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?	-
Add release notes Include any previous release notes that still relate to the release flag any known items with the label known-issue-<<release>> See document - Release Notes Overview	Charlotte, as product owner	Has begun adding notes. Axel 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 Plan Risks:	N/A	-

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	Gutenberg Team	In progress. Katrin will attend the prep meeting on 9/29
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, as Product Owner	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 Types of tests	N/A	-

Action	Responsible	Status
Update Features' statuses Identify which features are at risk and the "at-risk" label to the feature.	Product Owner
User stories: update Release field for those stories/bugs/tasks/etc that will not be done for the release.	Product Owner
Generate Release Artifacts (see Orchid) and link to Release notes	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>>	PO and Dev lead
Modules Ready for deployment Deployment information is provided in launchDescriptor section of module descriptor. Review test status - Unit, Integration, e2e tests https://jenkins-aws.indexdata.com/job/Testing/job/Scheduled%20Karate%20Tests/600/cucumber-html-reports/overview-features.html Tickets will be created automatically for each failure.	Team
Team meets with Kitfox to review upgrade instructions. Team's accept Bugfest build. Need to consider Consortia support. 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?	Team
Regression testing?	QA?
Conduct performance/load testing. See Types of tests	Product Owner writes user stories. TBD who will conduct.

Action	Responsible	Status
Action	Responsible	Status
Update Features' statuses There should be no at-risk feature	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>>	PO and Dev lead
Complete remaining performance/load testing. See Types of tests	Product Owner writes user stories. TBD who will conduct.

Action	Responsible	Status
Teams must conduct smoke tests to verify key functionality works as expected	Gutenberg Team
Testing: All Karate tests and e2e tied to release functionality should be done and running	Gutenberg 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