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.

Sign up for GitHub

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

Jump to bottom

Clearly display the conformance status for reports #3183

Open
mlavacca opened this issue Jul 4, 2024 · 4 comments
Open

Clearly display the conformance status for reports #3183

mlavacca opened this issue Jul 4, 2024 · 4 comments
Labels
area/conformance kind/documentation Categorizes issue or PR as related to documentation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone
v1.3.0

Comments

@mlavacca
Copy link
Member

mlavacca commented Jul 4, 2024 •
edited
Loading

What would you like to be added:

#3179 stated the possibility for implementations to submit partial reports. We need to accommodate this information in the documentation page, to make clear whether the conformance status is partial or success.

/cc @xtineskim
@mlavacca mlavacca added the kind/documentation Categorizes issue or PR as related to documentation. label Jul 4, 2024
@mlavacca
Copy link
Member Author

mlavacca commented Jul 4, 2024

/area conformance

@mlavacca mlavacca mentioned this issue Jul 4, 2024
Merged
@xtineskim
Copy link
Contributor

Im thinking that the clearest/easiest way to show this would be to have a separate table that lists the Partial implementations

@mlavacca
Copy link
Member Author

Im thinking that the clearest/easiest way to show this would be to have a separate table that lists the Partial implementations

+1 I think this is the way to go

@shaneutt
Copy link
Member

/triage accepted
/priority important-longterm

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Sep 20, 2024
@shaneutt shaneutt added this to the v1.3.0 milestone Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/conformance kind/documentation Categorizes issue or PR as related to documentation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Gateway API Pipeline
Status: Next
Milestone
v1.3.0
Development

No branches or pull requests
4 participants
@shaneutt @k8s-ci-robot @xtineskim @mlavacca