Closed Chris-Hibbert closed 5 months ago
@turadg pointed out the seat created in upgrade-10 should still be live, and can be inspected to verify that the seat was fixed by 8682
I don't see #8123 in this plan. Is that on purpose?
@anilhelvaci Anil is doing some work on vault stuff and noticed that vaults do, in fact, lose the state of their governed parameters on upgrade.
I don't see https://github.com/Agoric/agoric-sdk/issues/8123 in this plan. Is that on purpose?
Yes. It was never included in lists of goals that I saw. AIR, We explicitly decided to deal with the consequences of non-persistent governance.
We decided (2/12) to upgrade from master rather than a branch ...
That's now reified as:
perhaps that should go in the task list here?
Last I heard, we were not planning to do any of the actually planned upgrades from master, but getting there is somewhere between a goal and a pious hope. I'm pretty sure something called upgrade 15 will go out without being pulled direct from master.
I think the things on this list are closer to upgrade 17 at this point, and so it's possible we'll include @9252, but I wouldn't consider it gating.
What is the Problem Being Solved?
A plan for the userland updates for Upgrade 15
Steps (in order)
We decided (2/12) to upgrade from master rather than a branch, so it's not necessary to make branches. We still need the coreEvals.