DR-001-Arch: Consistent Stack vs. Reference Integration #2560
Conversation
qor-lb
requested review from
PandaeDo,
aschemmel-tech,
masc2023 and
pahmann
as code owners
|
|
|
The created documentation from the pull request is available at: docu-html |
qor-lb
requested review from
FScholPer,
antonkri and
johannes-esr
as code owners
|
Seems related to #2346, Feature as stand-alone Delivery? |
Yes agree, added it to the list in the description above. |
FScholPer
left a comment
FScholPer
left a comment
There was a problem hiding this comment.
What option is accepted or did I miss something?
aschemmel-tech
left a comment
aschemmel-tech
left a comment
There was a problem hiding this comment.
see inline comment
| - Specify CI/CD implementations or quality gates. | ||
| - Define release cadences or versioning strategies. | ||
| - Provide a migration plan for existing modules. | ||
| - Specify how architectural discussions are conducted or moderated. |
There was a problem hiding this comment.
Please include something like: "This approach does not prevent the use-case of independent module (or feature) delivery. I.e. the modules/features are still independent enough to be able to be released as a SEooC.
There was a problem hiding this comment.
@aschemmel-tech I added a paragraph to clarify that it is not the goal to constrain the modularity of the stack. Does this suffice or would you like to have the wording differently?
FScholPer
left a comment
FScholPer
left a comment
There was a problem hiding this comment.
no accepted option defined
@FScholPer the decision is right after the context: https://github.com/eclipse-score/score/pull/2560/changes#diff-7605e72a4577a9aeeadf15aca38407709dc0eff885ee5684e8d46097ef932da8R44 |
7 participants
Formal decision record based on discussion during last architecture community workshop: https://github.com/orgs/eclipse-score/discussions/1922#discussioncomment-14871055
This intends to establish a discussion basis for further technical dr's such as:
Important
This PR will be kept open at least until 13th Feb before merging to ensure that necessary reviews can be conducted.