Sprint 193

Owned by Natalia Zaitseva
Last updated: Jul 18, 2024 by Pavlo Smahin
1 min read

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

    1. Do we need to notify Sherzod about any change that might affect e2e tests?

Release notes and documentation

  1. Review completed tickets and decide if release notes should be updated:

    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

Delivery

  1. Document potential risks and risk mitigation plan

  2. Review the Definition of Done document

 

PO activities

  1. Update features' status

  2. Link stories to features

  3. Create epics

  4. Create recordings/presentations for customers

 Action item

@Khalilah Gambrell needs to update release notes about the MARC field order
@Christine Schultz-Richert will update release notes about Call-Number issues in Q SP#1
@Viacheslav Poliakov (Unlicensed) to update the release notes for Ramsons release about API breaking change → R Release Notes
@Christine Schultz-Richert and @Khalilah Gambrell to link stories from this filter issues not linked to features

Â