Modify valid_from/until attribute description - #800
Conversation
|
hi, you were too fast for me (I also missed to set the status to "draft") |
There was a problem hiding this comment.
Did you consider to make the valid_from mandatory, as currently implemented in the doc-as-code meta model?
Compare discussions here, https://sdvworkinggroup.slack.com/archives/C0864L05332/p1790669268509239 and https://sdvworkinggroup.slack.com/archives/C0864L05332/p1790673556715339
|
The created documentation from the pull request is available at: docu-html |
|
thank you for the hint, will change process description to have mandatory valid_from in stkh and feat req. |
| :complies: std_req__aspice_40__SWE-1-BP2[version==1], std_req__aspice_40__iic-17-54[version==1] | ||
|
|
||
| Stakeholder, feature and component requirements can have a validity attribute that tells | ||
| Stakeholder and feature requirements shall and component requirements can have a validity attribute that tells |
There was a problem hiding this comment.
So Stkh, Feat Requirements needs now both mandatory, valid_from, until? Current meta model has only valdi_from mandatory, until is optional, seems ok for me, as if it shall be used for ever, valid_from is enough, until not required, means if not exists, valid for all future version
There was a problem hiding this comment.
agree to keep valid_until optional, this is described in "gd_req__req_attr_valid_until" which says "Stakeholder, feature and component requirements can have a validity attribute"
There was a problem hiding this comment.
I see, the until is still can, reading only the diff here, does not show it, so it is fine
3 participants
complements #799