4 ms·
what exact production headaches you are expecting by bump the number from 1.13 -> 2.0, while all existing codes keep working as before? And how is it different
by mi_lk 4y ago
what exact production headaches you are expecting by bump the number from 1.13 -> 2.0, while all existing codes keep working as before?
And how is it different from bumping 1.13 to 1.14, even if they named it 1.14?
- belval 4y agoThe soft kind. Major versions are deeply ingrained as "possible backward-compatibility issues" in most engineers' brain. If you handle model development, evaluation and deployment yourself than sure you won't have any issues, but in a bigger organization you have to get people to switch and that version number will mean that everyone will ask the same "hang on this is a major version change?!" question every step of the way.