Updates
- The team has identified a critical issue affecting pull request merges in user-owned repositories.
- A withdrawal proposal (#33) has been submitted to cancel the v5.0.0 upgrade proposal (#32):
- Along with this, you can also vote NO in the upgrade proposal #32 submitted earlier.
- The team has fixed the identified issue and is conducting thorough testing
- A new upgrade proposal will be submitted after testing is complete
Important Notes for Validators
The proposed upgrade will take place at block height 29,278,500
(approximately 2024-11-29 14:00:00 UTC
).
29,435,500
(approximately 2024-12-02 14:00:00 UTC
).
Recommendations
- Back up your data before attempting the upgrade
- Monitor the #mainnet-validators channel on Discord for real-time support during the upgrade process
- If you encounter issues, do not restart your node mid-upgrade unless absolutely necessary. Reach out to the community for support first
- Pay special attention to the store migration process during this upgrade
Background
The Gitopia v5.0.0 release represents a significant enhancement to our DAO functionality, introducing a more robust and integrated governance system. This upgrade will follow the standard governance process, requiring approval through an on-chain proposal.
Upon approval of the governance vote, validators will be required to update the Gitopia binary at the specified halt-height.
Proposed Release Contents
The primary focus of this release is a comprehensive redesign of Gitopia’s DAO system, introducing tighter integration with repository workflows. Key changes include:
-
New DAO Implementation
- Migration to Cosmos SDK’s group module for internal DAO representation
- Enhanced governance capabilities for repository management
- New proposal management and voting mechanisms
-
Repository Governance Integration
- Configurable governance requirements for key repository actions:
- Release creation
- Pull request merging
- Collaborator management
- Repository deletion
- Configurable governance requirements for key repository actions:
-
SDK Modifications
- Custom fork of cosmos-sdk v0.47.13
- Disabled purging of group proposals to maintain governance history
-
Store Migrations
- Migration of existing DAOs to new implementation
Testing
Testing is currently in progress, with particular focus on:
- Store migration process
- DAO governance workflows
- Repository workflows in DAO and User owned repositories
Potential Risk Factors
This upgrade involves several significant changes that validators and users should be aware of:
-
Store Migration Risks
- The upgrade includes state migrations for existing DAOs
- Potential for longer upgrade time due to migration process
- Validators should ensure sufficient disk space and resources
-
Breaking Changes
- New DAO implementation affects existing repository transactions
- Changes to how repository actions are governed
- Updates to transaction handling for DAO-controlled repositories
Coordination and Support
The upgrade process will be actively coordinated through:
- #mainnet-validators Discord channel
- Real-time support during the upgrade window
- Emergency response team on standby
Governance Votes
The following summarizes the voting options for this proposal:
- YES - You agree that Gitopia should be updated with this release
- NO - You disagree that Gitopia should be updated with this release
- NO WITH VETO - You believe this proposal is spam, infringes on minority interests, or violates governance rules
- ABSTAIN - You contribute to the quorum but decline to vote for or against the proposal
Emergency Procedures
In case of critical issues during the upgrade:
- DO NOT restart your node without consulting the validator community
- Monitor the #mainnet-validators channel for emergency instructions
- Be prepared to halt the network if instructed by core team
- Have rollback procedures ready if needed
Resources and Documentation
- Full documentation of the new DAO system will be available at Gitopia Docs
We encourage all stakeholders to:
- Review the proposed changes thoroughly
- Participate in the governance process
- Prepare for the upgrade well in advance
Please share any concerns or questions in the forum discussion below.