Skip to end of banner
Go to start of banner

Sprint 205

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

\uD83D\uDCAD Checklist

Testing

  1. Identify tickets that require UI load testing for long lists/tables.

  2. Identify tickets that require Karate tests.

  3. Identify tickets that require performance testing.

  4. Review list of e2e tests created and verify the status of tests

  5. Add label = 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. Re-indexing changes

    6. Known issues

    7. MARC mappings changes

    8. What else?

  2. Update GitHub documentation

  3. Review previous release notes and confirm if we need to add these release notes to current release notes

  4. Confirm if we should schedule time with Kitfox and/or FSE Hosting to review certain release activities.

Delivery

  1. Document potential risks and risk mitigation plan

  2. 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.

Bugfest

  • Entire team: Identify Bugfest test case stories that entire team will claim and test
  • QA/PO: Review test cases and priority
  • QA/PO: Prepare test data and Bugfest documentation
  • PO: Prepare quickMARC subgroup UAT

✅ Action item

  • No labels