vegaprotocol / vegawallet-desktop

Desktop application for Vega Protocol's wallet
MIT License
15 stars 12 forks source link

REFINE: Create a smart version policy to suggest software updates #514

Closed ValentinTrinque closed 1 year ago

ValentinTrinque commented 1 year ago

Questions driving the need:

  1. Are we agreed there will always be a desktop wallet release alongside a core release so that there can always be a “matching” wallet version for all core versions?
  2. What happens when the difference is massive like if you’re using the current mainnet desktop wallet with Fairground, or with mainnet after the upgrade. This situation will cover most users for a while and needs to be handled extremely well.
  3. Do we have any mechanism for future major breaking changes or if we find a security issue and need to signal that upgrading is very important?
  4. Is there a difference between how loudly we shout about the mismatch depending on whether the release differ at major, minor, or patch semver level?
  5. Do error messages that could be caused by version incompatibility (eg a missing field that is mandatory or something on a txn) do the version check and add an additional message that this could be the reason (or include such a message hard coded)?
pennyandrews commented 1 year ago

Merging with #474