-
Notifications
You must be signed in to change notification settings - Fork 916
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
[kubeflow 1.8] KFP and Kubeflow 1.8 #2446
Comments
I want this to be assigned to be please @DnPlas I am going to start my research |
The following are responses gathered by asking in Slack, emails, and the documents presented in the kubeflow community meetings:
I have asked for clarification on the official channels of communications, at this moment we used slack and email (will define this in the future)
I will also update this as soon as the maintainers change and if any info changes accordingly. |
Hi @kubeflow/wg-pipeline-leads
The 1.8 release team will use this tracking issue to coordinate the integration of KFP with Kubeflow 1.8.
Please note that communications (announcements, updates, questions, follow ups, etc.) will be done through #2442 exclusively, this issue will be closed once the release team gathers the initial information from the WG.
Heads up that the proposed feature freeze is Aug 2nd, 2023, but the date is still subject to agreement and discussed here. Feel free to comment on the issue for suggestions. We will be sharing the finalised timeline before May 8th, 2023.
To prepare for the release, please provide answers to the following questions:
The release team WG liaison for KFP is @Davidnet and you can keep track of high-level release updates in #2442
The text was updated successfully, but these errors were encountered: