GitHub user xuang7 added a comment to the discussion: Policy and guidance on upgrades and backwards-compatibility between versions
Thanks for starting this discussion. I think we currently don't guarantee full compatibility across upgrades, so it would be good to make users aware of this and recommend backing up important resources before upgrading. I agree with having upgrade tests. A simple and useful version would be to boot version N, load some data through the app, then boot N+1 on the same volumes and verify that the data is still readable through the API. This should be possible to automate. I would avoid making patch releases an absolute compatibility guarantee, though. A more practical rule could be that patch releases should not break compatibility by default, and if an exception is unavoidable, the release should include a clearly documented. This is especially important for the storage changes we recently made. Some use cases may involve TB-scale datasets, so even a technically supported migration can have significant operational cost. For future releases, if there are any known compatibility issues, we should clearly document them along with the supported migration path. GitHub link: https://github.com/apache/texera/discussions/8570#discussioncomment-18487371 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
