We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello @kubeflow/wg-pipeline-leads @zijianjoy
The 1.9 release team will use this tracking issue to coordinate the integration of the Pipelines with the Kubeflow 1.9 release.
Heads up that the feature freeze is scheduled for April 15th (needs confirmation). For the full release schedule, refer to the 1.9 release timeline.
(note: links are pending kubeflow/community#687 and kubeflow/community#690)
To prepare for the 1.9 release, please provide answers to the following questions:
The release team WG liaison for Pipelines WG will be @milosjava and you can keep track of high-level release updates in the #2600 issue.
The text was updated successfully, but these errors were encountered:
Tracking issue kubeflow/pipelines#10402
Sorry, something went wrong.
For the Tekton version, it will be Tekton 0.53.2 (OpenShift Pipelines 1.13)
No branches or pull requests
Hello @kubeflow/wg-pipeline-leads @zijianjoy
The 1.9 release team will use this tracking issue to coordinate the integration of the Pipelines with the Kubeflow 1.9 release.
Heads up that the feature freeze is scheduled for April 15th (needs confirmation). For the full release schedule, refer to the 1.9 release timeline.
(note: links are pending kubeflow/community#687 and kubeflow/community#690)
To prepare for the 1.9 release, please provide answers to the following questions:
The release team WG liaison for Pipelines WG will be @milosjava and you can keep track of high-level release updates in the #2600 issue.
The text was updated successfully, but these errors were encountered: