alamb commented on issue #37: URL: https://github.com/apache/arrow-datafusion/issues/37#issuecomment-827176059
> Do we have a strict policy around dependency version bumps and their potential impact on dependent crates? I do not think we have any strict (or written) policy about this > For example, say Tokio releases a theoretical 2.0 which doesn't play nicely with the 1.x runtime (similar to the 0.2 => 1.0 transition), would we be ok upgrading to v2 and requiring that DataFusion users do the same? This is what we did when tokio went to 1.0 > Would that require a major version bump for DataFusion? It seems like a good idea :) Prior to 1 week ago the datafusion major release numbers were tied to the arrow major release numbers, so we didn't have the flexibility to implement such a policy. Defining one seems like a good idea -- 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. For queries about this service, please contact Infrastructure at: [email protected]
