fix audit findings action_78, action_66, action_68#617
Conversation
|
The created documentation from the pull request is available at: docu-html |
aschemmel-tech
left a comment
aschemmel-tech
left a comment
There was a problem hiding this comment.
see inline comments
process/process_areas/change_management/change_management_workflow.rst
Outdated
Show resolved
Hide resolved
aschemmel-tech
left a comment
aschemmel-tech
left a comment
There was a problem hiding this comment.
comments fixed but issue still in draft
masc2023
changed the title
masc2023
changed the title
masc2023
force-pushed
the
masc2023_fix_audit_findings
branch
from
23b9aba to
8a95708
Compare
process/process_areas/problem_resolution/guidance/problem_resolution_guideline.rst
Outdated
Show resolved
Hide resolved
process/process_areas/problem_resolution/guidance/problem_resolution_checklist.rst
Outdated
Show resolved
Hide resolved
process/process_areas/problem_resolution/guidance/problem_resolution_checklist.rst
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Should be reformulated, as now there are more versions to report in the template (First/Last Affected Release) - to clearly solve Action_68
There was a problem hiding this comment.
New formulation is "Document the first version where the problem was detected and the last affected version." - which is a bit misleading, because there can be a new bug found (in the field) which is present not only in the release where it was found but also in previous (and possibly later) releases.
…s covered, but the version which are based on the faulty version needs to be identified too.
masc2023
force-pushed
the
masc2023_fix_audit_findings
branch
from
8a95708 to
e0976f2
Compare
aschemmel-tech
left a comment
aschemmel-tech
left a comment
There was a problem hiding this comment.
partly fixed but two comments (one on old finding) added
process/process_areas/problem_resolution/guidance/problem_resolution_guideline.rst
Outdated
Show resolved
Hide resolved
aschemmel-tech
left a comment
aschemmel-tech
left a comment
There was a problem hiding this comment.
all findings resolved
2 participants
Action_78: It shall be defined who evaluates and accepts/ rejects Change Requests for Feature Changes and for Component Changes.
Action_66: Elaborate, what is a topic and what happens if a critical topic is not accepted.
Action_68: The version in which the Safety Anomaly was detected is covered, but the version which are based on the faulty version needs to be identified too.
Resolves: #567
Resolves partly: #557
Depends on #619, so Merge this PR after #619 is merged