Skip to content

Conversation

@khwilliamson
Copy link
Contributor

It's quick to skim the podcheck summary of errors, and some things, like broken links should really be fixed before the release.

It's quick to skim the podcheck summary of errors, and some things, like
broken links should really be fixed before the release.
Copy link
Collaborator

@demerphq demerphq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't entirely get the need for this. As part of the release process we tell people to run test_porting, which runs these checks.

I don't object to it either, I am just not sure why it is needed.

verbatim lines.

But other warnings should be. In particular, a broken link can well
mean that someone clicking on the pod in a web page will get a 404.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There should be a blank line after this one and before the next =head3

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks

@khwilliamson
Copy link
Contributor Author

The impetus for this was, IIRC, that 5.36.0 shipped with broken links. As the text says, people wrongly silence podcheck warnings, and this adds a quick double check that that hasn't happened.

@khwilliamson
Copy link
Contributor Author

I've added to the text more, but can't get github to accept it without a merge commit. So I'm closing this request, and opening a replacement

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants