andygrove commented on issue #30: URL: https://github.com/apache/datafusion-iceberg/issues/30#issuecomment-6173139005
Sorry to add any more confusion to this discussion, but it came up in the weekly sync today. Here is my thinking on the choices: ## Option 1 - no change to existing crate names - `iceberg-datafusion` users can continue to upgrade to new versions as they are released. The fact that the source code moved to a different repo is of no concern to them. - `datafusion-iceberg` users see no changes. ## Option 2 - rename two crates - `iceberg-datafusion` users don't see any new releases and may not realize that the crate got renamed to `datafusion-iceberg`. This is especially confusing since there is already a `data fusion-iceberg` crate that they may already know about and dismiss as an option - `datafusion-iceberg` users get a big surprise on their next upgrade Maybe we should just leave things as they currently are? -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
