meta: Add RELEASE.md #3224
meta: Add RELEASE.md #3224
Conversation
| 5. **Day 14:** Community announcement and gradual provisioners upgrade. | ||
| 6. **Day 16:** Deploy `rusk-vX.Y.Z` to **Mainnet**. |
There was a problem hiding this comment.
Isn't "provisioner upgrade" the same of "deploy to mainnet"?
What's the difference?
There was a problem hiding this comment.
Isn't "provisioner upgrade" the same of "deploy to mainnet"?
What's the difference?
People already deploying the binary, but thinking about it it doesn't make a whole lot of sense since we'll specify an upgrade is active after a given block height into the future anyway if it's a protocol change. Maybe it makes sense to specify a minimum amount of time/blocks a protocol change needs to be activated.
In terms of the dates mention, they're just examples. Feel free to suggest a different time frame.
| 1. **Unit Tests:** Every PR must pass. | ||
| 2. **Integration Tests:** Wallet, SDKs, contracts, circuits. | ||
| 3. **Network Tests:** Simulate large-scale node clusters. | ||
| 4. **Compatibility Tests:** Ensure backward compatibility with old node versions. |
There was a problem hiding this comment.
I would change "old node versions" to "previous cluster"
HDauven
requested review from
kieranhall,
welf,
ascartabelli,
miloszm,
fed-franz,
nortonandreev,
Daksh14,
moCello,
herr-seppia and
Neotamandua
Resolves #3223
This PR introduces a
RELEASE.mdoutlining a proposed release process for the Rusk monorepo. It covers branching, tagging conventions, a release lifecycle, testing phases and artifact publishing.