update process_description and doc-as-code version #2259
Conversation
masc2023
requested review from
a team,
AlexanderLanin,
PhilipPartsch,
aschemmel-tech,
dcalavrezo-qorix and
pahmann
as code owners
|
|
|
The created documentation from the pull request is available at: docu-html |
|
|
||
| * :need:`rl__safety_manager` to :need:`rl__technical_lead` | ||
| * :need:`rl__technical_lead` to :need:`rl__project_lead` | ||
| * :need:`rl__safety_manager` to :need:`rl__project_lead` |
There was a problem hiding this comment.
In the security management we have the escalation to a "steering committee". Should we not align this with the safety manager's escalation path. i.e. first to the PL and then to the "steering committee" for both managers?
There was a problem hiding this comment.
Yes, Security Management at the moment is not on the same maturity level as Safety Management, will follow, when the new version is available, please make a ticket, this version change is mainly to make the red colors available, so that we have it available for the audit. Further Release, v1.4.0 anyhow is planned
There was a problem hiding this comment.
ok, understood it is an issue in security management
aschemmel-tech
left a comment
aschemmel-tech
left a comment
There was a problem hiding this comment.
see inline comment
aschemmel-tech
left a comment
aschemmel-tech
left a comment
There was a problem hiding this comment.
ok, lets merge as is
doc-as-code: 2.0.3 process_description: 1.3.2 major changes, red color for ASIL B removing rl__technical_lead and rl__module_lead
masc2023
force-pushed
the
update_pd_dac_versions
branch
from
b767639 to
4757a8a
Compare
doc-as-code: 2.0.3 process_description: 1.3.2 major changes, red color for ASIL B removing rl__technical_lead and rl__module_lead
doc-as-code: 2.0.3
process_description: 1.3.2
major changes, red color for ASIL B
removing rl__technical_lead and rl__module_lead