summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormattip <matti.picus@gmail.com>2022-03-26 23:02:11 +0300
committermattip <matti.picus@gmail.com>2022-03-26 23:02:11 +0300
commit23f28f1b714d991f65e1e741231e8d775fd5fce1 (patch)
treea802d9e7c4de6045aa561f4c6ffaf758fe599b34
parent119bf865b15747bea815ec3ced10e2bbc1ba8de1 (diff)
downloadnumpy-23f28f1b714d991f65e1e741231e8d775fd5fce1.tar.gz
DOC: document automatic wheel building for a release
-rw-r--r--doc/RELEASE_WALKTHROUGH.rst.txt9
1 files changed, 7 insertions, 2 deletions
diff --git a/doc/RELEASE_WALKTHROUGH.rst.txt b/doc/RELEASE_WALKTHROUGH.rst.txt
index c4e305909..ff50b6571 100644
--- a/doc/RELEASE_WALKTHROUGH.rst.txt
+++ b/doc/RELEASE_WALKTHROUGH.rst.txt
@@ -126,8 +126,8 @@ source releases in the latter. ::
$ paver sdist # sdist will do a git clean -xdfq, so we omit that
-Build wheels
-------------
+Build wheels via MacPython/numpy-wheels
+---------------------------------------
Trigger the wheels build by pointing the numpy-wheels repository at this
commit. This can take up to an hour. The numpy-wheels repository is cloned from
@@ -163,6 +163,11 @@ Note that sometimes builds, like tests, fail for unrelated reasons and you will
need to rerun them. You will need to be logged in under 'numpy' to do this
on azure.
+Build wheels via cibuildwheel
+-----------------------------
+Tagging the build at the beginning of this process will trigger a wheel build
+via cibuildwheel and upload wheels and an sdist to the staging area.
+
Download wheels
---------------