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

release v0.24.0 #2756

Closed
4 of 7 tasks
ilgooz opened this issue Aug 18, 2022 · 7 comments
Closed
4 of 7 tasks

release v0.24.0 #2756

ilgooz opened this issue Aug 18, 2022 · 7 comments
Assignees

Comments

@ilgooz
Copy link
Member

ilgooz commented Aug 18, 2022

@aljo242
Copy link
Contributor

aljo242 commented Aug 18, 2022

Do we want to finish #2669 before release?

@aljo242
Copy link
Contributor

aljo242 commented Aug 18, 2022

#2693 migration guide required before release

@aljo242
Copy link
Contributor

aljo242 commented Aug 18, 2022

Working on #2679

@ilgooz
Copy link
Member Author

ilgooz commented Aug 18, 2022

Do we want to finish #2669 before release?

Not required for this release but yes if we can merge it by early next week.

@ilgooz
Copy link
Member Author

ilgooz commented Aug 18, 2022

Added link to those issues/prs in the first message.

@tbruyelle
Copy link
Contributor

tbruyelle commented Sep 2, 2022

Blocker for the cosmoscmd submodule : ignite/modules#40

Explanation: if we decide to move cosmoscmd to ignite/modules, it's because we don't want a scaffolded chain to depends on the whole CLI codebase. So if ignite/modules already depends on CLI, it won't work.

@ilgooz
Copy link
Member Author

ilgooz commented Sep 3, 2022

I think separation of cosmoscmd can be done in another release.

@aljo242 aljo242 closed this as completed Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants