Logging CFT Weekly [2026-11-10]

[arsibo]

Participants

Nural Mammadov== u27w81

Agenda & Meeting Minutes

• Meeting Minutes (TL & Communities & CFTs)

• Logging for S-CORE Release v0.10 #3225

  • @rmaddikery : please check the status of Component requirement test coverage for S-Core Release v0.10 logging#318 (move or close?)
  • @rmaddikery : please check the status of Feature requirement test coverage for S-Core Release v0.10 logging#319 (move or close?)
  • task to shift to next delivery
    • [comp log_frontend] Component Requirements check/adapt logging#324 => not complete . need to split up
    • [comp log_backend] Component Requirements check/adapt logging#325 => not complete . need to split up

• discussion on https://github.com/eclipse-score/logging/pull/398/commits by @uwe-martin

• feature requirements (TODO)

  • correct short name of https://eclipse-score.github.io/score/main/features/analysis-infra/logging/docs/requirements/mw-fr_logging_req.html#feat_req__log__err_handling_nonrec
  • check the content of the requirement https://eclipse-score.github.io/score/main/features/analysis-infra/logging/docs/requirements/mw-fr_logging_req.html#feat_req__log__err_handling_nonrec
  • remove valid_from: v2.0.0 feature requirement from the component requirements. Components will fulfill the feature requirements in future
  • @arsibo to move all open issues to v1.0 release

CI

• proposal from @hoppe-and-dreams take over the approach from https://github.com/eclipse-score/communication/blob/main/CI.md

Release planing

v1.00

• planning
  • priorities https://eclipse-score.github.io/reference_integration/main/s_core_v_1/roadmap/pi4.html
  • Logging for S-CORE Release v1.0 #2513
  • Quality status: https://eclipse-score.github.io/logging/main/verification_report/stats.html
  • Perform Req. inspection meeting log frontend logging#347
  • Perform Req. inspection meeting log backend logging#348
  • Perform Req. inspection meeting Datarouter logging#349

ToDo: create issues per line

• All module verification reports (wp__verification_module_ver_report) are approved by a Committer, containing:
  • Architecture coverage: all component architecture elements are linked to at least one test — verdict documented
  • Structural coverage: C0 (line) and C1 (branch) coverage per unit listed and meets targets
  • Static code analysis: 0 open Critical or High findings
  • Dynamic code analysis: 0 sanitizer findings (ASan/UBSan/LSan, TSan)
• The Platform Verification Report (wp__verification_platform_ver_report) is approved by a Committer, containing:
  • Feature requirements coverage: all valid feature requirements are linked to at least one
    Feature Integration Test via FullyVerifies / PartiallyVerifies — pass/fail verdict per requirement documented
  • Feature architecture coverage: all feature architecture elements are linked to at least one test — verdict documented
  • Feature Integration Test results: pass/fail/not_run result per test case documented
  • Feature Integration Test logs: test logs per test case attached

Risks

• Static code analysis: 0 open Critical or High findings/ Static code analysis(CodeQL) checks for Logging logging#262 will not be achievable without infrastructure (code is compliant with C++14 Misra but codeQL check C++23 Misra)
• Dynamic code analysis**: 0 sanitizer findings valgrind infrastructure is missing in CI/CD (works only locally)

v0.10

• planning
  • priorities https://eclipse-score.github.io/reference_integration/main/s_core_v_1/roadmap/pi3.html
  • Quality status: https://eclipse-score.github.io/logging/main/verification_report/stats.html
  • @ALL assigned the task which you can take over to you
  • next meeting we will discuss the capacity situation (unassigend tasks)
• chklst_req_inspection.rst
  • [comp log_frontend] Component Requirements check/adapt logging#324
  • [comp log_backend] Component Requirements check/adapt logging#325
  • [comp log_backend] Implementation completion logging#328
  • [comp datarouter] Implementation completion logging#329

Naming discussion

-29.09.2026 Naming discussion

Repository (repo)	Component (comp)	Component Path (component path)	Sphinx ID (:id:)
baselibs	Log Frontend	./score/mw/log	comp__log
logging	Log Backend	./score/mw/log	comp__log_backend
logging	Datarouter	./score/datarouter	comp__datarouter
logging	DLT Plugin?	./score/???	comp__???
logging	IPC Trace Plugin?	./score/???	comp__???

03.11.2026

@arsibo : discuss with Roland about reuse of Plugin Deployer & Network Accessor over the components
10.11.2026: Roland will discuss the topic in the process meeting

rename feat__logging to feat__logtrace??
@hoppe-and-dreams : add a PR for component clearing
03.11.2026: #3375

• delete the trace folder , log folder shall be the main folder , feature will be renamed to feat__logtrace
  10.11.2026: feat__log_and_trace shall be used. Decission by the CFT.
  -This PR will be handled first Draft: Unifying Logging and tracing feature #3420
• Logging and Tracing Cosmetics #3375 will be checked after
• https://github.com/eclipse-score/score/pull/3358will be checked & merged after 3375
  => @hoppe-and-dreams will handle this

Recurring topics

• Cross-Repo Metrics Report/logging
• Bug list

next meeting agenda

• Risks evaluation
• S-CORE Communication CI Build Jobs and Pipelines Design

Info

• AoB
  • https://sdvworkinggroup.slack.com/archives/C089XP2PGQ