This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author petdance
Recipients amaajemyfren, docs@python, hroncok, petdance, vstinner
Date 2020-05-28.15:20:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1590679204.57.0.889512423121.issue40770@roundup.psfhosted.org>
In-reply-to
Content
Some high-level questions to consider:

* Is it run only when a build of the docs is started?  Or should it be done regularly (daily/weekly?) to keep an eye on links so that it's not a surprise when build time comes along?

* Does a broken link stop the build, or is it just advisory?

* Who sees the results?  Are they emailed to someone?  A mailing list?  Posted somewhere publicly?

* Is someone assigned responsibility for acting on the failures?

* What counts as a failure?  Is a 301 redirect OK?  It seems that a 301 might be OK to pass, but someone should know about it to update to the new URL.

I am not familiar with the current documentation build process, so forgive me if these are already answered somehow.  I'm not looking for answers myself, but providing suggestions.
History
Date User Action Args
2020-05-28 15:20:04petdancesetrecipients: + petdance, vstinner, docs@python, hroncok, amaajemyfren
2020-05-28 15:20:04petdancesetmessageid: <1590679204.57.0.889512423121.issue40770@roundup.psfhosted.org>
2020-05-28 15:20:04petdancelinkissue40770 messages
2020-05-28 15:20:04petdancecreate