# Formalizing Testing Proceses for Upgrades
**URL:** https://forum.regen.network/t/formalizing-testing-proceses-for-upgrades/406
**Category:** Validators
**Created:** [June 17, 2025, 4:55am UTC](https://forum.regen.network/t/formalizing-testing-proceses-for-upgrades/406 "2025-06-17T04:55:38Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Jeancarlo](https://forum.regen.network/u/Jeancarlo)
#### Post date: [June 17, 2025, 4:55am UTC](https://forum.regen.network/t/formalizing-testing-proceses-for-upgrades/406/1 "2025-06-17T04:55:38Z")
To improve coordination and communication, we can discuss here what the ideal channels are for future upgrades. The objective is to define a process by which we can collaborate and communicate changes in easy-to-follow steps to members who wish to participate in current and future upgrades, including development work, testnet participation, local tests, and other relevant activities.
---
### Author:  [@Jeancarlo](https://forum.regen.network/u/Jeancarlo)
#### Post date: [June 17, 2025, 5:01am UTC](https://forum.regen.network/t/formalizing-testing-proceses-for-upgrades/406/2 "2025-06-17T05:01:19Z")
Currently, the fastest approach will be to add the new documentation directly to the Regen ledger itself, in a directory where people can use it as a set of steps to run a validator on the testnet. That still raises the question of how to reach out to other collaborators if you get stuck. Maybe GitHub Discussions is a good tool? Anyhow, these are just some Ideas. Feel free to suggest and discuss what you believe will make it easier for you.