SRM Notes for 02-10-2025

[glopesdev]

Agenda

• 🚀Small Issue (10 min)
• 🚅Medium Issue (20min)
• 🐢Large Issue (45min)

Reviewing

• Unified releases 🐢
  • Decision to use the Behavior board as the first test case
  • Three options for unified release:
    • CI/CD with existing core (1.13) and current firmware
    • CI/CD with latest ATxmega core (1.14):
      • New build of behavior board firmware
      • Release a Bonsai client compliant with the latest core features
      • Cherry-picked release of harp-tech/protocol (v1.14.0)
      • Caution with possible impact of clock synchronizer changes
    • CI/CD with stable protocol spec (v2.0.0, to be released)
      • Finalize and publish v2.0.0 of protocol spec
      • Develop and publish a new ATxmega core implementing the v2.0.0 required registers only
      • Release a Bonsai client compliant with the v2.0.0 protocol spec
      • New build of Behavior board firmware with that new ATxmega core
• Need to start discussing plans for SfN 🚀
• Requested org at PyPI 🚀
• How to specify hardware targets in YAML 🚀
  • No functional difference at runtime, since YAML registers are what matters
  • Will be used by CI/CD to generate firmware build assets and automatically populate metadata registers at build time, and for documentation pages, e.g. compatibility table
  • Should be treated as a list of strings, following semver to make sure it matches the information in R_VERSION