regular release cycle

[acelinkio]

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

[acelinkio]

Related to #1494

also somewhat related #1493

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[vdemeester]

/lifecycle frozen

This is important that the tektoncd/operator keeps a regular release cycle, align with tektoncd/pipeline, with the same LTS "support" as well (as in when tektoncd/pipeline does a LTS release, the tektoncd/operator that ships that version also is an LTS version)

/cc @tektoncd/operator-maintainers

[dohoangkhiem]

Can someone release a new version for operator with newer Pipelines? The last release was 2 months old, and with Pipeline v0.50.3, while the latest Pipelilnes now is v0.55.0, and according to https://github.com/tektoncd/pipeline/blob/main/releases.md#v053-lts the latest LTS is v0.53.

The operator is great, but TBH I feel it's quite desperate to be unable to control the component versions with the operator. Are their versions hardly bundled into each operator release?

[jkandasa]

@dohoangkhiem sorry for the inconvenience. we will try to maintain the regular release and I will try to release 0.69.1 by this week.

The operator is great, but TBH I feel it's quite desperate to be unable to control the component versions with the operator. Are their versions hardly bundled into each operator release?

The operator manages not only the operand images, also needs the release manifests from the operand repository(example: pipeline release.yaml) and that release.yaml bundled with operator container at build time. right now, it is hard to decouple the operand bundle from the operator.

[jkandasa]

@dohoangkhiem today we released operator version v0.69.1
https://github.com/tektoncd/operator/releases/tag/v0.69.1