v1 Release of Results

[khrm]

@afrittoli Shared:

The Tekton Pipeline project is preparing for its v1.0 release. We discussed this during the  Pipeline WG today, and one of the points that was brought up is that it would be very nice to coordinate the v1.0 release of pipeline with the v1.0 release of several other Tekton components.

I'm reaching out to the maintainers of the various Tekton projects to ask what they think about releasing a v1.0, possibly after the summer. Having a coordinated v1.0 release would have the benefit of aligning our release numbers too and hopefully make our users'  life easier when combining Tekton components.

So a tracker of things that needs to be done before v1:

• Epic: resolve bugs related to CEL filtering and add missing filters #506
• Tekton Results CLI release  #524
• Update release pipelines for attestation #525
• Add Support for Tekton Pipeline v1 APIs  #352 Support Tekton v1 APIs #303
• Improve log messages and log configurations #543

[khrm]

@adambkaplan @alan-ghelardi @sayan-biswas Please add what needs to be done before we can do v1.

[adambkaplan]

I'm inclined to say "whoah, hold on" when it comes to declaring us ready for v1 when we don't even have a declared "v1beta1" API yet. We have a very small timescale of active contributions and known production usage compared to the core Pipelines API and other APIs that feel they are ready for v1. Keeping the APIs at "alpha" and "beta" levels gives us the freedom to make significant breaking changes as a community. This becomes much harder if we declare a v1, since v1 implies a strong level of support and stability.

[alan-ghelardi]

Agree with Adam's comments. I'd prefer keeping the project in the alpha stage until wee all are really comfortable with a stable API. In the "search API" for example, we started making significant improvements recently and I believe that breaking changes may keep happening.

[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.

[khrm]

/remove-lifecycle stale