Corsair - Sprint 206

Owned by Mikita Siadykh
Last updated: Dec 17, 2024
1 min read

Checklist

Testing

  1. Identify tickets that require performance testing by adding label corsair-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 = corsair-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
Create epics/features
Create recordings/presentations for customers
Customer friendly documentation or contact documentation working group.

 Action item

@Kathleen Moore : to add FE backlog to the sprint 207 so @Uladzislau Kutarkin can take them once 206 backlog is completed
@Mikita Siadykh : set up metrics for Sunflower release
@Kathleen Moore : review and prioritize (order in backlog) Ramsons bugfix
@Kathleen Moore @Matt Weaver : create all required stories for Sunflower features
@Kathleen Moore : prepare list of tickets for refinement 12/11
@Kathleen Moore : update slides for system demo
Team: prepare page with RRT resources. @Matt Weaver please manage, mb we need a ticket to control this work? Update: Done. https://eis.atlassian.net/wiki/spaces/PRO/pages/1198686654/Corsair+RRT+Resources
@Kathleen Moore : prioritize BE backlog for 207 sprint
@Matt Weaver : create spike for fields automated testing - https://folio-org.atlassian.net/browse/MODFQMMGR-603