Interest Group: Release Team

[antonkri]

2025-08-05

Participants

@antonkri

Meeting Minutes & Agenda

• Review proposal for goals and next steps
• What has happened till now
  • Reference integration concept:
    • 
    • The 1st draft of score repository structure proposal #1475
  • Qemu Demo
    • https://github.com/eclipse-score/reference_integration/tree/main/qnx_qemu
• Agreed on who takes over which activity:
  • @rafaelfronza takes over responsibility on documenting and setting-up the reference integration repo and gate and @AlexanderLanin will support him:
    • [I-Gate] Define repo structure & integration strategy #1542
    • reference integration automation & module PR feedback #1543
  • @odra will take over set-up of RedHat Linux image and its execution in Qemu. For this @odra will contact @mohamed riad to see how it was done for Qnx.
    • [Unit-Test] Toolchain roll out in I-Gate #1546
  • @odra will take over gcc integration and update
    • [GCC] Toolchain roll out in I-Gate #1544
  • @Xinq will take over qcc integration and update
    • [QCC] Toolchain roll out in I-Gate #1545
• Agreed on follow-up date to review planning of activities
  • Follow-up meeting in 3 weeks to present current status and results
  • @antonkri Set-up a special meeting for those who decided to help to give a better overview how the integration into bazel should happen.

[opajonk]

@antonkri Please send me the invite for the next meetings as well; I think I got missed in the first round.

[tmewett]

I would like to join too, if possible

[evinoth1206]

Hello, I would like to also join in the reference integration topic. Is this already discussed in any of the regular exchange meetings?

[AlexanderLanin]

This discussion is quite old. Nevertheless please note that we have a concept discussion at https://github.com/orgs/eclipse-score/discussions/1966

[FScholPer]

2026-02-06 Kickoff Meeting

Participants

@antonkri
@FScholPer
@AlexanderLanin
@anmittag
@opajonk
@PiotrKorkus
@pawelrutkaq
Antonio Rosario Intilisano
@NicolasFussberger
@evinoth1206
@kgraeper
@MaximilianSoerenPollak
@masc2023

Agenda

• timeline
• reference_integration repo reshape into reusable state (already lot done on prep_0.6 branch)
• branching strategy proposal
  • "release/v0.6" on ref_int.
  • force other modules also to create a release branch?
• Unit-test measurement coverage and reporting in reference_integration
• Downloadable image, ideally raspi
• execution of sanitizers in reference_integration for cpp components
• Formal release aspects,
  • https://eclipse score.github.io/process_description//main/process_areas/release_management/release_workflow.html#wf__rel_platform_rel_note
    https://eclipse-score.github.io/process_description//main/process_areas/release_management/release_workflow.html#wf__rel_mod_rel_plan
    https://eclipse-score.github.io/process_description//main/process_areas/quality_management/quality_workflow.html#wf__vy_ap_pltrelease
    https://eclipse-score.github.io/process_description//main/process_areas/release_management/release_workflow.html#wf__rel_mod_rel_plan

Meeting Minutes

• timeline -> freeze begin of 9th of Feb 2026. Release date will be 23th of Feb 2026
• Contents of the release
  • QNX Image
  • Unit test coverage
    • 1. Step @pawelrutkaq will prep a pr of prep_0.6 branch of reference_integration to restructure the repo
    • 2. Step Create a release branch "release/0.6" in reference_integration repo
  • FT can decide if they want to use release branches or master for the release
  • AI: @FScholPer create a polly for two meetings next week in slack
  • Code Coverage: Template in https://github.com/eclipse-score/docs-as-code/blob/main/.github/workflows/test_and_docs.yml
  • @antonkri AI: takes care of the c++
  • @kgraeperAI: Change the unit-test.yaml
• Binary Raspi build eblinux exists but in beta -> next meeting @opajonk keeps update
• Raspi tarball still not accessible -> @antonkri update

[NicolasFussberger]

I would like to know the future of reference_integration/qnx_qemu. Whether this is the correct place to integrate further modules?
Currently, reference_integration/qnx_qemu is using very old versions of dependencies and seems to be independent of the "known_good" module combination.

[antonkri]

Unit-test measurement coverage and reporting in reference_integration

[antonkri]

Downloadable image, ideally raspi

[antonkri]

execution of sanitizers in reference_integration for cpp components

[masc2023]

Formal release aspects,
https://eclipse-score.github.io/process_description//main/process_areas/release_management/release_workflow.html#wf__rel_platform_rel_note
https://eclipse-score.github.io/process_description//main/process_areas/release_management/release_workflow.html#wf__rel_mod_rel_plan
https://eclipse-score.github.io/process_description//main/process_areas/quality_management/quality_workflow.html#wf__vy_ap_pltrelease
https://eclipse-score.github.io/process_description//main/process_areas/release_management/release_workflow.html#wf__rel_mod_rel_plan

[FScholPer]

2026-02-11 Release Team Meeting

Participants

@PiotrKorkus
@masc2023

Agenda

• Bazel.module
• Rust Coverage

Meeting Minutes

• New version in bazel.module will be 0.0.0. Rest still the same
• Rust Coverage please use the ferrocene toolchain
• @PiotrKorkus will align with Eelco to do the next steps for coverage

[FScholPer]

2026-02-13 Release Team Meeting

Participants

Agenda

• Checklist v0.6
• Reference Integration Update

Meeting Minutes

• Reference Integration restructuring still in progress

• Coverage still in progress

[FScholPer]

2026-02-18 Release Team Meeting

Participants

@antonkri
@4og
@pawelrutkaq
@PiotrKorkus
@dcalavrezo-qorix
@AlexanderLanin
@nradakovic
@RolandJentschETAS
@pawelrutkaq
@masc2023
J Lukasz
@MaximilianSoerenPollak
@johannes-esr

Agenda

• FEO part of the release or not
• Release notes
• Current state Reference Integration
• Logging state
• Unit tests (not everything works)- Baselibs
• AutoSD failing
• EB Linux

Meeting Minutes

• AutoSD & EBLinux open
• QNX tarball working
• Updated Release Checklist
• FEO experts are currently not responding via Slack. Will be discussed at tech lead circle tomorrow. Proposal: exclude for now, FEO can raise PR in reference_integration to add it back in. // Update: @johannes-esr will look into it.
• No further blockers identified

[odra]

is this meeting in the shared calendar?

[RolandJentschETAS]

2026-02-18 Release Team Meeting

Participants

@PiotrKorkus
@RolandJentschETAS
@pawelrutkaq
@FScholPer
@MaximilianSoerenPollak
@odra
@opajonk
@AlexanderLanin
@4og
Dan Calavrezo
Glamsch, Johannes

Agenda

Checklist v0.6

Meeting Minutes

• Updated Release Checklist

• Highlights:

• Baselibs is fine
• FEO is not included in V0.6 (also not in reference integration)
• Communication from main latest version shall be used
• Bazel cpp toolchain 0.2.2
• Logging 0.1.0
• Persistancy 1.3.0
• Platform 0.5.3
• test_scenarios 0.4.0
• toolchin v0.4.0
• tooling 1.1.2
• lifecycle 0.1.0

• PR for v0.6 created, but will not be finished until 23.2.2026