Skip to content

Conversation

@masc2023
Copy link
Contributor

@masc2023 masc2023 commented Nov 4, 2025

No description provided.

@github-actions
Copy link

github-actions bot commented Nov 4, 2025

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


- @{{CONTRIBUTOR_1}}
- @{{CONTRIBUTOR_2}}

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This template misses know limitations which means relevant open issues. This is relevant for component, feature, and platform.
For platform level it needs to collect features.
For feature it needs to collect the component issues.

Explicit CVE report makes also sense as known limitations.
Same would make be helpful for safety.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Template updated with missing information, but we have only platform and module releases, not more. CVE Section added

# *******************************************************************************

# Some portions generated by Co-Pilot

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There need to be the purpose of the release described. E.g. what is the safety level.
What is the release maturity: Ranging from only for testing in virtual environment up to production ready.
I assume this cannot be auto generated. So there might be the need by someone like a quality manager or project lead which gives an overall statement on the achieved quality.

We should consider a link to the user documentation of the released software as e.g. feature documentation within the feature repo.

Another point could be the external dependencies to other components.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please let's discuss about maturity in our meetings, not changed so far.

### Refactoring
- {{REFACTOR_1}} ([#{{PR_NUMBER}}]({{PR_LINK}}))

EST_UPDATE_1}} ([#{{PR_NUMBER}}]({{PR_LINKentation
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
EST_UPDATE_1}} ([#{{PR_NUMBER}}]({{PR_LINKentation
EST_UPDATE_1}} ([#{{PR_NUMBER}}]({{PR_LINK}}

Wrong style in this and other line.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changed

# *******************************************************************************

# Some portions generated by Co-Pilot

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it a good idea to have a disclaimer on what we promise and what not?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added

@masc2023 masc2023 force-pushed the add_release_templates branch 2 times, most recently from 2b1f847 to c639541 Compare November 18, 2025 07:38
@masc2023 masc2023 marked this pull request as ready for review November 18, 2025 07:39
@masc2023 masc2023 force-pushed the add_release_templates branch from c639541 to 3004164 Compare November 18, 2025 09:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants