Repository navigation
Rework of component requirements related to snapshots - #337
Conversation
tizava
commented
Jul 10, 2026
- Snapshots are now explicit (Driven by the users)
- Snapshots are created from live data (Not from data flushed to disk)
- New API to acquire status of the snapshot slot (Occupied/Free)
- General rework and cleanup
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
PandaeDo
left a comment
There was a problem hiding this comment.
Please have a look again on the requirements. It seems to me that they are not fully atomic. You can use https://eclipse-score.github.io/process_description//main/process_areas/requirements_engineering/guidance/requirements_templates.html#gd_temp__req_formulation and also the question if the requirement is testable. Understandable they are.
|
@tizava there are checks failing, please adapt and review comments. please care |
| :version: 1 | ||
| :derived_from: feat_req__persistency__snapshot_create[version==1] | ||
| :belongs_to: comp__persistency_kvs[version==1] | ||
| :tags: inspected |
There was a problem hiding this comment.
changed / new requirements needs to be tagged as valid
There was a problem hiding this comment.
Fixed with last commit
Requirements fixes
|
The created documentation from the pull request is available at: docu-html |
|
|
||
| .. note:: | ||
|
|
||
| This requirement is invalid after change of snapshot handling (see <ticket-id>) |
There was a problem hiding this comment.
where is ticket-id ?
|
|
||
| .. note:: | ||
|
|
||
| This requirement is invalid after change of snapshot handling (see <ticket-id>) |
0271ee7