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

v0.46.0 Release #11096

Closed
44 of 56 tasks
Tracked by #314
robert-zaremba opened this issue Feb 2, 2022 · 5 comments · Fixed by #12736
Closed
44 of 56 tasks
Tracked by #314

v0.46.0 Release #11096

robert-zaremba opened this issue Feb 2, 2022 · 5 comments · Fixed by #12736
Assignees

Comments

@robert-zaremba
Copy link
Collaborator

robert-zaremba commented Feb 2, 2022

Summary

Tracking issue for 0.46.0.

v0.46 Release team: @AmauryM @robert-zaremba @marbar3778

Before beta release

These are the pieces that need to be merged before we tag a beta.

nice to have

beta release

This phase is focused on v0.46 auditing. Once we move into this phase, we create a new branch release/v0.46.x. PRs are to be merged into master and backported to release/v0.46.x. Features, client-breaking changes and small API-breaking changes can still be merged back into the release branch if deemed necessary.

RC Blockers:

nice to haves:

rc release

Unless there's a strong requirement otherwise, this phase should be focused on bugfixes, final polishes and testnet/devnet testing. PRs are to be merged into master and backported to release/v0.46.x. Client-breaking changes and small API-breaking changes can still be merged back into the release branch if deemed necessary.

v0.46.0 release

  • Merge all Changelog entries from all rc releases into one v0.46.0 section
  • Merge and synthetize RELEASE_NOTES.md from all rc releases
  • Tag off v0.46.0 from the release/v0.46.x branch.
  • Update the STABLE_RELEASES.md document
  • Verify and update general docs: docs.cosmos.network documentation tracking #11898
  • Ensure docs.cosmos.network has a v0.46 branch
  • Create new Cosmovisor release
@amaury1093 amaury1093 changed the title 0.46 Release dependencies v0.46.0 Release dependencies Feb 2, 2022
@amaury1093 amaury1093 changed the title v0.46.0 Release dependencies v0.46.0 Release Feb 2, 2022
@amaury1093 amaury1093 changed the title v0.46.0 Release v0.46.0 Release dependencies Feb 2, 2022
@amaury1093 amaury1093 changed the title v0.46.0 Release dependencies v0.46.0 Release Feb 2, 2022
@faddat
Copy link
Contributor

faddat commented Feb 20, 2022

Hi all, it looks like Notional is going to invest heavily in SDK v46, because:

  • Better testnet features for easier development
  • libp2p & ipld in tendermint 35
  • NFTs
  • Work on governance, against the latest iteration

I'd like to tell you about how I am thinking about constructing stacks with SDK 46, and would love comment.

Right now, I've got testnets blocked by:

  • wasmd imports ibc so I am upgrading ibcv3 to support sdk 46

In fact, that might kind of be all. The way that I have been approaching developing on this version, fully aware that there may be issues from upstream, is to update the chain daily, and I've got testing set up with the new "testnet start" command (guys, this is gold)

I think we may be able to help solve a problem.

I think the sdk is flourishing
I think ibc-go is flourishing

I think they've lost touch with one another compatibility wise and that's inevitable.

I also think that cw will see really wide adoption, and I'd like to use it in a number of upcoming projects, so I'm going to get a thing going that will test:

  • wasmd
  • ibc-go
  • all of the modules in the sdk

and it occurs to me that the test platform I described there, also makes a very good template.

To build craft I used simapp as a reference very often and I got it to a place where I felt very good about its no-ibc stability.

I'm now trying to add CW (/x/wasm) to craft and that is getting tough.

Anyhow, I think that I'll iron out any issues pretty quickly and that we will soon have something that pulls all of these together.

Here are my earliest observations:

  • Simapp is cool, but isn't a template
  • Starport is cool, but doesn't really keep pace with the sdk (not a criticism, there's reason for this of course)
  • ibc-go is needed for meaningful testing
  • wasm shall be de rigeur -- whatever that means :P

Would the SDK team like a PR of:

  • an application template?
  • A system for testing the latest versions of all the things against one another?
  • none of the above?

It could also possibly live in its own repository.

Thanks very much

PS, I just thought of something that may make what I am describing clearer:

a template with

in a ci system that

  • monitors the different repositories
  • builds each time there's a change to the master branch
  • provides the community with integration information

PS:

This isn't really a feature request, and is certainly not a complaint. It is more or less what I figure I'll build and would love to get feedback on.

I know everyone is super-strapped for time and resources. The needs of our clients & communities have brought this to the front for us, and if we end up doing the various upgrades, we surely don't mind :).

@cyborgshead
Copy link

I hope state rollback will be merged soon, waiting for this feature for years
Sad to see this is nice to have in last releases for a far time

@faddat
Copy link
Contributor

faddat commented Mar 1, 2022

osmosis-labs/osmosis#705

I'm pretty sure that the capabilities needed for interfluid staking start with something like ica+46+cw

@amaury1093
Copy link
Contributor

Just tagged v0.46.0-beta1.

@tac0turtle
Copy link
Member

Boom

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

Successfully merging a pull request may close this issue.

6 participants