Logging CFT Weekly [2026-06-16]

[anmittag]

Participants

Agenda & Meeting Minutes

• PR will be rejected due to CI time out of QNX 8
  https://sdvworkinggroup.slack.com/archives/C0894QGRZDM/p1780058512257829 => check for status with Alexander Lanin would it be possible to trigger the re run by a developer?
  Follow-up: https://github.com/orgs/eclipse-score/discussions/2508#discussioncomment-16990977
• change visibility of private interface and introduce a public interface
  • Move the file | runtime.h/.cpp → detail/ folder | Correct location matches the detail namespace |
  • Block direct access | Restrict visibility in Bazel | Build will fail if anyone tries to depend on it from outside |
  • Give a public alternative | Add public API to logging.h | Teams have a safe, supported function to call |
• @MaciejKaszynski to update the https://github.com/eclipse-score/logging/pull/136/changes to include stats as PoC which can be used as a basis for REQ traceability.
• Tracking Milestones for v0.8: https://github.com/eclipse-score/score/milestone/30
• Expectation from Tech Lead circle: Close gaps on Requirements and Architecture design. [create a ticket] - @RSingh1511
• Is there any technical reason why we do not move to score yet? Yes, do not have all the checks in place yet, but we are getting better and confidence through v0.8.
• Cleanup outstanding PRs automatically [Create a ticket]. General consensus is that the PR owner requests for review in slack logging channel OR logging CFT. Same goes for outstanding planned issues in: LOG - Logging FT (view). @rmaddikery @arvindr19

-. AoB

• https://sdvworkinggroup.slack.com/archives/C089XP2PGQZ