...

• Agenda discussion - anything that needs to be added?
• Prioritized Topics:
• Decision on old open PRs
• Open Pull Requests VSS
• Open Pull Requests VSS-Tools
• Issues VSS
• Issues VSS-Tools
• Prioritized topics for next meeting

Meeting notes  2023-11-07:

• Prioritized Topics
  • Release Preparation
    • Decision needed - shall we only release 4.1 and not 5.0?
      • Potential rationale: The only "major changes" we have is unit/datatype/semantic change of 5-10 signals. Historically not sufficient for a "major" release, or?
      • Working assumption: We do not release 5.0 now as no requests, plan for spring instead
      • AP: Erik to check with Pierre Pierre Blais if Blackberry sees a value in a major relase now
      • If your organization wants a 5.0 before christmas, please let us now
      • AP: Erik to update 4.X branches (cherry pick)
    • Timeframe static id change
      • Adnan: working on hash support in addition to sequential id, compared 64 bit sv 32 bit hash.
      • Adnan: For hashing path, type, unit and datatype is used

Meeting notes  2023-10-31:

• Prioritized Topics
  • Static UID - draft PR at https://github.com/COVESA/vss-tools/pull/305
    • New script vspecID.py 
    • Give vspec files as both input and output
    • You can specify prefix with "gen-layer-ID-offset", first 64 reserved for COVESA. WIth id layer 4 bytes, otherwise 3 bytes
    • Adds a staticUID string, like '0x02345678'
    • "--validate-static-uid <old.vspec>" gives option to keep/replace if changed, if compatible (like name check)
    • You maintain static id files yourself
    • Once you have the generated .vspec/ .yaml, then with overlay you can run all other tools, like vspec2json
    • Erik: Can be included in minor release, as it does not affect UUID
    • Pierre: The Blackberry model serves the same purpose, different approach
    • Pierre: How to manage addressing by old name, if name is changed.

...