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

v7.0.0 tracking issue #1864

Closed
24 of 27 tasks
Tracked by #455
crodriguezvega opened this issue Aug 2, 2022 · 5 comments
Closed
24 of 27 tasks
Tracked by #455

v7.0.0 tracking issue #1864

crodriguezvega opened this issue Aug 2, 2022 · 5 comments
Labels

Comments

@crodriguezvega
Copy link
Contributor

crodriguezvega commented Aug 2, 2022

Main additions to this release are:

02-client refactor

This refactor will make the development of light clients easier. The ibc-go implementation will finally align with the spec and light clients will be required to set their own client and consensus states. This will allow more flexibility for light clients to manage their own internal storage and do batch updates. See ADR 006 for more information.

Follow the progress with the beta and RC milestones or in the project board.

Upgrade SDK v0.47.x

Follow the progress with the milestone.

Add authz support to 20-transfer

See #2431 for more details.

Milestones

v7.0.0 milestone

IBC spec compatibility

v1.0

QA

Backwards compatibility

  • Compatibility tests pass.
  • Upgrade test pass.
  • Interchain Accounts inter-tx tests pass.

Other testing

Migration

v6 to v7 migration docs

Checklist

  • Bump go package version.
  • Change all imports starting with github.com/cosmos/ibc-go/v6 to github.com/cosmos/ibc-go/v7.
  • Branch off main to create release branch in the form of release/v7.0.x and add branch protection rules.
  • Add branch protection rules to new release branch.
  • Add backport task to mergify.yml.
  • Set up compatibility tests for release/v7.0.x.
  • Upgrade ibc-go version in ibctest.
  • Check migration docs.
  • Check Swagger is up-to-date.

Post-release checklist


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged/assigned
@crodriguezvega crodriguezvega pinned this issue Aug 12, 2022
@crodriguezvega crodriguezvega changed the title v6.0.0 tracking issue v7.0.0 tracking issue Sep 6, 2022
@crodriguezvega crodriguezvega unpinned this issue Sep 12, 2022
@crodriguezvega crodriguezvega pinned this issue Oct 1, 2022
@crodriguezvega crodriguezvega moved this to Todo in ibc-go Nov 1, 2022
@crodriguezvega crodriguezvega moved this from Todo to In progress in ibc-go Dec 13, 2022
@gjermundgaraba
Copy link
Contributor

gjermundgaraba commented Jan 28, 2023

Looking at the tracking it looks like this is getting pretty close. Are there any plans for a beta or rc release? We would like to start testing v7 on our 0.47-rc chain.

Edit: nevermind me... I missed the fact that a beta had been tagged, because I was just looking in the releases section. Sorry about that... Carry on!

@crodriguezvega
Copy link
Contributor Author

Edit: nevermind me... I missed the fact that a beta had been tagged, because I was just looking in the releases section. Sorry about that... Carry on!

Indeed, we tagged v7.0.0-beta2 last week and we will have the first RC probably next week at the latest.

@crodriguezvega
Copy link
Contributor Author

crodriguezvega commented Mar 7, 2023

Compatibility tests pass before v7.0.0-rc1.

Will run upgrade and interchain accounts test after tagging rc1.

@crodriguezvega
Copy link
Contributor Author

Before final release:

@crodriguezvega
Copy link
Contributor Author

Closed by v7.0.0

@github-project-automation github-project-automation bot moved this from In progress to Todo in ibc-go Mar 22, 2023
@crodriguezvega crodriguezvega unpinned this issue Mar 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

2 participants