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

Support versions for data science pipelines #82

Open
accorvin opened this issue Jul 25, 2023 · 4 comments
Open

Support versions for data science pipelines #82

accorvin opened this issue Jul 25, 2023 · 4 comments
Labels
tracker Non-completable ticket; used for tracking work at a high level

Comments

@accorvin
Copy link
Member

accorvin commented Jul 25, 2023

This is a top level "tracker of trackers" for supporting versions for pipelines. We want to support versions in the same way that they are supported in Kubeflow Pipelines.

Requirements

Users should be able to:

  • Add a new pipeline version
  • Access all versions for a pipeline
  • Do runs for any version including previous versions

Red Hat Internal Additional requirements information can be found here

Individual Efforts

@accorvin
Copy link
Member Author

FYI @HumairAK @andrewballantyne I created this to be the higher level tracker capturing delivery of this feature. I'm still learning the ropes for how we want to track stuff like this in GitHub so LMK if you think I should have created this differently.

@HumairAK
Copy link

HumairAK commented Jul 25, 2023

thanks @accorvin , dashboard has their own issues they probably have created to track the actionable work within their repo, is that something we want to link here?

@andrewballantyne andrewballantyne added the tracker Non-completable ticket; used for tracking work at a high level label Jul 25, 2023
@andrewballantyne
Copy link
Member

andrewballantyne commented Jul 25, 2023

Rule of thumb is:

  • This repo has a tracker "of trackers"
  • Each other repo has a tracker
  • Each of those trackers have stories

Top level, "tracker of trackers" is used to describe requirements and is something for PM to manage (ideally). They call out "individual efforts" (example: #41)

Let me know if you want me to update the ticket @accorvin -- I'm getting the proper stuff logged in Dashboard if we don't already 🤔

EDIT:

@accorvin
Copy link
Member Author

@andrewballantyne my intent when creating this issue was that this would be that "tracker of trackers" you referenced. I'll add some of the necessary boilerplate for that now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tracker Non-completable ticket; used for tracking work at a high level
Projects
Status: No status
Development

No branches or pull requests

3 participants