It is possible to have a system config to disable and enable it (mainly to pass existing tests)?

Or a local variable to disable or enable by admin/owner.

It is possible to have a system config to disable and enable it (mainly to pass existing tests)?

Or a local variable to disable or enable by admin/owner.

Or we can keep this change on a separate branch, like mainnet_contracts_v1.8.0, and only use it for deployment? This way, the change is minimal.

It is possible to have a system config to disable and enable it (mainly to pass existing tests)?
Or a local variable to disable or enable by admin/owner.

Or we can keep this change on a separate branch, like mainnet_contracts_v1.8.0, and only use it for deployment? This way, the change is minimal.

If the change is simple enough, I would like to put them into the same branch to avoid extra management overhead.

If the change is simple enough, I would like to put them into the same branch to avoid extra management overhead.

We'll maintain a branch for the mainnnet contracts(and op-deployer) any way, say we can't just use the contracts in op-es for mainnet.

If the change is simple enough, I would like to put them into the same branch to avoid extra management overhead.

We'll maintain a branch for the mainnnet contracts(and op-deployer) any way, say we can't just use the contracts in op-es for mainnet.

A simple practice is that we maintain op-es and then cut a release after an official upstream release is announcement by

• merging upstream
• create a new release branch

PTAL at the implementation c0afb23, the LOC is much more than expected -_-b

5bd002b should have addressed all above comments.