OpenBSW Monthly / 2026-02-23

[rolandreichweinbmw]

Participants

@johannes-esr
@chheis
@rllorca
@rolandreichweinbmw
@darciaobermeierbmw
@christophruethingbmw
Luis Castela
Marzieh Sayyah
@jiyuanwangbmw
Daniel Santos
@dcavalei
@simon-d-bmw
@hans-guenterkothgasserbmw
Joao Faria
@aschaal

Agenda & Meeting Minutes

1. Release Planning
   • Eclipse Process:
     • Eclipse OpenBSW is currently in "Incubation Phase"
       • This means we get more help etc. from the Eclipse Foundation
       • OpenBSW probably a quite mature process (regular meetings etc.), just releases are missing
     • Releases
       • Distinguish between Release/Tag on GitHub and "Eclipse Releases" (see https://www.eclipse.org/projects/handbook/#release)
       • Support from EMO team regarding release -> @johannes-esr to reach out to EMO
       • @johannes-esr to set up release team meeting until May (@johannes-esr , @rolandreichweinbmw , @jiyuanwangbmw)
       • Plan for regular releases, e.g. two times a year (May, November)
         • What is done for a release in addition to the normal CI runs?
           • Test on Hardware (real/simulated) -> would be manually, because no automatic hardware is testing available right now
       • Eclipse suggests no external runners (virtual/on hardware) because of security implications
         • To be checked with Eclipse Helpdesk
2. OpenBSW Release Planning
   • New Features within the last months:
     • DoIP
     • Basic Rust Support
   • In Pipeline:
     • SOMEIP -> @johannes-esr to create a ticket; to be released within the next months
     • Message Routing -> timeline to be checked
     • Extension of Rust Support -> e.g. binding to existing C++ applications
3. Bazel Support
   • Supporting of two build systems (with full features) within OpenBSW probably not desireable
   • Add of bazel rules to integrate OpenBSW in a bazel project with partial support (inclusion of libraries, no run of tests, fixed defaults)
   • Bazel support #97 -> to added to Agenda of next meeting
4. Support for C++17 as base standard of OpenBSW #136
   • see discussion for details
   • Accenture to discuss internally reg. MCU support
   • final decision latest in next meeting

[simon-d-bmw]

@johannes-esr Please add the discussion about using C++ 17 (#136) to the agenda. I would very much appreciate if we could bring this discussion to a decision in the next monthly.

[simon-d-bmw]

Also, I would like to discuss with you the roadmap for the features SOME/IP, and Gateway (msg router)

[dcavalei]

Middleware, discuss the possibility of having a Kotlin code generator.