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

ADR 002: importing multiple ibc-go versions #683

Merged
merged 6 commits into from
Jan 7, 2022

Conversation

colin-axner
Copy link
Contributor

@colin-axner colin-axner commented Jan 5, 2022

Description

Covers the thought process for deciding not to support importing multiple ibc-go versions

content comes from previous comments from myself and @damiannolan

closes: #632


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against correct branch (see CONTRIBUTING.md)
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Code follows the module structure standards.
  • Wrote unit and integration tests
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/)
  • Added relevant godoc comments.
  • Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
  • Re-reviewed Files changed in the Github PR explorer
  • Review Codecov Report in the comment section below once CI passes

@colin-axner colin-axner changed the title ADR 2: importing multiple ibc-go versions ADR 002: importing multiple ibc-go versions Jan 5, 2022
Copy link
Contributor

@crodriguezvega crodriguezvega left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice explanation! I left my usual nitpicking comments... 🔎 Just two things that maybe should change in the whole document:

  • I think Go (with uppercase) is the official name, so maybe we should be consistent.
  • Instead of just saying SDK, should we always say Cosmos SDK? To be more specific, just in case.

docs/architecture/adr-002-go-module-versioning.md Outdated Show resolved Hide resolved
docs/architecture/adr-002-go-module-versioning.md Outdated Show resolved Hide resolved
docs/architecture/adr-002-go-module-versioning.md Outdated Show resolved Hide resolved
docs/architecture/adr-002-go-module-versioning.md Outdated Show resolved Hide resolved
docs/architecture/adr-002-go-module-versioning.md Outdated Show resolved Hide resolved
docs/architecture/adr-002-go-module-versioning.md Outdated Show resolved Hide resolved
docs/architecture/adr-002-go-module-versioning.md Outdated Show resolved Hide resolved
docs/architecture/adr-002-go-module-versioning.md Outdated Show resolved Hide resolved
docs/architecture/adr-002-go-module-versioning.md Outdated Show resolved Hide resolved
docs/architecture/adr-002-go-module-versioning.md Outdated Show resolved Hide resolved
Copy link
Member

@damiannolan damiannolan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ack. Agree with suggestions from @crodriguezvega. Nice work!

@colin-axner colin-axner marked this pull request as ready for review January 7, 2022 10:14
@colin-axner colin-axner merged commit 3ff0927 into main Jan 7, 2022
@colin-axner colin-axner deleted the colin/632-adr-ibc-go-major-versions branch January 7, 2022 10:21
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

Successfully merging this pull request may close these issues.

Add ADR explaining reasoning for not allowing simulatenous imports of multiple ibc-go versions
4 participants