Summary

We need a clear release process for the monorepo, covering branching strategy, tagging convention, release cycles for our different environments, compatibility testing between releases and how we deal with artifacts.

Having such a process fully described allows us to create consistent releases for the future across all environments and components.

Acceptance Criteria

1. A detailed RELEASE.md documenting the full process
2. A definition for branching and tagging strategies
3. Release lifecycles for development, devnet, testnet and mainnet
4. Defined artifict publishing targets. What do we release? Where? And how?
5. Testing and compatibility standards