Skip to content

Implementation ML2 #676

@PandaeDo

Description

@PandaeDo

Epic Description

What to do
From #561
- [ ] 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
- [ ] Action_42: The acceptance criteria for the static code analysis (static, dynamic) shall be defined. --> Add to verification plan
- [ ] 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

Metadata

Metadata

Labels

documentationImprovements or additions to documentation

Type

Projects

Status

No status

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions