upgrade-12 handler that includes zoe upgrade etc.

[dckc]

What is the Problem Being Solved?

We plan to upgrade walletFactory, zoe, etc. in upgrade 12. The currently tested mechanisms involve expensive install-bundle transactions followed by core-eval proposals. To save the expense, among other reasons, we plan to use one software-upgrade proposal, including all relevant core proposals, to do the upgrade.

Description of the Design / Test Plan

Should #8219 be in scope here? Conservatively, let's say yes, for now...

Tasks

Beta Give feedback

1. migrate walletFactory upgrade from a separate core-eval proposal to part of the software-upgrade proposal
2. migrate the zoe and zcf upgrade likewise
3. re-organize zoe and zcf upgrades in writeCoreProposals style, if not already done
4. add code to upgrade all upgradable vats during agoric-upgrade-12 #8219
   1 of 1
   enhancement +1
5. revive zoe-full-upgrade test #8121
   Zoe contract-upgrade deployment enhancement +4
   

For reference:

#8112 introduced --upgrade-info='{"coreProposals":[...]}' and #8166 integrated it with docker upgrade-tests.

Security / Scaling Considerations

not much

Upgrade Considerations

yes. :)

[ivanlei]

This is no longer the plan of record.

[dckc]

let's close it as "not planned"

[dckc]

no longer the plan