liftedinit / liftedinit/roadmap

Tendermint 0.34 to 0.37 upgrade

Open
#43 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

story tendermint
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Description: This story is related to #6. Tendermint 0.35 has been abandoned and is no longer supported. We need to first move to Tendermint 0.34 to be to upgrade to 0.37 which is the end target. This is necessary to increase our security and stability. This has already been researched as noted in #6.

Story ROI
Business Objective: By upgrading to Tendermint 0.37 we will be on the latest version and increasing network security and stability.

As an engineer, I want to upgrade from Tendermint 0.34 to 0.37 so that our network is more secure and stable.

  • Should run migration to upgrade network to Tendermint 0.37 in QA environment.
  • Should document procedure for production and obtain team approval, schedule prod upgrade.
  • Should run prod migration and upgrade from Tendermint 0.34 to 0.37.

Tasks:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked roadmap issue #6 and the existing research for the Tendermint 0.34-to-0.37 upgrade. Validate the migration in the QA environment, document the approved production procedure and schedule, then complete the production upgrade; done means all three issue checklist items are addressed.

Written by the indexing model from the issue text.

Assessment

Domain
blockchain, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.