8000 Soft upgrades and version numbers [Tracking Issue] · Issue #122 · cometbft/cometbft · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Soft upgrades and version numbers [Tracking Issue] #122
New issue
New issue
Open
Open
Soft upgrades and version numbers [Tracking Issue]#122
Labels
P:tech-debtPriority: Technical debt that needs to be paid off to enable us to move faster, reliablycommunity-callTo be discussed in an upcoming community callspecSpecification-relatedtrackingA complex issue broken down into sub-problems
@adizere

Description

@adizere
adizere
opened on Jan 16, 2023

We should increase range of upgrades that can be conducted as a "soft" upgrade rather than a "hard" upgrade (requiring a blockchain restart). The related RFC, which is now open at tendermint/spec#222, has more detail on the proposed solution.

Combined with upgrade tooling (tendermint/tendermint#5595), it will be much easier for users to upgrade Tendermint Core.

Version numbers will play a key role in this. Here are a few outstanding issues that deal with versioning across Tendermint Core:

Originally: tendermint/tendermint#5680

Metadata

Metadata

Assignees

No one assigned

    Labels

    P:tech-debtPriority: Technical debt that needs to be paid off to enable us to move faster, reliablycommunity-callTo be discussed in an upcoming community callspecSpecification-relatedtrackingA complex issue broken down into sub-problems

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions
      0