Q4 CY2023 Threading Epic Summary

[yanesca]

Requirement checklist

• Fix version/Requested Timescales: Mbed TLS 3.6
• Description/Use Cases (Use cases list): Any application that wishes to use PSA Crypto in a multi-threaded environment
• Deliverables (list of deliverables agreed with stakeholders/client(s)): Minimal Viable Product (for details see the Strategy for 3.6 section of the design document)
• Exclusions (what's not included in the scope of the work): Anything not explicitly mentioned in the Strategy for 3.6 section of the design document
• Dependencies (known external dependencies required for delivery): No external dependencies
• Relevant Contact(s) (contact list for the relevant people to get more information about this requirement): @gilles-peskine-arm

Epic checklist

• Is epic fully broken down? - Yes
• Parallelisation - Most of the time 2 people can work on it in parallel, sometimes 3 (see the
  dependency graph for details)
• Conflicts - interaction with a large part of the library, friction is expected, but there shouldn't be any major conflicts
• Epic estimate: 18S (7.1 weeks)
• Description/Use Case: see requirements
• DoD (expected deliverables, expected quality and exclusions): see requirements
• Experts list (if any otherwise N/A): N/A
• Design documentation: docs/architecture/psa-thread-safety.md
• Dependencies: N/A
• Resources needed: N/A
• Infra/Test Automation/CI needs: N/A
• Requirement link: https://jira.arm.com/browse/SECLIB-1161
• For a release: Mbed TLS 3.6, code freeze expected in January 2024, whole MVP is must have, no features to backport
• Review issues in the epic according to the issue checklist: Done
  • Testing gap identified (Windows). We decided to accept the risk.
• Risks: Tight timeline (dependency graph is deep)
• Testing notes: see Testing section of the design document
• Work behind a flag: use existing feature flags MBEDTLS_THREADING_PTHREAD and MBEDTLS_THREADING_C
• Changelog / documentation: Update threading design document and add changelog entry #8436