docs: add DR-003-Strat — Module Maturity Classification (Release / Experimental / Preview) - #3124
docs: add DR-003-Strat — Module Maturity Classification (Release / Experimental / Preview)#3124antonkri wants to merge 4 commits into
Conversation
github-project-automation
Bot
added this to
S-CORE Roadmap and TLC - Technical Lead Circle
|
to be discussed in the next TL circle |
|
The created documentation from the pull request is available at: docu-html |
|
looks like a good proposal. But as result we should add kpis and add it to the metamodel |
aschemmel-tech
left a comment
aschemmel-tech
left a comment
There was a problem hiding this comment.
In principle ok, some improvements suggested.
|
|
||
| **Release** | ||
|
|
||
| - The module implements **all** currently existing feature and component requirements. |
There was a problem hiding this comment.
I would add "unless excluded by the valid_from / valid_until attributes"
|
|
||
| - The module implements **all** currently existing feature and component requirements. | ||
| - All feature and component requirements are **fully covered / tested**. | ||
| - The module provides **all artifacts** mandated by the current state of the S-CORE developer |
There was a problem hiding this comment.
To differentiate this from the almost identical sentence in section "Experimental", maybe here write "in valid state" and below "at least in draft state"?
| | Deviations from process | undetermined | major, but transparent | minor only | | ||
| | Requirements implemented | undetermined | not necessarily all | all currently existing | | ||
| | Requirements covered / tested | undetermined | not necessarily all | fully | | ||
| | Quality statement possible | no | yes (with known gaps) | yes | |
There was a problem hiding this comment.
It is not clear to me what the "quality statement" is. Which work product(s)?
There was a problem hiding this comment.
Code Quality, Unit-test coverage
anmittag
left a comment
anmittag
left a comment
There was a problem hiding this comment.
- adapt meta model (docs-as-code) to enable the documentation: Release, Experimental, ....
- module provider / maintainer shall manage the attribute
- adapt the process description accordingly
4 participants
New Decision Record introducing three maturity levels for modules (Release / Experimental / Preview).
This makes it possible to include all modules in platform releases while giving users clear guidance on each module's maturity and intended usage. Builds on DR-001-Strat (consistent stack).
Status: draft.