Operator releases #350
Replies: 3 comments
-
cc @tektoncd/operator-collaborators @tektoncd/operator-maintainers |
Beta Was this translation helpful? Give feedback.
-
@vdemeester Thank you for starting this discussion. 🧑💻 👍
I think a
Let us stop following pipeline's version and have our own version series. One year back following pipeline version made sense as there were only pipeline and triggers and the same reconciler installed everything. But now as there are more components, different platform support, and multiple components pipeline version based release numbers for operator are confusing.
👍
👍 |
Beta Was this translation helpful? Give feedback.
-
https://github.com/tektoncd/operator/blob/main/docs/release/README.md |
Beta Was this translation helpful? Give feedback.
-
I think we need to rethink the way we do Operator releases. At the time of the creation of this discussion, the latest release is
v0.23.0-2
, whiletektoncd/pipeline
and other component release about 2 releases.First, we need to release more often, at least as the same cadence as
tektoncd/pipeline
, which is monthly. We have to setup some habits around this. Have some milestone, and have some goals of what we want to ship in each new releases (operator's feature, in addition to the version of the component we ship).We need to define the "release" triggers, aka what makes the operator do a release:
In addition, we may want to rethink the versioning number
component
Finally, we need to release all our target at the same time. Right now, we only release the
kubernetes
target, and I think this doesn't make much sense (mainly because there is a disconnect between the platforms on what they ship).Creating this discussion to gather some ideas and feedback before trying to come up with a more definite plan.
Beta Was this translation helpful? Give feedback.
All reactions