[lifecycle&health] Meeting Minutes 2026

[ramceb]

2026-01-07

Agenda

• Review PRs
  • Review if Health monitoring FMEA 2026-01-09 9 am.
• Review Open topics
  • Design proposal for configuration 2026-01-8 4 pm

[pawelrutkaq]

Meeting 2026-01-09, 09:00
https://teams.microsoft.com/l/meetup-join/19%3ameeting_MjMyMDkxNWYtNzIyNS00OTlhLThiZGItYWYzMmYwNzkxNDMz%40thread.v2/0?context=%7b%22Tid%22%3a%22ab1be58c-0a5a-47f0-8b55-1c095dbd46f5%22%2c%22Oid%22%3a%220c966945-d6f6-4ec4-b8b2-fd7770f4bd96%22%7d

@ramceb
@pawelrutkaq
@S-MOHAMD
@NicolasFussberger
@FScholPer

Summary:

We concluded FMEA for HM Library. The summary is documented in code, specifically in this commit: eclipse-score/lifecycle@e5fc9b1

[ramceb]

2026-01-14

Participants

@ramceb
@pawelrutkaq
@S-MOHAMD
@NicolasFussberger
@FScholPer
@odra
@SimonKozik
@vinodreddy-g

Agenda

• Goals for iteration 13 S-CORE Roadmap
  • Integrate lifecycle in reference integration
    • Merge PR Improvement: otterdog extended configuration with branch protection #33 afterwards rename repo from inc_lifecycle to lifeycle.
    • Step 1. Create Release
      • Release 0.0.0 created.
      • Component set up in bazel registry.
    • Step 2: Add to Reference integration
      • Add to reference integration image
      • Provide config to start example apps from reference integration.
      • We start with a MVP and treat all apps as native processes.
    • Step 3: Add lifecycle reference app
• Library topics
  • For the health monitor we want to use the iceoryx2-bb for now. The dependency to iceoryx2 has to be discussed in another context.
• Review open PRs
• Review open topics
• Feedback round
  • Emphasize release planing
  • Agree on release goals

[ramceb]

2026-01-21

Participants

@ramceb
@pawelrutkaq
@S-MOHAMD
@NicolasFussberger
@FScholPer
@odra
@SimonKozik
@vinodreddy-g

Agenda

• Meeting to discuss configuration setup: Friday, 23rd of january, 9-10 am.
• Proposal for migration path from process group to run target based config
  • Decision: The migration path presented is accepted. @NicolasFussberger: Please add presented diagrams to the minutes.
  • Discussion about configuration of alive channels:
    • Decisions:
      • We only have a single alive channel per process.
      • Configuration of the alive channel shall be ready by the application and communicated to the launch_manager via API.
      • @pawelrutkaq Prepare proposal for sequence diagrams between health monitor and launch_manager.
• Review PRs
• Backlog grooming

[NicolasFussberger]

The proposed migration path from ProcessGroups to RunTargets is depicted here:

We are currently thinking that for the intermediate migration steps we can map a RunTarget-based configuration to the ProcessGroup-based implementation as follows: