Persistency FT Meeting Minutes 2025

[joshualicht]

All official meetings will be documented in this thread (starting 2025-08-28 as agreed in #1629)
So if you subscribe here, you'll get summaries of the meetings you missed.

[joshualicht]

Weekly 2025-08-28

Participants

@Elsaka-Ahmed-JC
@joshualicht

Agenda

Pull Requests (no drafts)

Open

testing DDD #76 #74
Dcalavrezo test rep #31
kvs_cpp: Adapt to Module Folder Structure #76
impl: consistent instance params #87
gitlint: Use gitlint from score #96
testing: reimpl supported datatype CITs #97

Closed

fix get all keys function #82
formatting: remove trailing whitespace #85
impl: change flush_on_exit APIs #86
Add S-CORE devcontainer #88
fix string literal conversion #89
use mw log instead of cout #90
Add score_python_basics bazel MODULE #93
impl: use interior mut for flush_on_exit #94
impl: make IDs implement Copy trait #95

Meeting Minutes

• C++: Snake Case (persistency) vs Pascal Case (other Repos)
  -> Snake Case is coming from Rust Naming Convention
  -> Pascal Case is used in C++ Components
  Desicion to be taken in the next Meeting 2025-09-04

• C++: Mockable API for KVS:
  -> Problem regarding static open() method (refer to this fork branch: mock_api
  Proposal from @Elsaka-Ahmed-JC: Remove static from open functionality -> return shared pointer (also to prepare access dictionary of available/opened kvs objects)
  Ideas to be discussed in the next Meeting 2025-09-04

• C++: Detailed Design
  -> There should be a template for detailed design, which should be used for all components
  This should be addressed in Architecture Community

Open Points

• Avoid changing the API in both C++ and Rust without discussing in the FT Meeting. No merges should take place beforehand

[vbogdanb]

Weekly 2025-09-04

Participants

@joshualicht
@vbogdanb
@umaucher
@vinodreddy-g
@arkjedrz
@Ahmed-Elsaka-JC
@PandaeDo

Agenda

Pull Requests (no drafts)

Open

Meeting Minutes

• Decided to follow what fits best for each language related to naming convention:
  -> Snake Case for Rust
  -> Pascal Case for C++

• C++: Mockable API for KVS
  Will be solved when we change to having a pool of kvs instances, this will remove the open function and the loading of kvs will be done in the in the builder.
  Hiding the KVS public constructer will be required.

• C++: Detailed Design
  Template available https://eclipse-score.github.io/process_description/main/process_areas/implementation/guidance/implementation_guideline.html

Open Points

• Discussion related to the usage of flash_on_exit

[vbogdanb]

Weekly 2025-09-11

Participants

Agenda

• How should the "storage_mode" be abstracted from Builder API (regarding set permission for kvs file persistency#107)

Pull Requests (no drafts)

Open

• Flush_on_exit will be removed and flush function should be updated to return error/success
• Investigate providing storage backend to the builder and transition from one backend to another
• To be review impl: instance pool based on global state persistency#91 and aligned with update kvs build to avoid reopen opened instance. persistency#102

[vbogdanb]

Weekly 2025-09-18

Participants

@umaucher
@vbogdanb
@PandaeDo

Agenda

• Flush_on_exit will be removed and flush function should be updated to return error/success
• Investigate providing storage backend to the builder and transition from one backend to another
• To be review impl: instance pool based on global state persistency#91 and aligned with update kvs build to avoid reopen opened instance. persistency#102

Meeting Minutes

Short meeting because of low participation

Pull Requests (no drafts)

Open

[vbogdanb]

Weekly 2025-09-25

Participants

@umaucher
@vbogdanb
@PandaeDo
@arkjedrz
@Ahmed-Elsaka-JC

Agenda

• Flush_on_exit removed from RUST(impl: remove flush_on_exit persistency#125) and C++ will be next(CPP: remove flush on exit persistency#122)
• To be review impl: instance pool based on global state persistency#91 and aligned with update kvs build to avoid reopen opened instance. persistency#102

Meeting Minutes

• CPP: implement CIT tests persistency#124 to be done , hint: https://github.com/eclipse-score/inc_mw_per/tree/main/tests

Pull Requests (no drafts)

Open

• Testing on QNX target
• Please review: Backend API changes - backends independent from filesystems persistency#126 Backend API changes - backends independent from filesystems persistency#126
• Review the KVS architecture
• KVS backend diagram from storage

[vbogdanb]

Weekly 2025-10-02

Participants

@umaucher
@vbogdanb
@arkjedrz
@Ahmed-Elsaka-JC

Agenda

Meeting Minutes

• We need to have a KVS Backend to enable multiple storage types

Pull Requests (no drafts)

Open

• @arkjedrz Provide a demonstration on abstraction
• Review the KVS architecture
• Review requirements

[vbogdanb]

Weekly 2025-10-16

Participants

@umaucher
@vbogdanb
@arkjedrz
@Ahmed-Elsaka-JC

Agenda

Meeting Minutes

• We need to have a KVS Backend to enable multiple storage types

Pull Requests (no drafts)

Open

• Review of requirements
• @vbogdanb To raise in the architecture community a discussion about std::abort

[vbogdanb]

Weekly 2025-10-23

Participants

@umaucher
@vbogdanb
@arkjedrz
@Ahmed-Elsaka-JC
@tizava
@doodspav
@vinodreddy-g

Agenda

Meeting Minutes

• We need to have a KVS Backend to enable multiple storage types
• https://eclipse-score.github.io/score/main/features/persistency/kvs/requirements/index.html
• https://eclipse-score.github.io/process_description/main/process_areas/requirements_engineering/index.html
• https://github.com/eclipse-score/score
• @vbogdanb Question about release req? Question about workflow?

Pull Requests (no drafts)

Open

• Review of requirements pull request -> target 2025.11.13
• @vbogdanb To raise in the architecture community a discussion about std::abort -> Maybe not nlohmann or if it possible to raise a contribution request for a qualified parser

[vbogdanb]

Weekly 2025-10-30

Participants

@umaucher
@vbogdanb
@arkjedrz
@Ahmed-Elsaka-JC
@doodspav

Agenda

Meeting Minutes

• We need to have a KVS Backend to enable multiple storage types
• https://eclipse-score.github.io/score/main/features/persistency/kvs/requirements/index.html
• https://eclipse-score.github.io/process_description/main/process_areas/requirements_engineering/index.html
• https://github.com/eclipse-score/score
• Release requirements: Prepare s-core v0.5 alpha release #1925
• Workflow discussions ongoing

Pull Requests (no drafts)

Open

• Review of requirements pull request -> target 2025.11.13
• @vbogdanb To raise in the architecture community a discussion about std::abort -> Maybe not nlohmann or if it possible to raise a contribution request for a qualified parser

[vbogdanb]

Weekly 2025-11-06

Participants

@umaucher
@vbogdanb
@arkjedrz
@Ahmed-Elsaka-JC
@doodspav
@tizava

Agenda

Meeting Minutes

• We need to have a KVS Backend to enable multiple storage types
• https://eclipse-score.github.io/score/main/features/persistency/kvs/requirements/index.html
• https://eclipse-score.github.io/process_description/main/process_areas/requirements_engineering/index.html
• https://github.com/eclipse-score/score
• Release requirements: Prepare s-core v0.5 alpha release #1925
• Workflow discussions ongoing

Pull Requests (no drafts)

Open

• Review of requirements pull request -> target 2025.11.13
• @vbogdanb To raise in the architecture community a discussion about std::abort -> Maybe not nlohmann or if it possible to raise a contribution request for a qualified parser
• release notes, having short description of the provided functionality as comment in the release tag of the module -> @vbogdanb
• one pagers for c++ and rust kvs -> @doodspav

[vbogdanb]

Weekly 2025-11-20

Participants

@umaucher
@vbogdanb
@arkjedrz
@Ahmed-Elsaka-JC
@doodspav
@PandaeDo
@atarekra

Agenda

• C++ KVS requires hash file for defaults, but Rust does not persistency#170 -> @arkjedrz
• resolves #2000 Persistency feature requirements rework #2001
• Test Cases for default values in case of CPP added persistency#171
• impl: backend design change persistency#150
• impl: custom types support persistency#149

Meeting Minutes

• C++ KVS requires hash file for defaults, but Rust does not persistency#170 -> @arkjedrz
• resolves #2000 Persistency feature requirements rework #2001 -> We shall not specify the version format
• Test Cases for default values in case of CPP added persistency#171 -> @vbogdanb look into the comment
• impl: backend design change persistency#150 -> Next week simplified version by @arkjedrz with no backend handling , do decide on the design by next week

[arkjedrz]

Weekly 2025-11-27

Participants

@umaucher - Uwe M.
@arkjedrz - Arek J.
@Ahmed-Elsaka-JC - Ahmed E.
@PandaeDo - Volker H.
@tizava - Tibor Z.
@atarekra - Ahmed T.-R.

Agenda

• resolves #2000 Persistency feature requirements rework #2001 - @tizava
  • Let's give it another week for reviews and merge it next week (soft deadline 4.12.2025).
• C++ tests: Test Cases for default values in case of CPP added persistency#171
  • @vbogdanb or @arkjedrz, provide a comment. To be discussed next week (4.12.2025).
• Simplified Rust's backend for Persistency: impl: new backend API persistency#173
  • To be merged.
  • Some final review by @tizava?
• Design diagram by @Ahmed-Elsaka-JC: Draft persistency#172
  • To be discussed further - waiting for additional comments.
  • Rewrite to PlantUML is preferred.

Meeting Minutes

Written as a subpoints in Agenda.

[vbogdanb]

Weekly 2025-12-04

Participants

@vbogdanb - Bogdan B.
@umaucher - Uwe M.
@Ahmed-Elsaka-JC - Ahmed E.
@PandaeDo - Volker H.
@tizava - Tibor Z.
@atarekra - Ahmed T.-R.
@@doodspav - Paul

Agenda

eclipse-score/persistency#182 -> to fix after common interface definition
#2001 -> will be closed by next week
C++ tests: eclipse-score/persistency#171 -> @vbogdanb (11.12.2025)
Simplified Rust's backend for Persistency: eclipse-score/persistency#173 -> Please review until next week (11.12.2025)
@vbogdanb Ask about safe writing

[vbogdanb]

Weekly 2025-12-11

Participants

@vbogdanb - Bogdan B.
@umaucher - Uwe M.
@Ahmed-Elsaka-JC - Ahmed E.
@PandaeDo - Volker H.
@atarekra - Ahmed T.-R.
@doodspav - Paul
@arkjedrz Arek

Agenda

• Cpp KVS does not reflect if the default value is set. persistency#182 -> to fix after common interface definition
• Refactor self-move warning suppression persistency#191 to be reviewed @doodspav
• Architecture almost aligned
• @vbogdanb Ask about safe writing in the Architecture Meeting
• https://github.com/eclipse-score/persistency/pull/189/changes to be reviewed @doodspav . @vbogdanb
• impl: new backend API persistency#173 to be reviewed @vbogdanb , @doodspav
• C++ KVS Does Not Update Snapshot Count on First Flush persistency#192 -> @Ahmed-Elsaka-JC
• Cpp KVS does not reflect if the default value is set. persistency#182 -> to fix after common interface definition

0.5-beta checks

• Update doc-as-code version to 2.2.0

• Usage of Toolchain gcc 0.0.5 tag

• Ensure ALL targets can be compiled with Linux toolchain for x86/(arm). This check should be part of module release workflow.

• Ensure ALL targets can be compiled with QNX toolchain for x86/(arm). This check should be part of module release workflow.

• Ensure ALL unit-test targets (Linux host) can be successfully executed. This check should be part of module release workflow.

• [C++ modules only] Ensure unit-test coverage is measurable (gcov)

• Create a release containing meaningful release notes and publish it to the bazel registry

• Provide more detailed description of the release in the overall release notes: S-CORE v0.5 beta release notes #2300