Skip to content
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

Release Team Project Management for top Issues and PRs in WG #643

Open
jbottum opened this issue Aug 15, 2023 · 2 comments
Open

Release Team Project Management for top Issues and PRs in WG #643

jbottum opened this issue Aug 15, 2023 · 2 comments

Comments

@jbottum
Copy link
Contributor

jbottum commented Aug 15, 2023

Each of the Kubeflow Working Groups has a large number of outstanding issues and PRs. We could use a process to triage, process and close these issues. There are too many issues for one person to manage. The WG contributors could use some help, especially on the near term priorities.

Proposal: The Release Team's liaisons may keep a list of top issues and PR. The liaison should provide that list to the WG leads and ask to review it. The list may be reviewed at least once every month. This will provide a feedback loop for users who are asking questions.

@andreyvelich
Copy link
Member

Thank you for open this issue @jbottum!

How this list will be tracked ?
Should we create separate GitHub Project to triage those issues similar to KFP: https://github.com/kubeflow/pipelines/projects/8 ?
cc @zijianjoy

Tagging @money8203 for the suggestions and help for this.

@zijianjoy
Copy link
Contributor

zijianjoy commented Aug 15, 2023

FYI, @gkcalat has implemented the stale GHA in https://github.com/kubeflow/pipelines/blob/master/.github/stale.yml which allows us to mark KFP stale PR/issues with the given wait time.

For KFP, we are triaging issues to SDK, Runtime(backend+frontend), Components, Contribution for different domains. I think each WG can also use their best judgement about how to triage GitHub issues/PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants