-
Notifications
You must be signed in to change notification settings - Fork 220
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
KServe roadmap for KF 1.10 #775
Comments
KServe roadmap: https://github.com/kserve/kserve/blob/master/ROADMAP.md |
/assign @vrajjbhatt |
@rimolive: GitHub didn't allow me to assign the following users: vrajjbhatt. Note that only kubeflow members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hi @vrajjbhatt please request membership to the kubeflow org. Follow up the next steps: https://github.com/kubernetes/community/blob/master/community-membership.md Thanks
|
0.14 VERSION released already. |
@juliusvonkohout @rimolive to work models webapp issues. and confirm any challenges ahead for this release. |
@rimolive @varodrig @terrytangyuan @tarekabouzeid can you help with rebasing/forking the 5 PRs here and merging them https://github.com/kserve/models-web-app/pulls We also need someone to go trough https://github.com/kserve/models-web-app/issues and close or confirm whether they are still valid. |
kserve 0.14 synced in manifests kubeflow/manifests#2908 |
Should we leave this open if there is a kserve 0.14.1 release? |
Hello @dansun @terrytangyuan
The 1.10 release team will use this tracking issue to coordinate the integration of the KServe with the Kubeflow 1.10 release.
Heads up that the feature freeze is scheduled for January 20th 2025 (needs confirmation). For the full release schedule, refer to the 1.10 release timeline.
(note: links are pending due to #761)
To prepare for the 1.10 release, please provide answers to the following questions:
The release team WG liaison for Pipelines WG will be @vrajjbhatt and you can keep track of high-level release updates in the #768 issue.
The text was updated successfully, but these errors were encountered: