spinframework / spinframework/spin-operator
bump SpinAppExecutor CRD version and automate updating CRD versions on release
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 289
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
I believe this should have been done as part of the v0.2.0 release since there was a change to the SpinAppExecutor CRD and going forward we should outline when and how we should be bumping CRDs.
Contributor guide
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
Review the v0.2.0 release changes and the current SpinAppExecutor CRD versioning. Determine where CRD versions are maintained and how releases are performed; done means the CRD is bumped appropriately and future releases automate or clearly define when and how version updates occur.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100