PEP 101: Remove DE tasks #4574
PEP 101: Remove DE tasks #4574
Conversation
hugovk
requested review from
Yhg1s,
pablogsal,
ambv and
ned-deily
as code owners
| @@ -388,8 +387,6 @@ and guides you to perform some manual steps. | |||
| ``docs.nyc1.psf.io``. Make sure the files are in group ``docs`` and are | |||
| group-writeable. | |||
|
|
|||
| - Let the DE check if the docs are built and work all right. | |||
There was a problem hiding this comment.
Arguably this step could be kept (modulo whoever does the checking), there have been recent releases where the docs haven't built properly, so it was important to check, even though CI failing/hanging alerted us to this.
A
There was a problem hiding this comment.
There's not actually a step in the automation scripts at https://github.com/python/release-tools that does this (or pauses to get someone to check it), other than the CI passing.
We could add one, if we can define something useful?
There was a problem hiding this comment.
Arguably at minimum, the HTML files should seem fine at dip-test level, the EPUB file should pass EPUBcheck, the PDF archives should contain the expected files & not be corrupt, etc. These feel like reasonable checks?
A
Since python/release-tools#71 the docs have been automatically built in the CI and there's no manual tasks for the Docs Expert as part of PEP 101.
cc @JulienPalard
📚 Documentation preview 📚: https://pep-previews--4574.org.readthedocs.build/