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 to latest SDK develop #1433

Closed
1 task
faboweb opened this issue Oct 8, 2018 · 3 comments · Fixed by #1450
Closed
1 task

Migrate to latest SDK develop #1433

faboweb opened this issue Oct 8, 2018 · 3 comments · Fixed by #1450
Assignees

Comments

@faboweb
Copy link
Collaborator

faboweb commented Oct 8, 2018

In order to start on governance we should migrate to the latest SDK code.

Concerns:

  • we will probably not be able to connect to gaia-8001 after
@faboweb
Copy link
Collaborator Author

faboweb commented Oct 8, 2018

Maybe create a hotfixes branch for bugs on the old network.

@NodeGuy
Copy link
Contributor

NodeGuy commented Oct 8, 2018

Hmm, I wonder if we can do better here. Possibilities:

  • monorepo with SDK & Voyager
  • coordinated release cadence:
    1. SDK release (0 weeks)
    2. New testnet is launched from SDK release (2 weeks)
    3. Voyager publishes release that works with new testnet (4 weeks)
    4. Repeat.

@fedekunze fedekunze changed the title Migrate to latest SDK develope Migrate to latest SDK develop Oct 8, 2018
@jbibla
Copy link
Collaborator

jbibla commented Oct 9, 2018

Maybe create a hotfixes branch for bugs on the old network.

perhaps we should try a feature branch for new SDK + governance. we can merge into develop and release when the testnet is up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants