[FEO Weekly 2025-05-12]

[johannes-esr]

Participants

Agenda

Review of Project Board

• FEO FT (view)

Planning of Milestones

• 2025-05-30 Functional Gap Analysis S-CORE v0.5 Completed / https://github.com/eclipse-score/score/milestone/10
  • Epic: Functional gap analysis for feature "Fixed Execution Order" #883
    • Already some gaps identified (see subtickets) -> what's missing?
• 2025-06-01 S-CORE v0.5 Release Candidate / https://github.com/eclipse-score/score/milestone/14
  • Epic: Create requirements for feature "FEO" #938
    • FEO Feature Request already includes some requirements, but probably not all -> how to proceed?
  • Epic: Create architecture artifacts for feature "FEO" #941
• 2025-10-01 S-CORE v0.5 Feature Complete / https://github.com/eclipse-score/score/milestone/19
• 2025-12-01 S-CORE v0.5 Certifiable / https://github.com/eclipse-score/score/milestone/23

[ramceb]

Minutes

• To fulfill MS https://github.com/eclipse-score/score/milestone/19 we need a Rust implementation for QNX8. So we have a dependency to Enable Rust Targets for QNX #816.
• We need templates for Component and Feature Safety/Security Analyses.
• 2025-12-01 S-CORE v0.5 Certifiable / https://github.com/eclipse-score/score/milestone/23 shall be broken down 2-3 month.
• Overall consideration: We start with feature and component requirements and architecture- Afterwards we do a detailed planing for die Milestones "S-CORE v0.5 Feature Complete" and "S-CORE v0.5 Certifiable"
• Feedback to architecture and TL round: FEO will most likely use the preliminary APIs of mw::com and mw::log as the final APIs will not be available in time.
• @arsibo Please put this on the agenda of the architecture round in 2 weeks