Skip to content
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 checklist v0.2.0 #308

Open
3 of 4 tasks
ckadner opened this issue Feb 24, 2022 · 5 comments
Open
3 of 4 tasks

Release checklist v0.2.0 #308

ckadner opened this issue Feb 24, 2022 · 5 comments
Assignees

Comments

@ckadner
Copy link
Member

ckadner commented Feb 24, 2022

Outstanding work items before cutting the v0.2.0 release:

MLX v0.2.0 is intended to be a stable release for Kubeflow 1.5 before introducing new "breaking" changes (asset versioning, component registry, KFP IR transition, ...) -- similarly MLX v0.1.0 was for KFServing on Kubeflow 1.4

Kubeflow 1.5 is not ready just yet, pending kserve/knative for k8s 1.22

  • Upgrade MLX-API Python dependencies, upgrade to kfp-tekton v1.1.1 @ckadner
  • Create a new manifest patch to add the v0.2.0 version @Tomcli @yhwang
  • Test the v0.2.0 deployment on KIND and IKS K8s 1.21
  • ...
@Tomcli
Copy link
Member

Tomcli commented Mar 1, 2022

@ckadner I tested with pipelines and MLX works fine on k8s 1.21. We can cut the 0.2 branch and cherry pick new changes as we need to. This should let you start merging the new APIs for MLX

@Tomcli
Copy link
Member

Tomcli commented Mar 1, 2022

I cut a new branch here. Any bugs fixes and version change can go to here
https://github.com/machine-learning-exchange/mlx/tree/v0.2.0

@ckadner
Copy link
Member Author

ckadner commented Mar 1, 2022

Thank you @Tomcli

You checked off Create a new manifest patch to add the v0.2.0 version -- Did you have to make any changes or check it off because there are no required changes?

@Tomcli
Copy link
Member

Tomcli commented Mar 2, 2022

i added this pr for v0.2.0 branch, main branch should keep using the nightly tag
https://github.com/machine-learning-exchange/mlx/pull/309/files

@Tomcli
Copy link
Member

Tomcli commented Mar 2, 2022

@ckadner when you cut the release, you can cut it from the v0.2.0 branch so that we can keep track of the diff for any new cherry pick commits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants