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

V20: Scoping Issue #5864

Closed
18 of 28 tasks
p0mvn opened this issue Jul 18, 2023 · 3 comments
Closed
18 of 28 tasks

V20: Scoping Issue #5864

p0mvn opened this issue Jul 18, 2023 · 3 comments

Comments

@p0mvn
Copy link
Member

p0mvn commented Jul 18, 2023

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

Preview Give feedback
No tasks being tracked yet.

In-Scope

The scope that is currently planned for v20

Tasks

Preview Give feedback
  1. C:x/concentrated-liquidity T:triage
    czarcas7ic
  2. 39 of 39
    F: volume-splitting T:task ⚙️
    AlpinYukseloglu czarcas7ic
    p0mvn
  3. C:CLI C:x/epochs C:x/lockup V:state/breaking
    ValarDragon mattverse
  4. C:x/superfluid T:bug 🐛
  5. F: concentrated-liquidity
    sunnya97
  6. czarcas7ic mattverse
  7. nicolaslara
  8. A:backport/v20.x C:CLI C:docs V:state/breaking
    mattverse p0mvn
  9. A:no-changelog C:docs V:state/compatible/no_backport
    czarcas7ic
  10. C:x/gamm V:state/breaking
  11. p0mvn

Non-Blocking

Efforts below will be added to the scope if they are complete prior to the current scope being complete.

Tasks

Preview Give feedback
  1. 16 of 30
    ClickUp Test F: concentrated-liquidity T:epic ⛰
    AlpinYukseloglu p0mvn
  2. hieuvubk

Not Pursuing

Efforts below are not being pursuit this release.

Tasks

Preview Give feedback
  1. czarcas7ic
  2. T:triage

Concurrent To v20

Efforts being pursued concurrently but independently of v20 release

Tasks

Preview Give feedback
  1. czarcas7ic
  2. nicolaslara
  3. mattverse niccoloraspa
  4. 10 of 15
    F: Crosschain Swaps T:epic ⛰
    czarcas7ic nicolaslara

Deprioritized

Issues below were in-scope at some point but were moved out due to a lack of clarity on product priorities.

Tasks

Preview Give feedback
  1. C:docs C:x/superfluid Stale V:state/breaking
  2. iboss-ptk mattverse
  3. C:x/lockup Stale
  4. F: CosmWasmPool Help wanted
@faddat
Copy link
Member

faddat commented Aug 3, 2023

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:

@p0mvn
Copy link
Member Author

p0mvn commented Aug 3, 2023

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.
Only after that, we will dedicate capacity on writing up a design document with plans for the unfork, including how it will relate to all the dependencies.

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.
Additionally, we now have a requirement to create a document outlining all known context and development plan before starting on the actual implementation of a large feature. The reason why this is especially important for unfork is because we will need to figure out how to deal with some of the custom functionality on our fork. For SDK unfork, Adam, Nicolas and I will be working on it after v17 is out. Once it's ready, we are hoping to collaborate on the implementation with anyone interested.
That being said, if you can drive forward some of the dependency upgrades in the meantime such as wasmd etc, so that they are compatible with sdk 0.50, that would be excellent.

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

@p0mvn
Copy link
Member Author

p0mvn commented Aug 14, 2023

Linking context from #ext-cosmos-tech: https://osmosis-network.slack.com/archives/C047X1T6ERK/p1692022598220689

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

No branches or pull requests

3 participants