Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guidance on CPE pattern (for CSAF 2.0) #740

Merged
merged 3 commits into from
Jun 11, 2024

Conversation

tschmidtb51
Copy link
Contributor

- addresses parts of oasis-tcs#693
- add FAQ regarding usage of the new pattern
- addresses parts of oasis-tcs#693
- clarify that the pattern was changed in CSAF 2.1
Copy link
Contributor

@sthagen sthagen left a comment

Choose a reason for hiding this comment

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

LGTM.

@santosomar
Copy link
Contributor

During the 2024-05-29 CSAF TC monthly meeting we discussed that a motion will be send via email to approve the changes as suggested.

@tschmidtb51 tschmidtb51 marked this pull request as ready for review May 29, 2024 20:42
@tschmidtb51 tschmidtb51 added motion This item has a motion pending and removed tc-discussion-needed labels May 29, 2024
@santosomar
Copy link
Contributor

The motion to accept the pull request as suggested in #740 and include it into the guidance towards CSAF 2.0, has passed. It automatically carried on 2024-06-05 23:00 UTC.
https://groups.oasis-open.org/discussion/motion-for-740

Copy link
Contributor

@santosomar santosomar left a comment

Choose a reason for hiding this comment

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

Thank you for all your contributions @tschmidtb51 !

@santosomar santosomar merged commit 1fe65d6 into oasis-tcs:master Jun 11, 2024
5 checks passed
@tschmidtb51 tschmidtb51 removed the motion This item has a motion pending label Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
csaf 2.0 csaf 2.0 work
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants