-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Tekton Pipelines Topical Ownership #3662
Conversation
Question, do we also want to add some |
We identified topic areas in Tekton Pipelines and established explicit ownership on specific areas of the codebase in https://docs.google.com/document/d/1k4ZDcdpfjq_LUxR2D3Ka16kvtZMCd1moZCgFqnCaq4w/edit Topical owners are responsible for triaging bugs, reviewing TEPs and moving along any work in their topic areas
8672a01
to
3a567f8
Compare
sure, will add that to the next steps |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbwsg, vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Changes
We identified topic areas in Tekton Pipelines and established explicit
ownership on specific areas of the codebase in doc
Topical owners are responsible for triaging bugs, reviewing TEPs and
moving along any work in their topic areas
Next step would be automating tagging topical owners on issues, PRs
and TEPs on their topic areas
/kind misc
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes