alamb commented on pull request #68: URL: https://github.com/apache/arrow-datafusion/pull/68#issuecomment-931202056
> Trying to figure out the constraints that we are working here: what does "stable" mean in this context? we accept breaking changes to the arrow crate between major versions, and thus the expectation of stability there is 3 months? Or do we expect arrow to not change significantly between major versions and thus have a longer expectation? @jorgecarleitao From my perspective some requirements for an arrow implementation used in DataFusion are: 1. The feature set is "close enough" to the current implementation of arrow that all DataFusion tests pass 2. There is a clear path, ability and willingness to help close any other gaps between the existing arrow-rs implementation 2. There is a community committed to its development and maintenance, under some sort of formal community project governance model (e.g. Apache Arrow) In terms of technical requirements, I agree with @houqp that it is also desirable to be able to release bug fixes for some period of time that does not also require taking breaking API changes. However, this is largely mechanical work (eg. what I do for arrow-rs) and I think can be applied to most any codebase. What is needed is interest / willingness from the community to do it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
