Gaia master should not be updated to Cosmos-SDK master

[tac0turtle]

Summary

Gaia represents the software used by the Cosmos Hub. Its master branch should not look at the master branch of the Cosmos-SDK as this is unstable software. The reason this is being done is when we moved Gaia out of the Cosmos-SDK we removed the cmd's from the Cosmos-SDK, so we used Gaia as part of the SDK testing suite. We have now brought the cmd's back to the SDK and do not have a need for Gaia to look at master.

Problem Definition

Gaia master branch is looking at the latest Cosmos-SDK master branch.

Proposal

Gaia is pinned to a release of the Cosmos-SDK (0.37.x), it's master branch gets minor updates and can be used on testnets for early-stage testing before being deployed to the hub.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[alexanderbez]

I approve of this. Very easy to do this. Have the latest 2.x.x release of Gaia now be main.

[tac0turtle]

will let this sit for a couple of days before I make the changes

[webmaster128]

When this is implemented (which makes perfect sense as far as I can see), where would a version of gaia be maintained that contains the latest updates to Cosmos SDK master? Would someone work on this at all? We'd need somthing like a gaia nightly to start testing stargate clients (cosmos/cosmjs#242).

Thank you!

[tac0turtle]

When this is implemented (which makes perfect sense as far as I can see), where would a version of gaia be maintained that contains the latest updates to Cosmos SDK master? Would someone work on this at all? We'd need somthing like a gaia nightly to start testing stargate clients (CosmWasm/cosmjs#242).

Thank you!

could simd & simcli be used from the sdk. WE would just need to add a make target for installing instead of building.

[webmaster128]

could simd & simcli be used from the sdk. WE would just need to add a make target for installing instead of building.

Yes, I think that would do the trick. Would it be possible to dockerize simd/simcli like https://hub.docker.com/r/tendermint/gaia (I can build and upload locally if needed)? It would need to run as a testing chain on dev machines and CIs without a Go build environment.

[tac0turtle]

Yes, I think that would do the trick. Would it be possible to dockerize simd/simcli like hub.docker.com/r/tendermint/gaia (I can build and upload locally if needed)? It would need to run as a testing chain on dev machines and CIs without a Go build environment.

yes, ill take care of that in the coming days.

[alessio]

I agree with this. This burden is becoming unbearable

[jgimeno]

This is music to my ears! I totally agree!

[tac0turtle]

default branch is now main and has been reverted to latest release. I will begin migrating things from master that need to be here