GitHub user rajsite closed a discussion: Context for the move of Arrow JS and version policy
1. I see the [issue](https://github.com/apache/arrow/issues/46702) and [PR](https://github.com/apache/arrow/pull/46703) that moved the Arrow JS implementation out of the arrow monorepo. Is there discussion for that direction change one can reference? 2. We use arrow for interoperability from .NET C# (Blazor) and JS and just relied on the monorepo version alignment to not worry about compatibility. Now it's possible to be out of sync (arrow js is currently v21 while arrow dotnet is v20). - With the change is there a policy on versioning and compatibility between monorepo and arrow-js? - Arrow has [Format Versions](https://arrow.apache.org/docs/format/Versioning.html#post-1-0-0-format-versions) which I think is supposed to address this concern but I can't find documentation of what format version libraries are supporting. Is that what we should rely on now that we can't rely on monorepo versioning and how would we do that? GitHub link: https://github.com/apache/arrow-js/discussions/204 ---- This is an automatically sent email for user@arrow.apache.org. To unsubscribe, please send an email to: user-unsubscr...@arrow.apache.org
