OpenBSW Monthly / 2026-07-06

[rolandreichweinbmw]

General

• Time: 11:00 CEST
• Meeting link: https://eclipse.zoom.us/j/86834108303?pwd=eMjZBzFbDkOkZgX8i0rzPpGOgFBuoo.1#success

Participants

@rolandreichweinbmw
@aschaal
@simon-d-bmw
@christophruethingbmw
@danielfaleirosantos
@jiyuanwangbmw

Agenda

• OpenBSW Release Process
  • Review process successful: https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/work_items/1125
  • Next steps:
    • Define Release Timeplan, with @johannes-esr
    • Proposal: 6 months release interval? -> 3 months release interval?
    • Maintenance?
    • Do we add features to a release? Or only bugfixes?
    • E.g. add bugfixes for the last release, and maintain older releases only on demand. Start low-profile at first.
    • Release requirements:
      • Tests run on hardware and/or virtual tests: Available only proprietary maybe, and external to github.com workflows
      • Tests run on POSIX: Available at github.com
      • Branch
• Safety in ETL
  • Already supported (recently added):
    • Static code analysis: Clang-tidy, clang-format
    • Review process includes more formal reviews
    • More commiters formally assigned
    • Documentation now maintained in the repo, Hugo/Markdown: https://etlcpp.com
    • Test coverage report via lcov
  • What is missing: Concrete support for ISO26262?
    • Expected release plan? Timeline for features?
    • Certificate process, in parallel to release process, propose to ETL
    • Start with safe subset of ETL to qualify
    • MC/DC coverage: Only available with latest OSS tooling, expected to be widely available later this year
• PTP (@johannes-esr )
• FLYNC (https://www.flync-language.com/ by Technica) for OpenBSW (@LarsVoelker, @rllorca)
• Issue Refactor UDS request APIs to use ETL views #510
  • Adjustment to using etl::array and etl::span is considered natural refactoring, also for public interfaces
  • Review by @christian-schilling