decide which helm versions we want to support
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
What is our policy on which helm versions are valid? We should figure that out, document it, and then ensure that we support those versions in CI... build matrix in linting, perhaps?
Related to #72
(also related to the awesome "multi-line" go-templating that newer versions of helm support, but which we dropped b/c it was not backwards compatible with old versions)
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
Start by reviewing related issue #72 and the repository's existing linting CI build matrix. Determine which Helm versions are currently supported and how newer versions affect the referenced Go templating behavior. Done means an agreed version policy is documented and CI reflects the supported versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- ci-cd, devops, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100