raulk

Atom is already on 1.10.x. Downgrading to a version prior to 1.9.x means going back two minor releases, which at least I won't do for the sake of a single...

I'm going to try and stake a stab at this.

This is technically TBD until the team has time to ship FEVM safely, take a step back, assess Wasm scope, and come up with a more detailed timeline. We can...

There are roughly two approaches here: 1. One FVM release per network version, with client importing all and selecting which version of the FVM to instantiate depending on the network...

@Stebalien Please add your input here, and let's aim to close this issue with a final decision.

Now that we're embarked on M2 development, I'd like to revisit this discussion and come to a consensus. I'd like to hear from client implementors about the "sliding versions" approach,...

@Stebalien Separately from the above, I wanted to talk specifically about version number usage. The model you propose implies staying on v1 forever, but I'm pretty sure we'll introduce breaking...

@anorth Now that we have a better line of sight into the kinds and magnitudes of code changes that will go into M2, as well as future features, I'm withdrawing...

> > Every network version is a new major version of ref-fvm, with a "flip the page" mental model. > > For M2, yes. But not necessarily _every_ network version....

This discussion resulted in a successful outcome above. Closing.