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

Migrate the devfile v1 Tests to devfile v2 #3142

Closed
adisky opened this issue May 11, 2020 · 3 comments · Fixed by #3279
Closed

Migrate the devfile v1 Tests to devfile v2 #3142

adisky opened this issue May 11, 2020 · 3 comments · Fixed by #3279
Assignees
Labels
triage/needs-information Indicates an issue needs more information in order to work on it.
Projects

Comments

@adisky
Copy link
Contributor

adisky commented May 11, 2020

/kind test

Followup issue for PR #3216

@adisky adisky added this to For consideration in Sprint 184 via automation May 11, 2020
@girishramnani girishramnani moved this from For consideration to To do in Sprint 184 May 14, 2020
@prietyc123 prietyc123 added the triage/needs-information Indicates an issue needs more information in order to work on it. label May 18, 2020
@prietyc123
Copy link
Contributor

Thanks @adisky for sharing the doc [1] for devfile v2 implementation plan. AFAIU we are just adding a compatibility matrix of v2 for devfile support, I mean both v1 and v2 will be supported for devfile implementation and in later state v1 will be deprecated, right ?

However TBH I am clueless what test plan you are looking for it whereas we have the test for devfile in place. So can you please be more specific of what else test you are looking for.

[1] https://docs.google.com/document/d/11BVhP1gViu5C3IGYQpiulX1lUkSGOG8p-lOJq4I5mUs/edit#heading=h.bw3vmyuddut1

@prietyc123
Copy link
Contributor

I am not sure about keeping this issue in this sprint. As I have gone through the planned execution for V2 parser and it seems more challenging that it might take time, may be the whole sprint. So, keeping this issue in this sprint doesn't make sense to me.

Even I feel if we assign this task to the owner of the V2 parser this will be done parallely without consuming additional time that someone may take in getting the context. This will release some bandwidth for other tasks. So, I am unassigning myself.

/unassign @prietyc123

@prietyc123
Copy link
Contributor

I am not sure about keeping this issue in this sprint. As I have gone through the planned execution for V2 parser and it seems more challenging that it might take time, may be the whole sprint. So, keeping this issue in this sprint doesn't make sense to me.

Even I feel if we assign this task to the owner of the V2 parser this will be done parallely without consuming additional time that someone may take in getting the context. This will release some bandwidth for other tasks. So, I am unassigning myself.

ping @adisky

@adisky adisky changed the title Add Tests for devfile parser V2. Add Tests for devfile V2. Jun 1, 2020
@girishramnani girishramnani removed this from To do in Sprint 184 Jun 1, 2020
@girishramnani girishramnani added this to For consideration in Sprint 185 via automation Jun 1, 2020
@girishramnani girishramnani moved this from For consideration to To do in Sprint 185 Jun 1, 2020
@girishramnani girishramnani changed the title Add Tests for devfile V2. Migrate the devfile v1 Tests to devfile V2. Jun 1, 2020
@girishramnani girishramnani changed the title Migrate the devfile v1 Tests to devfile V2. Migrate the devfile v1 Tests to devfile v2. Jun 1, 2020
@girishramnani girishramnani changed the title Migrate the devfile v1 Tests to devfile v2. Migrate the devfile v1 Tests to devfile v2 Jun 4, 2020
Sprint 185 automation moved this from To do to Done Jun 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
No open projects
Sprint 185
  
Done
Development

Successfully merging a pull request may close this issue.

4 participants