add document lifecylce model

[masc2023]

Extend documentation guideline
Add new process requirements

Resolves: #435

[github-actions]

The created documentation from the pull request is available at: docu-html

[PandaeDo]

Could you please also update the Documentation Management Plan?

[pahmann]

Not sure what I should extract from this link as a comparison as it links to a concept not to a list of docment types.

[masc2023]

Indeed is there a table only with inspected work products, just scroll down
inspected work product Id ....

[RolandJentschETAS]

Because any review have to be documented for later safety audits and for analysis of field issues, is there any process requirement, that document reviews and review discussions / participants have to be stored for the whole lifetime of the product (>10 years)?

[masc2023]

Because any review have to be documented for later safety audits and for analysis of field issues, is there any process requirement, that document reviews and review discussions / participants have to be stored for the whole lifetime of the product (>10 years)?

This is considered already during past audits, as part of Github, REviews, etc. but there are work products, which may not require reviews at all. So first step is to identify, which document types we have and then we can see, if Lifecycle model 1 is required or not

[pahmann]

I reviewed the changes, but can really better track the changes with multiple commits and not always the force push to keep a single commit in a PR. I know the history remains, but I have to search much longer and compare potentially several force pushes.
It is common practice for many projects to have a commit history on the PR and do force pushes only for non-reviewed code. We can always squash and merge at the end.
Maybe we can discuss this beginning of next year in a process community meeting. Especially, in case many files are changed addressing review findings over time helps which is harder with the force-pushes.