assignUser commented on issue #38872: URL: https://github.com/apache/arrow/issues/38872#issuecomment-1826204604
There recently was some discussion about potentially moving the swift implementation into a separate repo on the mailing list: https://lists.apache.org/thread/8l217nrb6kbf81w2mh94ykylck5wgrlc Looking at the SO post it seems that swift can't deal with a package that is not in the root dir of the repo? As there is some additional overhead to a dedicated repo and releases as discussed on the ml, an alternative might be to setup that repo but make it a mirror (e.g. via gha triggered on push to main or on release ...) of only the swift sub dir in the expected format and keep devlopment/releases within. Or keep the code in apache/arrow-swift but release in tandem with apache/arrow? I am sure we can find a compromise! cc @abandy -- 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]
