semver & git inspired upgrade flow

[orishim]

Rather than having every change to the DAO happen through global "improvement proposals", we could have a more open process where anyone can push modifications to individual branches which ripple up to a dev branch that can only be merged to main through a proposal.

We could also use semantic versioning to track updates to the DAO as releases (e.g. dorg-2.1.0).

[asgeir-s]

I like the notion of keeping it as that with a dev "environment" deployed on a testnet.

In this case, we will have a nice record of all the changes to the DAO over time.

Then deploying a change could go like this.

1. Add any changes (via PRs to dev).
   All changes must be set up with a script for creating deployment transactions.

Also, changes do not imply that we need to add new code from our side; it could be just to equip a module created by somebody else.

5. Create a PR to main.
6. This could trigger a command to create a proposal including the needed transactions (to whatever governance module we use).

[orishim]

Later on Radicle could be useful for linking repo updates & devops with on-chain governance, and Polywrap for keeping all on and off-chain components atomically synced.