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

[Epic] v8 tracking issue #1141

Closed
19 of 28 tasks
ValarDragon opened this issue Mar 24, 2022 · 8 comments
Closed
19 of 28 tasks

[Epic] v8 tracking issue #1141

ValarDragon opened this issue Mar 24, 2022 · 8 comments

Comments

@ValarDragon
Copy link
Member

ValarDragon commented Mar 24, 2022

@ValarDragon
Copy link
Member Author

It feels like to me like we're hitting scope creep on v8 / when that'd go into an on-chain proposal. I propose making a new issue for planning a v9 release, and moving some v8 items into there.

The goal would be to target a v8 proposal going on-chain April 8th or April 11th.

Items that I think we should move to v9:

  • Token Factory
  • TWAP

@faddat
Copy link
Member

faddat commented Apr 16, 2022

Kicked off a branch:

https://github.com/osmosis-labs/osmosis/tree/v8.x

@Vinitowinit
Copy link

Hey @ValarDragon, Hope your doing well mate :) Curious if this Epic will be ready by end of this week. I see @faddat has kicked off a branch which is exciting. I also see the GAMM Work still needs sometime to properly address as well!

@Vinitowinit
Copy link

Hey @ValarDragon following up here again if possible to see if there is any update. Thank you so much and enjoy the remainder of your week

@ValarDragon
Copy link
Member Author

ValarDragon commented Apr 27, 2022

Hey, this will definitely not be ready by end of week unfortunately. Would appreciate any help in documenting & improving any of the relevant changes!

@Vinitowinit
Copy link

Hi yes, of course, I think I can help with documentation if need be. Improving the relevant changes I am unaware of where to help. For instance, stable swap is clearly out of my scope/capability to help :/

@Vinitowinit
Copy link

Looking at the additional work, it looks like this v8 release will actually take 3-4 more weeks until pushed. Let me know how I can help your team push it out further from a documentation stance. Thanks

@mattverse
Copy link
Member

Closing this issue in replacement of V10

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

4 participants