Chains v1.0.0
Open
Nobody has claimed this yet.
lifecycle/frozen
- Dominant language
- Go
- Stars
- 277
- Forks
- 164
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 61
Description
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
- https://github.com/tektoncd/chains/issues/716
- Add tests to catch changes in pipelines versions.
- https://github.com/tektoncd/chains/issues/640 (Should we remove this from here?)
- 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)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the unchecked Pipelines Regression Testing item and review issue 716, then inspect the remaining linked work in issues 1044 and 968. Determine the tests needed to catch pipeline-version changes and verify that all required v1 release items are resolved or explicitly scoped before the stable release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, security, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100