Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

driver-only ECC: EPICs summary issue (Q3) #7856

Closed
mpg opened this issue Jun 29, 2023 · 1 comment
Closed

driver-only ECC: EPICs summary issue (Q3) #7856

mpg opened this issue Jun 29, 2023 · 1 comment

Comments

@mpg
Copy link
Contributor

mpg commented Jun 29, 2023

Requirement checklist:

  • Fix version/Requested Timescales (can be used to describe Phased delivery milestones): 3.5 must have to TF-M code size improvements
  • Description/Use Cases (Use cases list): people who have ECC accelerators / alternative implementation of ECC and want to save code size can compile out all of ecp.c and bignum.c (see restrictions below).
  • Deliverables (list of deliverables agreed with stakeholders/client(s)): a version of Mbed TLS that supports this.
  • Exclusions (what's not included in the scope of the work)
  • Dependencies (known external dependencies required for delivery): none
  • Relevant Contact(s) (contact list for the relevant people to get more information about this requirement): Nordic, TF-M

Epic checklist:

  • Is epic fully broken down? Yes
  • Parallelisation: partially between the two EPICs as the dependency is incremental
  • Conflicts: one conflict with code size work on PK, that should be resovled in a week
  • Epic estimate 2c: 5.2w (6.6w including nice-to-have) / 2d: 2w
  • Description/Use Case: OK
  • DoD (expected deliverables, expected quality and exclusions): OK
  • Experts list (if any otherwise N/A): @mpg
  • Design documentation: docs/architecture/psa-migration/strategy.md + Driver-only ECC: goals and strategy #6839
  • Dependencies: none
  • Resources needed: Valerio doing most of the work, us mostly reviewing (Manuel, Paul, Tom D)
  • Infra/Test Automation/CI needs: none
  • Requirement link: none
  • For a release: aiming for 3.5 (late September)
  • Review use of a separator to split must-have from nice-to-have: OK
  • Review issues in the epic according to the issue checklist below
  • Changelog / documentation - mostly of it defered, wrap-up tasks at the end of each EPIC
  • Task/issue checklist: OK
@mpg
Copy link
Contributor Author

mpg commented Sep 29, 2023

Closing as the EPICs had been completed (except the nice-to-have part of 2c).

@mpg mpg closed this as completed Sep 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant