update change management plan #1706
Conversation
|
The created documentation from the pull request is available at: docu-html |
|
For me this is step 2. As long as there is no branch protection in the modules. |
Unclear, what do you mean? |
I mean as long as there are pushes to master allowed in some repositories without any issue it makes no sense to activate this part of the process |
Then I set it back to draft, please consider, what we want then show at the next audit as real working example |
|
@antonkri we need the process fullfiled until next audit( I know you are working on that) |
|
|
||
| name: "Change Request" | ||
| description: Issue to track a change | ||
| title: "Change: Your Change Request title" |
There was a problem hiding this comment.
How about title: "Change Request: Your Change Request title"
.github/ISSUE_TEMPLATE/3-change.yml
Outdated
| options: | ||
| - label: Feature Request/Modification | ||
| - label: Component Request/Modification | ||
| required: true |
There was a problem hiding this comment.
Any reason why "component modification" is required?
update to reflect changes in process description eclipse-score/process_description#167 and eclipse-score/process_description#148 Resolves: eclipse-score#1310 Change-Id: I6a58c1f0c457c654230e01ffb30a179b1729bcf4
originates from CR #135090