-
Notifications
You must be signed in to change notification settings - Fork 65
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
Clarify V2 to V3 migration guide #210
Comments
Also why are we using I'm now looking at the migration session on The Things Conference (https://app.hopin.com/events/the-things-conference-2021/stages/a901d5a9-1f8b-4532-a5a5-d0d486c9d388) and that looks much easier that way. |
I think @neoaggelos first needs to update the documentation if needed (for example using |
cc @ymgupta |
OK, @neoaggelos @ymgupta please request @nejraselimovic for review. |
There is #130, which has been open for quite some time |
@neoaggelos you own #130 so please keep moving with that. Also it's not entirely addressing this issue, but it's a good start. |
@nejraselimovic @neoaggelos pls have a look at this issue |
I think this can be closed now as we have made a full reorganization and update of migration docs. |
Summary
Clarify V2 to V3 migration guide.
See https://www.thethingsnetwork.org/forum/t/ttn-v2-to-the-things-stack-v3-transition/43247/36
Why do we need this ?
Because apparently there are too many assumptions in the current documentation.
What is already there? What do you see now?
https://www.thethingsindustries.com/docs/getting-started/migrating/migrating-from-v2/
What is missing? What do you want to see?
ttnctl selfupdate
work or is itttnctl.exe selfupdate
? Those small thingsttnctl
for TTN with the V2 private network instructionsHow do you propose to document this?
Can you do this yourself and submit a Pull Request?
I'm off next week, please monkey test this and merge soon, people are already stuck.
The text was updated successfully, but these errors were encountered: