-
Notifications
You must be signed in to change notification settings - Fork 608
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
V20: Scoping Issue #5864
Comments
I made a branch for v18, it started with the lint for tests pr because having that in makes the upgrade easier / safer: Actually, as long as this is reasonable to you, I realized today that it's probably possible to make a good deal of progress even in parallel with 17, so I created a target branch and I'm going to make pull requests towards that. I'm currently working on the first PR which basically just makes sure that everything can tidy. In other upgrades that I've done, this PR tends to be really large because it's very challenging to do an upgrade of part of the code. Dependencies that need upgrading:
|
Cross-posting from Slack: Hi Jacob. Thanks for the context. This is my first day back from vacation so I don't have the most up-to-date context on the plans for the unfork. Will share my latest state below and get back with updates once I have them. The current plan is to focus on releasing v17 with immediate concentrated liquidity fixes and improvements. As part of concentrated liquidity learnings, we would like to avoid using feature branches due to branch synching overhead. So if you are able to start some smaller incremental work, please do it to main as opposed to long-lasting feature branches. AFAIR, the only reason we use our custom wasmd is because we have some custom SDK fork APIs that prevent us from using the upstream. Will need to confirm this. Ideally, we should stop using Osmosis fork for wasmd as well after unforking SDK |
Linking context from #ext-cosmos-tech: https://osmosis-network.slack.com/archives/C047X1T6ERK/p1692022598220689 |
Background
Tentative plan for the v20 scope. Each effort is to have a design document created. Upon reviewing and accepting the design, the final decision about v20 inclusion will be made.
Need Decision
Issues that were requested and need scope decisions
Tasks
In-Scope
The scope that is currently planned for v20
Tasks
Non-Blocking
Efforts below will be added to the scope if they are complete prior to the current scope being complete.
Tasks
Not Pursuing
Efforts below are not being pursuit this release.
Tasks
Concurrent To v20
Efforts being pursued concurrently but independently of v20 release
Tasks
Deprioritized
Issues below were in-scope at some point but were moved out due to a lack of clarity on product priorities.
Tasks
AfterCosmWasmPoolCreated
hook to create an internal gauge #6122The text was updated successfully, but these errors were encountered: