...
Meeting notes 2024-02-13:
- Release Planning
- Branch usage:
- Release Instruction updated according to discussion.
- Erik: Suggesting the following issues/PRs shall be closed at next meeting unless there are comments/remarks
- Unit handling
- Wheel speed - and possibly a wider discussion on "overlapping signals"
- Summary: Today we have individual wheel speed measured as km/h
- Request for rad/s (possibly degrees/s would work as well)
- Anyone objecting having both km/h and degrees/s, as they may support partially different usecases.
Release Planning - Instance handling (Left/Right vs Driver/Paeenger)
- Use of discussions instead of issues
- Issue handling - general
- What to do with issues where there has not been any progress in many months
- Keep forever or decide on an auto-close policy?
- Should be doable at least for suggestions/discussions
- For limitations/defects - possibly manage elsewhere? Like in documentation for the related tool.
- Example: Signal Accuracy - https://github.com/COVESA/vehicle_signal_specification/issues/105
- Possible improvement area, but no-one seems to be interesting actively driving it
- Example: Emission standards - https://github.com/COVESA/vehicle_signal_specification/issues/394
- Possible improvement area, but no-one seems to be interesting actively driving it
- Issues are of different types today, some maybe fit better as discussion, but also then we have a question on how long we want them to exist
- Possible improvement areas
- Actual limitations/error (which no-one intends to fix)
...
{"serverDuration": 549, "requestCorrelationId": "0db676d9da5c11b7"}