Persistency FT Meeting Minutes 2026

[vbogdanb]

Persistency FT Meeting Minutes 2026

[vbogdanb]

Meeting minutes 2026-01-08->2026-01-22:
https://github.com/orgs/eclipse-score/discussions/1680#discussioncomment-15445877
https://github.com/orgs/eclipse-score/discussions/1680#discussioncomment-15507542
https://github.com/orgs/eclipse-score/discussions/1680#discussioncomment-15570887

[vbogdanb]

Weekly 2026-01-29

Participants

@vbogdanb - Bogdan B.
@Ahmed-Elsaka-JC - Ahmed E.
@PandaeDo - Volker H.
@tizava - Tibor Z.
@arkjedrz Arek
@vinodreddy-g Vinod

Meeting Minutes

eclipse-score/persistency#182 -> to fix after common interface definition
eclipse-score/persistency#227 comp req should be rework and reviewed
The component shall encode each key as valid UTF-8? -> @tizava
https://github.com/eclipse-score/persistency/actions/runs/21214394044/job/61151306834?pr=172 -> @arkjedrz

eclipse-score/persistency#230 -> review and check findings from @arkjedrz
@vbogdanb Ask about safe writing in the Architecture Meeting, ask about snapshot,hash validation, test tool usage from OEMs

[vbogdanb]

Weekly 2026-02-12

Participants

@vbogdanb - Bogdan B.
@Ahmed-Elsaka-JC - Ahmed E.
@PandaeDo - Volker H.
@tizava - Tibor Z.
@arkjedrz Arek
@umaucher

Meeting Minutes

Snapshots decision:

• Will keep snapshots
• Will remove snapshot rotation
• Will modify the api to explicitly create snapshots and load them in memory

SnapshotCreate(SnapshotID)
SnapshotDelete(SnapshotID)
SnapshotRestore(SnapshotID)
SnapshotCount()
SnapshotMaxCount()

New snapshot functions will not be added to the current kvs api inside eclipse-score/persistency#172 !

Doc-as-code will be fixed, expected next week
Do not resolve reviewer comments in the PR !!! ( Reviewers will re-review the fix and resolve the comments)
If PR come too late for offline review , they will not be discussed in the Pers meeting. They will be mentioned so people can have a offline review of them.

New folder structure definition -> eclipse-score/module_template#40 (comment)

eclipse-score/persistency#182 -> to fix after common interface definition
eclipse-score/persistency#227 comp req should be rework and reviewed - @vbogdanb @tizava to be done by 2026-03-12
The component shall encode each key as valid UTF-8? -> @tizava

@vbogdanb Ask about safe writing in the Architecture Meeting, ask about snapshot,hash validation, test tool usage from OEMs