Repository navigation
Implementation ML2 #676
Description
Epic Description
What to do
From #561
- [x] Action_27: No coding guideline for RUST exists. Coding standards need to be defined. -> https://eclipse-score.github.io/score/main/contribute/development/rust/coding_guidelines.html - Guidelines are up to date. Action Item will be closed for now as we have external dependencies which can't be solved for Implementation ML2
- [x] Action_42: The acceptance criteria for the static code analysis (static, dynamic) shall be defined. --> Add to verification plan
- [x] Hint during audit: Document compiler checks.
https://github.com/eclipse-score/process_description/issues/540
https://github.com/orgs/eclipse-score/discussions/1501
Planning from 29th April Roland Jentsch, Volker Häussler
- Roland will focus on technical details, Volker will update the process description
Acceptance Criteria (DoD)
All tasks done
Activity
RolandJentschETAS commentedon May 13, 2026
Will take the action about the rust coding guidelines.
RolandJentschETAS commentedon May 22, 2026
See also #544
RolandJentschETAS commentedon Jun 25, 2026
See
S-CORE
eclipse-score/score#2984 - improve rust coding guidelines and add CodeQL
score_rust_policies
eclipse-score/score_rust_policies#11 -> feat: add Cargo.toml lint profiles for relaxed and strict baselines