mukan-ibc/.github/ISSUE_TEMPLATE/release-tracker.md

name	about
Release tracker	Create an issue to track release progress

Milestones

IBC spec compatibility

QA

Backwards compatibility

• Compatibility tests pass for the release branch.
• Upgrade tests pass.
• Manual test with ledger signing.

Other testing

Migration

Checklist

• Bump go package version.
• Change all imports starting with github.com/cosmos/ibc-go/v{x} to github.com/cosmos/ibc-go/v{x+1}.
• Branch off main 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 interchaintest.
• 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:
  • Update permalinks with links of the released tag.
  • 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
• Ensure annotations on tests are correct as per the compatibility test tool:
  • 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