update of change management to consider new FEP proposal#748
Conversation
masc2023
requested review from
PandaeDo,
RolandJentschETAS,
aschemmel-tech and
pahmann
as code owners
|
The created documentation from the pull request is available at: docu-html |
qor-lb
left a comment
qor-lb
left a comment
There was a problem hiding this comment.
Definitely goes into the right direction, thanks! some minor changes below.
| Use the content :ref:`Decision Record Template <decision_record_template>` to create a | ||
| Change Request. |
There was a problem hiding this comment.
Not every change should/must end up in a decision record. I tried to also document this in the CMP in score. The DR/FEP path should be only for "bigger"/"major" changes - because this path also takes a lot more time to find agreement. We should still have a shorter path for smaller changes that don't need that level of alignment.
Can we somehow separate the information that has to be available in a change request from the format? That way we could then define in the CMP in score that major changes persist this information in a DR via the FEP and that smaller changes can still move forward if this information is only available in a issue without needing a prior DR?
There was a problem hiding this comment.
Currently https://github.com/eclipse-score/.github/blob/24c3501a931460f1d89123a3ea21750c414e7f22/.github/ISSUE_TEMPLATE/1a_FeatureRequest.yml defines which work products are affected by Change Request, "Scope" changes, otherwise, just fill out a normal taks, w/o Change Management, using https://github.com/eclipse-score/.github/blob/24c3501a931460f1d89123a3ea21750c414e7f22/.github/ISSUE_TEMPLATE/4_Task.yml
2 participants
As proposed the Change Management process is updated to reflect the FEP.
Resolves partly: eclipse-score/score#3085