-
Notifications
You must be signed in to change notification settings - Fork 44
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.9] Define Kubeflow 1.9 Roadmap for Model Registry #3
Comments
drafting so far:
no specific version required, there is a MR Python client on PyPI: https://pypi.org/project/model-registry/
we will likely tag an alpha version, once ready from default branch (into specific branch if needed for branching-out).
Knative (not used) maybe check the MR tests have gone through the KF1.9 supported versions? tracker |
/assign @tarilabs |
updated drafting so far:
no specific version required, there is a MR Python client on PyPI: https://pypi.org/project/model-registry/
we will likely tag an alpha version, once ready from default branch (into specific branch if needed for branching-out).
Knative (not used) maybe check the MR tests have gone through the KF1.9 supported versions? |
I would suggest creating a separate "Roadmap" issue outlining the high-level the roadmap throughout the next months and releases, since it seems like this was discussed extensively in meetings. Also, let's think about how we can onboard new users to the Model Registry once we release 1.9. Most importantly:
|
This commit will add Neha to model-registry OWNERS file
Hello @rareddy @tarilabs, this is a kind reminder that Monday, March 4th will be our Kubeflow 1.9 release development checkpoint, we will be halfway through our dev cycle, and we expect most of the work to be well underway (reminder: code freeze is scheduled for Apr 15th) Can you please acknowledge your status with respect to your roadmap, comment on the progress made so far, and provide an assessment of the work that remains? (understandably) Not everything may be completed in time. Please proactively let the release team know if there are delays, blockers, or uncertain situations, know so that we can align expectations and try and help you out, if possible. Please, can you update the first comment in this issue with a check of tasks that need to be completed for a successful Model Registry alpha release? There are quite a few things being discussed in comments here and elsewhere (meeting notes etc.). Let's try and consolidate into a plain list of deliverables. |
With MR part of KF 1.9: https://blog.kubeflow.org/kubeflow-1.9-release/#model-registry , The next roadmap tracker can be found at: |
For Kubeflow 1.9 roadmap needs to be defined.
ml-metadata
project as the initial repository to build a Model Registry.no specific version required, there is a MR Python client on PyPI: https://pypi.org/project/model-registry
this issue [Kubeflow 1.9] Define Kubeflow 1.9 Roadmap for Model Registry #3
Test with KF 1.9 Kubernetes version #44
incorporated into: Update kubeflow/model-registry manifests from v0.2.0-alpha manifests#2697
tracked with Add Kubeflow Model Registry Network Policies manifests#2701
(not a blocker for KF1.9 release)
stretch goals:
References
KF 1.9 version matrix tracker:
The text was updated successfully, but these errors were encountered: