Should we transfer MacPython/numpy-wheels to the NumPy org?
Hi All, Seems that is pretty easy to transfer a github repo to another owner. Should we do this for the numpy-wheels repo? That would put all the management in one place and now might be a good time to do it before the 1.20.x branch. Chuck
Seems like a good idea. It would need Matti or someone to set up the various keys I think?
On 10/29/20 5:42 AM, Charles R Harris wrote:
Hi All,
Seems that is pretty easy to transfer a github repo to another owner. Should we do this for the numpy-wheels repo? That would put all the management in one place and now might be a good time to do it before the 1.20.x branch.
Chuck
What is the goal? So far it is convenient that all the repos that upload to https://anaconda.org/multibuild-wheels-staging are under one org to coordinate upload token use.
I agree with Matti that keeping at least the nightly wheel building /
uploading for a bunch of projects all in on place makes sense.
Tom
On Thu, Oct 29, 2020 at 6:00 AM Matti Picus
On 10/29/20 5:42 AM, Charles R Harris wrote:
Hi All,
Seems that is pretty easy to transfer a github repo to another owner. Should we do this for the numpy-wheels repo? That would put all the management in one place and now might be a good time to do it before the 1.20.x branch.
Chuck
What is the goal? So far it is convenient that all the repos that upload to https://anaconda.org/multibuild-wheels-staging are under one org to coordinate upload token use.
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
-- Thomas Caswell tcaswell@gmail.com
On Thu, Oct 29, 2020 at 4:00 AM Matti Picus
On 10/29/20 5:42 AM, Charles R Harris wrote:
Hi All,
Seems that is pretty easy to transfer a github repo to another owner. Should we do this for the numpy-wheels repo? That would put all the management in one place and now might be a good time to do it before the 1.20.x branch.
Chuck
What is the goal? So far it is convenient that all the repos that upload to https://anaconda.org/multibuild-wheels-staging are under one org to coordinate upload token use.
My thought was administration, which was triggered by the need to move to travis-ci.com. Note that the travis app shows up on the MacPython site, and apparently is available for scipy-wheels, but is not visible to numpy-wheels. My guess is that an owner of MacPython needs to add the repo and migrate it. Chuck
On Thu, Oct 29, 2020 at 6:00 AM Matti Picus
On 10/29/20 5:42 AM, Charles R Harris wrote:
Hi All,
Seems that is pretty easy to transfer a github repo to another owner. Should we do this for the numpy-wheels repo? That would put all the management in one place and now might be a good time to do it before the 1.20.x branch.
Chuck
What is the goal? So far it is convenient that all the repos that upload to https://anaconda.org/multibuild-wheels-staging are under one org to coordinate upload token use.
One case using *multibuild-wheels-staging* that is not currently under MacPython is https://github.com/scikit-image/scikit-image-wheels. We have not actually uploaded to *multibuild-wheels-staging* yet, but will be doing so when we build wheels for the upcoming 0.18 release.
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
participants (6)
-
Charles R Harris -
Gregory Lee -
Kevin Sheppard -
Matthew Brett -
Matti Picus -
Thomas Caswell