4 ms·
> Every change has to be backwards compatible, and there can be no side-effects of random rollbacks, sometimes even across several versions How does that rule
by seanwilson 7y ago
> Every change has to be backwards compatible, and there can be no side-effects of random rollbacks, sometimes even across several versions
How does that rule work out in practice? If you're doing staged rollouts of new builds because you think there's a decent chance those new builds have bugs in them, shouldn't you realistically expect that rollbacks could have unexpected side-effects?
- tantalor 7y ago> expect that rollbacks could have unexpected Expect the unexpected? Sure anything can happen. But paxys is specifically referring to expected (known) side-effects of rollbacks. For example if Foo and Bar are on versions Foo.3 and Bar.3, and we know rolling back to Bar.2 breaks Foo.3, then you broke backwards compatibility. Generally all combinations of possible rollbacks must continue to work, e.g., {Foo.2, Foo.3} x {Bar.2, Bar.3}. The number of rollbacks is limited to 1 or 2 versions, e.g., Foo.1 and Bar.1 cannot be used anymore.