-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Comments
Hi all, it looks like Notional is going to invest heavily in SDK v46, because:
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:
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 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:
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:
Would the SDK team like a PR of:
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
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 :). |
I hope state rollback will be merged soon, waiting for this feature for years |
I'm pretty sure that the capabilities needed for interfluid staking start with something like ica+46+cw |
Just tagged |
Boom |
Summary
Tracking issue for 0.46.0.
v0.46 Release team: @AmauryM @robert-zaremba @marbar3778
Before
beta
releaseThese are the pieces that need to be merged before we tag a
beta
.time.Now()
non-determinism for v0.46 #11115nice to have
beta
releaseThis 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.
v1
Module Readiness Checklist #11086release/v0.46.x
branch tomain
@marbar3778RC Blockers:
legacy.Cdc
for all modules #11643nice to haves:
rc
releaseUnless 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.
UPGRADING.md
document #11587 UpdateUPGRADING.md
v0.46.0 release
docs.cosmos.network
documentation tracking #11898The text was updated successfully, but these errors were encountered: