SovereignCloudStack / SovereignCloudStack/cluster-stacks
Create release branches with version generator
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
/kind feature
Describe the solution you'd like
With #101 we're now able to create the scs Cluster Stacks in various versions without code repetition.
That makes it possible to create releases with one code base.
The downside ist, that the code for the releases doesn't exist in the repository.
To solve this the different versions should be stored in release branches, named after Kubernetes versions.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
- Kubernetes version: (use
kubectl version) - OS (e.g. from
/etc/os-release):
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the approach from #101 and the existing version generator, then determine how Kubernetes-version-named release branches should be created and maintained. Done means the repository contains the requested release branches generated from the shared code base.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100