3 ms·
It's actually not. Versioning is a concept where each version lives in non-intersecting time intervals. This concept is completely focusing on the fact that y
by marcosdumay 1y ago
It's actually not.
Versioning is a concept where each version lives in non-intersecting time intervals.
This concept is completely focusing on the fact that your structures lifetimes must absolutely have non-empty intersections. It's close to the opposite.
- chrisweekly 1y ago> "Versioning is a concept where each version lives in non-intersecting time intervals." Is it? Node.js publishes "Current", "LTS" and "Maintenance" versions, and there's always a reasonable time interval during which consumers typically upgrade from eg Maintenance to newer LTS or even Current. From the publishing side, that's very similar to "expand and contract", in temporarily expanding what's supported to include Current, and dropping support for oldest versions leaving Maintenance. It's continuous instead of ad hoc, and there are more than 2 versions involved, but the principle is basically the same (at least if you squint). Though I guess if you're talking strictly about schema management strategies, then yeah, "versioning" might be very different from "expand contract", as you noted.
- UltraSane 1y agoIt is often necessary to use multiple versions at the same time