4 ms·
The change log is massive, so this is not unexpected to have a few issues. Maybe the two-year backlog of features and updates should have been batched into a fe
by jasonthorsness 1y ago
The change log is massive, so this is not unexpected to have a few issues. Maybe the two-year backlog of features and updates should have been batched into a few releases instead of this one big one? But there was a beta, and this is ripping the bandaid.
https://github.com/benbjohnson/litestream/releases/tag/v0.5.0 https://github.com/benbjohnson/litestream/releases/tag/v0.5....
- mtlynch 1y agoI think the most disruptive part is the migration to the new LTX format,[0] which I'd imagine is hard to do incrementally. [0] https://fly.io/blog/litestream-v050-is-here/#the-ltx-file-format https://fly.io/blog/litestream-v050-is-here/#the-ltx-file-fo...
- benbjohnson 1y agoLitestream author here. Yes, that's correct. LTX was the biggest hurdle to get over and was impossible to switch over incrementally. The storage layer change brings a lot of benefits and enables a lot of future work that we're really excited about. Thanks to mtlynch and everyone else who has submitted bug reports. We're squashing issues and working to get everything stable as quickly as possible.
- liuliu 1y agoFeels like a side-effect of forever 0.x version symptom (I am guilty of as well). Even though semi-ver says 0.x can do whatever, people don't associate enough disruptive changes to it, whereas 0.4.x if it is 1.x, then it is much clearer this is a 2.x release. All things considered, this is probably just a tiny footnote in this software's life.
- ncruces 1y agoThey jumped from v0.3.x to v0.5.0 after a couple of years of v0.3.x (with an unreleased v0.4.x in between). That alone should hint everyone it was a big leap.