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 v8.1.0 #5649

Closed
13 of 26 tasks
crodriguezvega opened this issue Jan 18, 2024 · 3 comments
Closed
13 of 26 tasks

Release v8.1.0 #5649

crodriguezvega opened this issue Jan 18, 2024 · 3 comments
Assignees
Labels
type: release Issues related to tagging a release

Comments

@crodriguezvega
Copy link
Contributor

crodriguezvega commented Jan 18, 2024

This release main additions are:

Channel upgradability

Implementation of the channel upgrades spec. See alpha, beta and RC milestones for more details.

Unordered ICA channels

New ICA channels will support unordered ordering, and with channel upgradability it will be possible to upgrade existing ICA ordered channels to change the ordering to unordered. See this issue for more information.

For other improvements and fixes in this release, please check out the release/v8.1.x changelog.

Milestones

v8.1.0 milestone

IBC spec compatibility

v1.0

QA

Backwards compatibility

Other testing

Migration

Checklist

  • Branch off release/v8.0.x to create release branch in the form of release/vx.y.z and add branch protection rules.
  • Add branch protection rules to new release branch.
  • Add backport task to mergify.yml
  • Upgrade ibc-go version in ibctest.
  • Check Swagger is up-to-date.

Post-release checklist

  • Update CHANGELOG.md
  • Update the table of supported release lines (and End of Life dates) in RELEASES.md:
    • Add the new release line.
    • Remove any release lines that might have become discontinued.
  • Update version matrix in RELEASES.md:
    • Add the new release.
    • Remove any tags that might not be recommended anymore.
  • Update the list of supported release lines in README.md, if necessary.
  • Update docs site:
    • If the release is occurring on the main branch, on the latest version, then run npm run docusaurus docs:version vX.Y.Z in the docs/ directory. (where X.Y.Z is the new version number)
    • If the release is occurring on an older release branch, then make a PR to the main branch called docs: new release vX.Y.Z doing the following:
      • Update the content of the docs found in docs/versioned_docs/version-vx.y.z if needed. (where x.y.z is the previous version number)
      • Update the version number of the older release branch by changing the version number of the older release branch in:
        • In docs/versions.json.
        • Rename docs/versioned_sidebars/version-vx.y.z-sidebars.json
        • Rename docs/versioned_docs/version-vx.y.z
  • Update the compatibility test matrices:
    • Add the new release.
    • Remove any tags that might not be recommended anymore.
  • Update the manual e2e simd test workflow:
    • Remove any tags that might not be recommended anymore.
  • After changes to docs site are deployed, check ibc.cosmos.network is updated.
  • Open issue in SDK tutorials repo to update tutorials to the released version of ibc-go.

For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged/assigned
@crodriguezvega crodriguezvega added the type: release Issues related to tagging a release label Jan 18, 2024
@crodriguezvega crodriguezvega self-assigned this Jan 18, 2024
@crodriguezvega crodriguezvega moved this to Todo in ibc-go Jan 18, 2024
@crodriguezvega crodriguezvega pinned this issue Jan 18, 2024
@crodriguezvega
Copy link
Contributor Author

Green compatibility and upgrade tests at 95b89bb before final release.

@crodriguezvega
Copy link
Contributor Author

Release is out.

@crodriguezvega
Copy link
Contributor Author

Closed by #5780.

@github-project-automation github-project-automation bot moved this from In progress to Done in ibc-go Feb 1, 2024
@crodriguezvega crodriguezvega unpinned this issue Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: release Issues related to tagging a release
Projects
Archived in project
Development

No branches or pull requests

1 participant