Soft upgrades and version numbers [Tracking Issue] #5680
Labels
C:spec
Component: specification
stale
for use by stalebot
T:design
Type: Design work is needed
T:tracking
Tracking issue for other issues
Projects
Milestone
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 (#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:
The text was updated successfully, but these errors were encountered: