Task: Deprecation window for Releasechannel #34
Description
Understand the Task
Description
Sometimes managed components or versions of them cannot stay in a releasechannel due to:
- license change
- bugs
- security problems
The Releasechannel should allow deprecation of components to be done based on defined rules.
One solution could be a regular day in the week where releasechannel updates are promoted which helps to make that process understandable and predictable (releasetrain) for users of MCP landscapes
Solution idea
- sliding window for every version in our releasechannel
- sliding window depends on various factors:
- semantic version (x major versions must be supported/ provided, x minor versions, x patch versions)
- notification alerts can be triggered to notify users of MCP landscapes
- documentation
- kubernetes resource (MCP resource, managed component resource)
- slack
- when the deprecation window is hit, the components must be marked as deprecated and should not be in a releasechannel for longer then x days.
Any further valuable resources.
-
Better scanning in releasechannel can trigger deprecation: Epic: Improve Scanning in Releasechannel #33
-
releasechannel repo (tbd)
-
control-plane-operator (tbd)
-
mcp-operator (tbd)
What is required to accept the Task as done.
Done Criteria
- rules are definable for a releasechannel
- manual overrides are possible for deprecating components
- ocm components are marked in OCI registry (through image labels or special metadata files in ocm component)
- Code has been reviewed by other team members
- Internal technical Documentation created/updated
- New / changed code is documented
- Unit Tests created for new code or existing Unit Tests updated
- Integration Test Suite updated
- Enduser Documentation updated (if applicable)
- Successful demonstration in Review