jorisvandenbossche commented on PR #375: URL: https://github.com/apache/arrow-adbc/pull/375#issuecomment-1401696346
I am wondering: do we need / want this? I know we build conda packages in the main Arrow CI, but my experience is that this is 1) quite uncommon (I don't know any other package I contribute to that does this, but to be fair those packages also don't have such a complicated build setup, but adbc is also much less complicated compared to arrow), and 2) gives quite some maintenance overhead to keep this up to date and synced with upstream conda-forge. If the reason to do this is to ensure that our conda packages will work before doing the final release (avoid needing to patch/make a bug fix release if the upstream conda packages turn out to be failing with a new release), we can also trigger a build in the upstream conda-forge feedstock once a first RC is out, and that way ensure conda builds are passing before the final release. (note, I am currently not actively contributing to this repo and helping its maintenance, so I don't have much of a say in this, but at least I wanted to mention the option that we can also _not_ do this ;)) -- 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]
