WIP: try to define what an SCS release is#1157
Draft
jklare wants to merge 1 commit into
Draft
Conversation
* this rework of the existing Release Policies Draft tries to address
the question of what an SCS Release is and why anybody should care
* the goal here is to use the SCS Release to communicate a certain level
of quality about individual parts or full software stacks when trying
to build an SCS certifiable cloud environment
* this rework should also reduce the amount of work required on the SCS
community side when creating an release by:
* moving away from re-releasing software or waiting for
individual software releases to happen
* reusing the work already done by the SCS certification process
as a quality control for viable software stacks to build SCS
compatible clouds
* reducing the release cycles from every 6 months to annually,
to also align with the validity of the certificates
* this rework additionally includes the wording "modular software stack"
to build a basis for marketing communications around this topic and
clearly answer the question what is included, what is not and why
AI-assisted: Claude Code
Signed-off-by: Jan Klare <klare@osism.tech>
Contributor
Author
|
@SovereignCloudStack/project-board based on the discussions we had, here some write-up of my current thoughts :) please let me know what you think! |
fkr
reviewed
Apr 20, 2026
|
|
||
| An SCS Release is an annual attestation that a curated set of third-party | ||
| open-source modular software stacks have been validated as a reliable basis for | ||
| building and operating a "Certified SCS-compatible IaaS" environment. The SCS |
Member
There was a problem hiding this comment.
Suggested change
| building and operating a "Certified SCS-compatible IaaS" environment. The SCS | |
| building and operating "SCS-compatible IaaS" or "SCS-compatible KaaS" environments. The SCS |
Since the Releases are more than just IaaS. Furthermore I would just stick to SCS-compatible without the certified, since the releases can also be used to build environments that are not meant to be certified that want to be compatible whatsoever.
fkr
reviewed
Apr 20, 2026
|
|
||
| To be attested in an SCS Release, a modular software stack MUST be in active | ||
| production use in at least one provider environment that holds a valid | ||
| "Certified SCS-compatible IaaS" certification at the time of the release. This |
Member
There was a problem hiding this comment.
Suggested change
| "Certified SCS-compatible IaaS" certification at the time of the release. This | |
| "Certified SCS-compatible IaaS" or "Certified SCS-compatible KaaS" certification at the time of the release. This |
fkr
reviewed
Apr 20, 2026
|
|
||
| For each modular software stack included in an SCS Release, there SHOULD be | ||
| comprehensive documentation covering the implementation-specific configuration | ||
| necessary to achieve and maintain "Certified SCS-compatible IaaS" compliance. |
Member
There was a problem hiding this comment.
Suggested change
| necessary to achieve and maintain "Certified SCS-compatible IaaS" compliance. | |
| necessary to achieve and maintain "Certified SCS-compatible IaaS" or "Certified SCS-compatible KaaS" compliance. |
fkr
reviewed
Apr 20, 2026
| ### Pillar 3: Automated Integration Testing (SHOULD) | ||
|
|
||
| Automated testing pipelines that validate the full modular software stack used | ||
| to deliver a "Certified SCS-compatible IaaS" environment SHOULD exist at the |
Member
There was a problem hiding this comment.
Suggested change
| to deliver a "Certified SCS-compatible IaaS" environment SHOULD exist at the | |
| to deliver a "Certified SCS-compatible IaaS" or "Certified SCS-compatible KaaS" environment SHOULD exist at the |
Member
|
@jklare thanks for the initiative. I added it to the agenda of today's PB meeting as well! |
Contributor
Author
|
Since we are about to remove the Drafts/ folder from this repository, we should decide what to do with this PR here. Any opinions on how to proceed with this topic? @SovereignCloudStack/project-board |
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
2 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.
AI-assisted: Claude Code