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.

Sign up for GitHub

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

Jump to bottom

create a guideline for future ICS upgrades #1330

Open
Tracked by #1246
MSalopek opened this issue Sep 25, 2023 · 0 comments
Open
Tracked by #1246

create a guideline for future ICS upgrades #1330

MSalopek opened this issue Sep 25, 2023 · 0 comments
Assignees
@MSalopek
Labels
scope: docs Improvements or additions to documentation type: tech-debt Slows down development in the long run

Comments

@MSalopek
Copy link
Contributor

MSalopek commented Sep 25, 2023 •
edited
Loading

In order to facilitate quick upgrade schedule following cosmos-sdk and ibc-go upgrades we should aim to create a comprehensive guideline about upgrading ICS modules.

The guidline should contain (at minimum) the following steps:

  1. learn the the differences between cosmos-sdk/ibc-go versions and create an upgrade plan (a.k.a "spike")
  2. create an ADR outlining the upgrade plan for impacted areas:
  • library code (/x/ccv)
  • app wiring (/app, cmd)
  • internal testing tools (unit, integration, diff, e2e)
  • CI/CD pipelines
  1. best practices when performing the upgrades
  2. common issues and ways to resolve them

The goal of the guideline and ADRs should be to allow for faster upgrade schedules, better integration with dependencies and knowledge sharing.
@MSalopek MSalopek mentioned this issue Sep 25, 2023
Closed
@MSalopek MSalopek changed the title create a guideline for future ICS upgrade create a guideline for future ICS upgrades Sep 25, 2023
@MSalopek MSalopek added the S: KTLO Keeping the lights on: Keeping the current product operational (bugs, troubleshooting, deps updates) label Sep 25, 2023
@github-project-automation github-project-automation bot moved this to 🩹 F1: Triage in Cosmos Hub Sep 25, 2023
@MSalopek MSalopek moved this from 🩹 F1: Triage to 📥 F2: Todo in Cosmos Hub Sep 25, 2023
@MSalopek MSalopek added product type: tech-debt Slows down development in the long run labels Sep 25, 2023
@mpoke mpoke added scope: docs Improvements or additions to documentation and removed product labels Mar 22, 2024
@mpoke mpoke removed the S: KTLO Keeping the lights on: Keeping the current product operational (bugs, troubleshooting, deps updates) label Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MSalopek MSalopek

Labels
scope: docs Improvements or additions to documentation type: tech-debt Slows down development in the long run
Projects
Cosmos Hub
Status: 📥 F2: Todo
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mpoke @MSalopek @bermuell