dave0802/13/2023, 4:50 PM
raulraja02/13/2023, 5:11 PM
simon.vergauwen02/13/2023, 5:42 PM
0.x seriesTo put some more perspective, Arrow 1.x was release almost 2021 and Arrow 2.x is being released later this year. Within 1.x.x there were no breaking changes, and the last version of 1.x.x will be source compatible with 2.x.x. 1.x.x -> 2.x.x will remove some obscure APIs, and further clean-up some old legacy things that are not being used.
dave0802/13/2023, 6:27 PM
simon.vergauwen02/13/2023, 6:30 PM
very minimal changesThis can be done in a binary compatible way, so we might just stick to 2.x.x even when context receivers land into the language.
and check the PRs for all remaining work that is still to be merged before the
dave0802/20/2023, 2:58 PM
simon.vergauwen02/20/2023, 3:29 PM
is stable, but is it production-ready?Yes, it's production-ready.
Also, even if not, maybe it would be possible to have a release with a bunch of typealiases with the new names to avoid new projects having to migrate?This is already the case, current
is what will be released as
in 2-3 weeks and all non-deprecated code will be source and binary-compatible with
+ everything from
if it will be removed from
and all non-deprecated code will remain unchanged. We're still figuring out how to deprecate
nicely, and plan a migration plan. This can potentially be partially be automated as well. We want everything to be as automatic, and as painless as possible.