Skip to content

Commit 5f26c5a

Browse files
committed
Clarify which files should be uploaded
1 parent 4444372 commit 5f26c5a

File tree

1 file changed

+5
-7
lines changed

1 file changed

+5
-7
lines changed

peps/pep-0101.rst

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -352,7 +352,8 @@ and guides you to perform some manual steps.
352352
downloads.nyc1.psf.io together with GPG signature files.
353353

354354
- ``scp`` or ``rsync`` all the files built by the build-release workflow
355-
to your home directory on ``downloads.nyc1.psf.io``.
355+
to your home directory on ``downloads.nyc1.psf.io``, along with any
356+
signatures, SBOMs, etc.
356357

357358
While you're waiting for the files to finish uploading, you can continue
358359
on with the remaining tasks. You can also ask folks on Discord
@@ -367,12 +368,9 @@ and guides you to perform some manual steps.
367368
creating it if necessary. Make sure it is owned by group ``downloads``
368369
and group-writable.
369370

370-
- Move the following files into place:
371-
372-
- The ``.tgz``, and ``.tar.xz`` source tarballs, as well as their ``.asc``
373-
GPG signature files.
374-
- The Android binaries (if Python 3.14 or later).
375-
- The Win/Mac binaries are usually put there by the experts themselves.
371+
- Take the files you uploaded to your home directory above, and move them
372+
into the release directory. The Win/Mac binaries are usually put there
373+
by the experts themselves.
376374

377375
Make sure they are world readable. They should also be group
378376
writable, and group-owned by ``downloads``.

0 commit comments

Comments
 (0)