You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 2, 2021. It is now read-only.
With MLMD changes complete, and all lineage components in kubeflow/frontend. There are some other components that would make sense to migrate:
ArtifactDetails.tsx
ExecutionDetails.tsx
ExecutionList.tsx
@Bobgy Would there be a way to make sure all future changes are propagated similarly, for the time being. I understand that creating shared versions of these components makes sense in the longer term, but I do not have the cycles to carry forward that change currently.
Current Plan
Manually review the diffs and update the files in this repo, so all the new Lineage Relevant updates are present here as well
I think there's no easier way other than creating shared components.
I can see if I can put these into KFP 1.0 plan if you don't have cycles, but I don't expect any changes in those components for the foreseeable future. Maybe it's not very urgent.
One question what does all the new Lineage Relevant updates mean?
About
With MLMD changes complete, and all lineage components in kubeflow/frontend. There are some other components that would make sense to migrate:
@Bobgy Would there be a way to make sure all future changes are propagated similarly, for the time being. I understand that creating shared versions of these components makes sense in the longer term, but I do not have the cycles to carry forward that change currently.
Current Plan
Manually review the diffs and update the files in this repo, so all the new Lineage Relevant updates are present here as well
Meta
/area metadata
/area front-end
/priority p1
/assign @avdaredevil
/cc @kwasi
The text was updated successfully, but these errors were encountered: