Introduce new oldgeneric os_purpose. Stabilize 0102-v2.#1172
Open
garloff wants to merge 2 commits into
Open
Conversation
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
added
enhancement
Member
Author
|
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 ... |
Contributor
|
Not sure we need to bump minor version as long as the standard is in Draft. |
Contributor
depressiveRobot
left a comment
depressiveRobot
left a comment
There was a problem hiding this comment.
According to SCS-0001 Draft phase I would say a new version number is not necessary.
| - Recommended field `os_purpose`. | ||
| - Version 2.0 (this one) makes the field `os_purpose` mandatory. | ||
| - Version 2.0 makes the field `os_purpose` mandatory. | ||
| - Version 2.1 added an `os_purpose` of `oldgeneric`. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Version 2.1 added an `os_purpose` of `oldgeneric`. |
Related to comment above.
Contributor
There was a problem hiding this comment.
We shouldn't omit the change though. It should be included in line 277.
Contributor
There was a problem hiding this comment.
You are right. I'll create an additional suggestion.
Co-authored-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com> Signed-off-by: Kurt Garloff <kurt@garloff.de>
| - Recommendation on `os_version` to be a version number (if such a value exists). | ||
| - Recommended field `os_purpose`. | ||
| - Version 2.0 (this one) makes the field `os_purpose` mandatory. | ||
| - Version 2.0 makes the field `os_purpose` mandatory. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Version 2.0 makes the field `os_purpose` mandatory. | |
| - Version 2.0 makes the field `os_purpose` mandatory and adds a new value `oldgeneric`. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As discussed on SIG Std/Cert on 2026-05-07.
This PR does three things: