-
Notifications
You must be signed in to change notification settings - Fork 288
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
[release]: python ML library opensearch-py-ml #2814
Comments
We are in process of automating releases so it might fall under |
AFAIK, that is for front end components (if any). @bbarani please correct if I am wrong. |
@bbarani Thanks for your answer. I have 2 follow up questions:
|
Hello @dhrubo-os @ylwu-amzn Does this have to be released along with OpenSearch 2.4 release? As per my understanding, this is a standalone library and can be released independent of 2.4 release. Please let us know if this has to be released on specific time coinciding with any other release. |
Hi @bbarani Yeah this is a standalone library and can be release independent of 2.4 release. That being said, this plugin will help customer to simplify of few steps in mlCommons custom model feature, which is why we want to release this plugin asap. Please suggest what are the steps are remaining from our end to release this plugin. Thanks |
Hi @dhrubo-os, For now below are the to-do on our list:
|
The release was successful. Get the artifacts here: https://pypi.org/project/opensearch-py-ml/ |
What is the name of your component?
opensearch-py-ml
What is the link to your GitHub repo?
https://github.com/opensearch-project/opensearch-py-ml
Targeted release date
Nov 15
Where should we publish this component?
pypi
What type of artifact(s) will be generated for this component?
python library
Have you completed the required reviews including security reviews, UX reviews?
Security review will be done by Nov 12.
Have you on-boarded automated security scanning for the GitHub repo associated with this component?
Yes
Additional context
No response
The text was updated successfully, but these errors were encountered: