Update release-process.md #68
Conversation
I've made some small edits to reflect the new protocol upgrades governance process
✅ Deploy Preview for op-stack-pm ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| | T-3 weeks | Stakeholder veto period starts | | ||
| | T-3 weeks | Sepolia deployment | |
There was a problem hiding this comment.
Is this right? My understanding was that the veto period starts 1 week before the mainnet activation?
There was a problem hiding this comment.
we can start it at any point after the DAB review. is complete - 1 week before mainnet activation is also ok. I was assuming the sooner the better
There was a problem hiding this comment.
Ah I see. I think it is common to look at this the other way, as in "what's the tightest schedule that can be run" in terms of going from code complete to activation.
|
|
||
| **All features must go through an Alphanet and a Betanet before being deployed on Testnet.** This means that you | ||
| should target having your features deployed to the Alphanet and Betanet right before the gov cycle at the very latest. | ||
| For example: |
There was a problem hiding this comment.
| For example: |
| validation. | ||
| 4. If the feature works on Betanet, it gets deployed to the Sepolia Testnet for governance review. | ||
| 5. If governance passes, the feature is deployed to mainnet. | ||
| 4. As soon as code is frozen, the upgrade proposal can be posted to the forum and the Developer Advisory review period starts (7d). |
There was a problem hiding this comment.
I'm not sure what is that we mean here with the code being "frozen", and how it differs from the "Feature is code-complete" at T-6 weeks.
According with the SDLC, audits happen before the Alphanet deployment, and we aim to have no more code changes after the audits.
So I assume that the DAB review should start at T-6, and not T-4?
Note as well that Alphanet and Betanet testing is intended to surface faults that couldn't be detected without realistic usage. The DAB review is closer in spirit to the audit, and should happen in parallel with the same, so T-6.
There was a problem hiding this comment.
For the DAB review to start, we should have no more code changes. So if that's at T-6, that's a reasonable starting point. When I spoke to Seb he mentioned that for upgrades that touch the fault proof system we need to generate an absolute prestate hash which might happen a bit later, closer to the start of the deployment on Sepolia. The timeline probably depends a bit on the upgrade ...
|
|
||
| 1. Features are developed according to a stable-trunk development model. | ||
| 2. Features are deployed to an Alphanet for initial acceptance testing. | ||
| 2. Features are deployed to an Alphanet for initial acceptance testing. The Developer Advisory Board should be kept in the loop. |
There was a problem hiding this comment.
Can we have a link or something that gives more background on the DAB and how to get in contact with them?
There was a problem hiding this comment.
yes! will work on a separate page on that that we can link to
Description
I've made some small edits to reflect the new protocol upgrades governance process
Tests
none
Additional context
See this internal FAQ document
Metadata
none