amoeba commented on issue #43904: URL: https://github.com/apache/arrow/issues/43904#issuecomment-2599296924
Good call on doing that search. If we just stop uploading to gemfury and those projects don't migrate, I guess they'll think they're testing against a recent PyArrow nightly when they're actually just getting the last version we published to gemfury which could be very out of date. Maybe we can do the following: 1. Stop uploading nightly wheels to gemfury 2. Post to the dev list (using careful language to make it clear the nightlies aren't an official release, etc, etc) 3. Filter through that GitHub search and identify repos to file issues against to notify of the change and give them a cutoff date 4. Disable/delete or otherwise remove the arrow-nightlies index so installs against it fail. This would be done Is that too much? If it sounds good, I can take on 1, 2, and 3 if someone with credentials can do 4 when the time comes. -- 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]
