Use Case

As a... Driver Engineer
I want... to merge the CSOT feature branch
So that... CSOT can be released to users

User Impact

• New feature

Dependencies

• See linked tickets

Unknowns

• N/A

Acceptance Criteria

Implementation Requirements

This ticket is intended to make CSOT available to users by merging in the features from this EPIC which have been developed on the feature branch into the driver's main branch.

• merge main into the feature branch
• Resolve all merge conflicts
• Ensure that no extraneous TODO or FIXME comments have been left unaddressed
• Ensure that code comments are still relevant to the current state of the codebase
• Ensure that all relevant CSOT spec tests are running
• Ensure that no dead/duplicate code is introduced during the merge/rebase
• Merge feature branch into main
  • Don't squash the commits of the individual ticket PRs when merging onto main

Testing Requirements

• Ensure that all tests continue to pass on the updated feature branch
• Double check any major modifications to/deletions of existing tests to make sure we aren't losing coverage or unexpectedly changing existing functionality
• Ensure we have perf tests running for both CSOT enabled (both with an infinite timeout and with a reasonable timeout value) and CSOT disabled; ensure there is no regression to CSOT disabled; ensure the CSOT enabled tests show reasonable perf

Documentation Requirements

• Ensure that all CSOT-specific types and methods are marked as public and have appropriate inline documentation
• Mark ticket as Docs changes needed and specify CSOT behaviour for the DOCS team
• We also want to have detailed release notes for these changes
  • In particular make sure we clarify how CSOT relates to existing timeout options that are or are not being deprecated with the release of CSOT

Follow Up Requirements

• Release the driver