I'd rather mirror closely what numpy and scipy are doing, while we are getting more familiar with the release process.
I guess it was done to be more convenient, you build and test all the wheels, approve upload on testpypi.org, test locally, and then can approve the upload to PyPI. Without the chain workflow you have to build and test twice, which is quite costly since right now can take 1-2 hours (because of the macOS 5 concurent runners limitation + the fact that we have 7 slow macOS-intel build and 7 faster macOS arm builds).
I'd rather mirror closely what numpy and scipy are doing, while we are getting more familiar with the release process.
I guess it was done to be more convenient, you build and test all the wheels, approve upload on testpypi.org, test locally, and then can approve the upload to PyPI. Without the chain workflow you have to build and test twice, which is quite costly since right now can take 1-2 hours (because of the macOS 5 concurent runners limitation + the fact that we have 7 slow macOS-intel build and 7 faster macOS arm builds).