chains
chains copied to clipboard
Chains v1.0.0
We want to cut a stable release for Chains.
Most of our actual feature set has been stable for some time - we don't expect any major changes to how chains operates.
However, there are still things we want to tackle before a v1 is cut, primarily around library stability and testing:
- [ ] Pipelines Regression Testing
- [x] https://github.com/tektoncd/chains/issues/716
- [ ] Add tests to catch changes in pipelines versions.
- [x] https://github.com/tektoncd/chains/issues/640 (Should we remove this from here?)
- [x] https://github.com/tektoncd/chains/issues/665
- [ ] https://github.com/tektoncd/chains/issues/1044
- [ ] https://github.com/tektoncd/chains/issues/968
- Needs a lot of effort. We may end up rushing this if we want this for v1. Instead we could add it as a feature that needs to be enabled.
Things that are not in scope:
- SLSA v1.0 support (additive feature)
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.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
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 rotten
Send feedback to tektoncd/plumbing.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/close
Send feedback to tektoncd/plumbing.
@tekton-robot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopenwith a justification. Mark the issue as fresh with/remove-lifecycle rottenwith a justification. If this issue should be exempted, mark the issue as frozen with/lifecycle frozenwith a justification./close
Send feedback to tektoncd/plumbing.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Is it possible to re-open this? Seems it was auto-closed but some of the chains v1.0.0 TODO issues are still open.
/reopen /lifecycle froze
@wlynch: Reopened this issue.
In response to this:
/reopen /lifecycle froze
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/lifecycle frozen
Created an issue for the client lib work: https://github.com/tektoncd/chains/issues/1044