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.

Sign up for GitHub

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

Jump to bottom

Add explicit data transfer step (plain cp if necessary) #33

Open
jfomhover opened this issue Aug 19, 2022 · 2 comments
Open

Add explicit data transfer step (plain cp if necessary) #33

jfomhover opened this issue Aug 19, 2022 · 2 comments
Assignees
@garg-amit
Labels
hold

Comments

@jfomhover
Copy link
Contributor

New branch doesn't have data transfer explicitely because it's not support in dpv2.

But we could introduce a "fake" DT step just doing cp input/* output/ so that we put a placeholder for a future DT step.
@jfomhover jfomhover added the release-Aug31 This issue is planned for the upcoming release on Aug 31. label Aug 19, 2022
@garg-amit garg-amit self-assigned this Aug 31, 2022
@thomasp-ms
Copy link
Contributor

Sorry @garg-amit , I realized the issue I created earlier today. Is a duplicate of this one. I'm removing the duplicate, and tagging this one for iteration 2.

@thomasp-ms thomasp-ms added iteration-02 and removed release-Aug31 This issue is planned for the upcoming release on Aug 31. labels Sep 1, 2022
@thomasp-ms thomasp-ms mentioned this issue Sep 1, 2022
Closed
@thomasp-ms
Copy link
Contributor

This will be done in iteration, removing from this milestone

@garg-amit garg-amit added the hold label Sep 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@garg-amit garg-amit

Labels
hold
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jfomhover @thomasp-ms @garg-amit