-
Notifications
You must be signed in to change notification settings - Fork 780
Closed
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestreleasePull requests that facilitate cutting a releasePull requests that facilitate cutting a release
Milestone
Description
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?
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).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestreleasePull requests that facilitate cutting a releasePull requests that facilitate cutting a release