Skip to content

Introduce new oldgeneric os_purpose. Stabilize 0102-v2.#1172

Open
garloff wants to merge 3 commits into
mainfrom
feat/0102-oldgeneric-and-stabilize
Open

Introduce new oldgeneric os_purpose. Stabilize 0102-v2.#1172
garloff wants to merge 3 commits into
mainfrom
feat/0102-oldgeneric-and-stabilize

Conversation

@garloff
Copy link
Copy Markdown
Member

@garloff garloff commented May 18, 2026

As discussed on SIG Std/Cert on 2026-05-07.

This PR does three things:

  • Introduce a new os_purpose oldgeneric. As only the generic images have the uniqueness requirements, we don't need a catch-all "old" nor do we need oldXXXX at this point.
  • By consequence, change the standard to v2.1.
  • Stabilize it.

As discussed on SIG Std/Cert on 2026-05-07.

This PR does three things:
- Introduce a new os_purpose oldgeneric. As only the generic images
  have the uniqueness requirements, we don't need a catch-all "old"
  nor do we need oldXXXX at this point.
- By consequence, change the standard to v2.1.
- Stabilize it.

Signed-off-by: Kurt Garloff <kurt@garloff.de>
@garloff garloff self-assigned this May 18, 2026
@garloff garloff requested a review from fkr as a code owner May 18, 2026 09:00
@garloff garloff added enhancement New feature or request standards Issues / ADR / pull requests relevant for standardization & certification labels May 18, 2026
@garloff
Copy link
Copy Markdown
Member Author

garloff commented May 18, 2026

Obviously, every single aspect can be debated. If we need a significant amount of discussion, it will probably be better to split this into several PRs. Let me know ...

@mbuechse
Copy link
Copy Markdown
Contributor

Not sure we need to bump minor version as long as the standard is in Draft.

Copy link
Copy Markdown
Contributor

@depressiveRobot depressiveRobot left a comment

Choose a reason for hiding this comment

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

According to SCS-0001 Draft phase I would say a new version number is not necessary.

Comment thread Standards/scs-0102-v2-image-metadata.md Outdated
Comment thread Standards/scs-0102-v2-image-metadata.md Outdated
Co-authored-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com>
Signed-off-by: Kurt Garloff <kurt@garloff.de>
@depressiveRobot depressiveRobot self-requested a review May 20, 2026 13:42
Comment thread Standards/scs-0102-v2-image-metadata.md Outdated
Co-authored-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com>
Signed-off-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com>
@depressiveRobot depressiveRobot self-requested a review May 29, 2026 10:24
Copy link
Copy Markdown
Contributor

@depressiveRobot depressiveRobot left a comment

Choose a reason for hiding this comment

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

Still some open issues for me:

  • field stabilized_at must be added
  • Are adjustments to the conformance tests needed?
  • Do we also want to deprecate v1 with this PR?

title: SCS Image Metadata
type: Standard
status: Draft
status: Stable
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.

Suggested change
status: Stable
status: Stable
stabilized_at: 2026-06-01

When we stabilize, stabilized_at must be added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request standards Issues / ADR / pull requests relevant for standardization & certification

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

3 participants