Skip to end of banner
Go to start of banner

Firebird - Sprint 202

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

« Previous Version 5 Next »

Checklist

Testing

  1. Identify tickets that require performance testing by adding label firebird-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 = firebird-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

PO activities

  • Update features' status
  • Link stories to features
  • Update empty Release field
  • Create epics/features
  • Create recordings/presentations for customers
  • Customer friendly documentation or contact documentation working group.

✅ Action item

  • No labels