You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: