Skip to content

Clarify the breaking nature of v1 upgrade #3416

@adizere

Description

@adizere

Feature Request

Summary

Suppose a team is upgrading from v0.38 to v1.

What do they need to know when it comes to the breaking nature of this upgrade? Do validators need to coordinate? Do they need to migrate their config.toml? Do the answers depend?

Ref: trufnetwork/kwil-db#760

Proposal

Let's provide more guidelines regarding upgrading to v1. Consider:

  • We do a very good job of detailed guidelines in https://github.com/cometbft/cometbft/blob/main/UPGRADING.md. Let's make sure this doc answers the questions in the KwillDB PR linked above.
  • Let's make sure upgrading guidelines are discoverable, either/ both from docs.cometbft.com as well as from other places (main readme.md, a blog post, X thread).

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationenhancementNew feature or requestreleasePull requests that facilitate cutting a release

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions