-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Governance] Upgrade playbook and downstream investigation #625
Milestone
Comments
33 tasks
14 tasks
okdas
added a commit
that referenced
this issue
Aug 19, 2024
## Summary Follow-up PR to #702 to document protocol upgrades procedure. ## Issue - #702 - #625 ## Type of change Select one or more: - [ ] New feature, functionality or library - [ ] Bug fix - [ ] Code health or cleanup - [x] Documentation - [ ] Other (specify) ## Testing **Documentation changes** (only if making doc changes) - [ ] `make docusaurus_start`; only needed if you make doc changes **Local Testing** (only if making code changes) - [ ] **Unit Tests**: `make go_develop_and_test` - [ ] **LocalNet E2E Tests**: `make test_e2e` - See [quickstart guide](https://dev.poktroll.com/developer_guide/quickstart) for instructions **PR Testing** (only if making code changes) - [ ] **DevNet E2E Tests**: Add the `devnet-test-e2e` label to the PR. - **THIS IS VERY EXPENSIVE**, so only do it after all the reviews are complete. - Optionally run `make trigger_ci` if you want to re-trigger tests without any code changes - If tests fail, try re-running failed tests only using the GitHub UI as shown [here](https://github.com/pokt-network/poktroll/assets/1892194/607984e9-0615-4569-9452-4c730190c1d2) ## Sanity Checklist - [ ] I have tested my changes using the available tooling - [ ] I have commented my code - [ ] I have performed a self-review of my own code; both comments & source code - [ ] I create and reference any new tickets, if applicable - [ ] I have left TODOs throughout the codebase, if applicable <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Introduced a new category for "Upgrades" in the documentation to enhance navigation related to protocol upgrades. - Launched comprehensive documentation on the governance mechanisms for protocol parameter adjustments, detailing the DAO's role and examples of changes. - Added a structured page for past and upcoming protocol upgrades, improving user understanding of upgrade statuses. - Released a document outlining the protocol upgrade process, specifying steps and criteria for implementation. - **Documentation Updates** - Improved organization and clarity throughout the documentation by refining content structure and descriptions related to protocol upgrades. - Updated sidebar positions and references to ensure accurate navigation and resource linking for "Full Node" documentation. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Daniel Olshansky <[email protected]>
Both PRs are now merged. We're going to continue adding/chainging the process as we issue upgrades in Beta testnet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Objective
Write the playbook on how we'll handle on-chain governance updates.
Origin Document
Goals
Research and understand
the tools available in the Cosmos SDK for governance upgrades (i.e.x/upgrade
)Identify missing gaps
or differences between how we'll handle governance upgradesCollaborate with
the team at Informal Systems (CometBFT) or Binary Builders (Cosmos SDK) if need beDeliverables
Non-goals / Non-deliverables
General deliverables
Creator: @Olshansk
Co-Owners: @okdas
The text was updated successfully, but these errors were encountered: