-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1 Release of Results #526
Comments
@adambkaplan @alan-ghelardi @sayan-biswas Please add what needs to be done before we can do v1. |
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. |
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. |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
/remove-lifecycle stale |
@afrittoli Shared:
So a tracker of things that needs to be done before v1:
The text was updated successfully, but these errors were encountered: