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

Scoping: migrate feature #33

Closed
1 task
kenwheeler opened this issue Jan 19, 2017 · 3 comments
Closed
1 task

Scoping: migrate feature #33

kenwheeler opened this issue Jan 19, 2017 · 3 comments
Assignees

Comments

@kenwheeler
Copy link

Lets use this ticket to discuss the scope of the migrate command

TODO:

  • Agreed upon high level scope points go here
@kenwheeler kenwheeler changed the title Scoping: migrate command Scoping: migrate feature Jan 19, 2017
@evenstensberg
Copy link
Member

migrate should transform from v1 to v2, that's it.

@DanielaValero
Copy link
Contributor

Hi, I'd say that in order to be able to split this into smaller tasks, would be good to have a more detailed plan of the implementation of this.

@pksjce: You've been doing some work here, and mentioned in our call that the ground work you've been setting is quite in place and would be ready to get some extra hands in.

Would you share with us here the code design ideas that you've got? Perhaps maybe starting from a high level point of view, and then we can get more into details?

@pksjce
Copy link

pksjce commented Jan 31, 2017

@okonet - We need to collate all thats done in #40 and #6. After that we can come up with some concrete tasks that can be easily split.

@okonet okonet closed this as completed Apr 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants