-
Notifications
You must be signed in to change notification settings - Fork 125
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
Publish 0.9 release blog #166
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: yuzisun The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for elastic-nobel-0aef7a ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Signed-off-by: Dan Sun <dsun20@bloomberg.net>
Signed-off-by: Dan Sun <dsun20@bloomberg.net>
Signed-off-by: Dan Sun <dsun20@bloomberg.net>
Signed-off-by: Dan Sun <dsun20@bloomberg.net>
Signed-off-by: Dan Sun <dsun20@bloomberg.net>
Signed-off-by: Dan Sun <dsun20@bloomberg.net>
## Introduce InferenceGraph | ||
|
||
The ML Inference system is getting bigger and more complex. It often consists of many models to make a single prediction. | ||
The common use cases are image classification and nature language multi-stage processing pipelines, for example an image classification pipeline needs to run top level classification first then downstream further classification based on previous prediction results. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The common use cases are image classification and nature language multi-stage processing pipelines, for example an image classification pipeline needs to run top level classification first then downstream further classification based on previous prediction results. | |
The common use cases are image classification and natural language multi-stage processing pipelines. For example, an image classification pipeline needs to run top level classification first then downstream further classification based on previous prediction results. |
- Upgrade TorchServe serving runtime to 0.6.0 | ||
- Update MLServer serving runtime to 1.0.0 | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also add links to the full release notes here?
Check out the full release notes for [Kserve](https://github.com/kserve/kserve/releases/tag/v0.9.0) and [ModelMesh](https://github.com/kserve/modelmesh-serving/releases/tag/v0.9.0) for more details.
Signed-off-by: Dan Sun <dsun20@bloomberg.net>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
* Create 2022-07-21-KServe-0.9-release.md Signed-off-by: Dan Sun <dsun20@bloomberg.net> * Update mkdocs.yml Signed-off-by: Dan Sun <dsun20@bloomberg.net> * Update 2022-07-21-KServe-0.9-release.md Signed-off-by: Dan Sun <dsun20@bloomberg.net> * add inference graph image Signed-off-by: Dan Sun <dsun20@bloomberg.net> * update image path Signed-off-by: Dan Sun <dsun20@bloomberg.net> * update blog link Signed-off-by: Dan Sun <dsun20@bloomberg.net> * Add full release notes Signed-off-by: Dan Sun <dsun20@bloomberg.net>
* Create 2022-07-21-KServe-0.9-release.md Signed-off-by: Dan Sun <dsun20@bloomberg.net> * Update mkdocs.yml Signed-off-by: Dan Sun <dsun20@bloomberg.net> * Update 2022-07-21-KServe-0.9-release.md Signed-off-by: Dan Sun <dsun20@bloomberg.net> * add inference graph image Signed-off-by: Dan Sun <dsun20@bloomberg.net> * update image path Signed-off-by: Dan Sun <dsun20@bloomberg.net> * update blog link Signed-off-by: Dan Sun <dsun20@bloomberg.net> * Add full release notes Signed-off-by: Dan Sun <dsun20@bloomberg.net> Signed-off-by: rachitchauhan43 <rachitchauhan43@gmail.com>
"Fixes #issue-number" or "Add description of the problem this PR solves"
Proposed Changes