Skip to content

Replace yaml scopes by regular standards#1199

Merged
mbuechse merged 10 commits into
mainfrom
feat/scope-standards
Jul 24, 2026
Merged

Replace yaml scopes by regular standards#1199
mbuechse merged 10 commits into
mainfrom
feat/scope-standards

Conversation

@mbuechse

@mbuechse mbuechse commented Jun 6, 2026

Copy link
Copy Markdown
Contributor

Resolves #1198

This is meant as a preview of a quite radical change. It's possible that multiple PRs would be needed to be in line with extant regulations.

@jklare

jklare commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Any clue why the link checks are failing here?

@mbuechse

Copy link
Copy Markdown
Contributor Author

@jklare Not really. The links do work. Maybe the docs page is defending itself against bots :)

@jklare jklare left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM, thanks for pushing this. I think this is a lot easier to understand when trying to figure out which tests need to pass and what the difference between each of the scope version is. I added a couple of questions and comments.

Comment thread Standards/scs-0501-v3-scs-compatible-iaas.md
Comment thread Standards/scs-0501-v5-scs-compatible-iaas.md
Comment thread Standards/scs-0501-v5-scs-compatible-iaas.md Outdated
Comment thread Standards/scs-0501-v3-scs-compatible-iaas.md Outdated
Comment thread Standards/scs-0501-w1-scs-compatible-iaas-testing.md Outdated
Comment thread Standards/scs-0502-w1-scs-compatible-kaas-testing.md Outdated
@mbuechse
mbuechse force-pushed the feat/scope-standards branch from e4182e6 to 09a2044 Compare July 22, 2026 19:57

@jklare jklare left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM, let's get this merged. Since I am unsure if you want this to be squashed as one big things or separate commits, I will leave the honours to you @mbuechse :)

@jklare

jklare commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

This should probably be rebased before being merged.

mbuechse added 10 commits July 24, 2026 09:59
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
@mbuechse
mbuechse force-pushed the feat/scope-standards branch from f0334ee to 9ca87ac Compare July 24, 2026 07:59
@mbuechse
mbuechse merged commit ff0ce9a into main Jul 24, 2026
9 of 10 checks passed
@mbuechse
mbuechse deleted the feat/scope-standards branch July 24, 2026 08:12
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.

[Cleanup] Replace YAML scopes by regular standards [Cleanup] Split implementation part off of certification specification

2 participants