regular release cycle
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
Hey team! Trying to use an operator when ever available. The current version of this operator is 2 months old and missing fixes from newer components.
Docs mention releases to be twice a month for catching all of the updates to Tekton related components. Any chance on having this follow a regular release cadence?
https://github.com/tektoncd/operator/blob/main/docs/release/README.md#faq
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 with docs/release/README.md, especially its FAQ section, and compare the documented twice-monthly release expectation with the current operator version and available component fixes. Clarify the release process and ownership before defining what a regular cadence would require; done would mean an agreed, documented cadence that keeps the operator current.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100