2023Q2 status report for boot performance

[• grahamperrin]

website/content/en/status/report-2023-04-2023-06/boot-performance.adoc

12–15

17–18

20–21

[cperciva]

Fix line wrapping

[cperciva]

Dumb question, am I supposed to commit this to the docs tree, or do I just leave the review hanging here and let someone else commit it?

[pauamma_gundo.com]

In D40756#927547, @cperciva wrote:

Dumb question, am I supposed to commit this to the docs tree, or do I just leave the review hanging here and let someone else commit it?

Good question. https://docs.freebsd.org/en/articles/freebsd-status-report-process/#_building_the_report is vague on that point. I forgot: are you a docs committer? (And tangentially: did you deliberately make salvadore a blocking reviewer?)

[cperciva]

In D40756#927985, @pauamma_gundo.com wrote:

In D40756#927547, @cperciva wrote:

Dumb question, am I supposed to commit this to the docs tree, or do I just leave the review hanging here and let someone else commit it?

Good question. https://docs.freebsd.org/en/articles/freebsd-status-report-process/#_building_the_report is vague on that point. I forgot: are you a docs committer? (And tangentially: did you deliberately make salvadore a blocking reviewer?)

I'm a src+ports committer, but during the 13.2 release cycle I was doing a lot of commits to the docs repo and nobody complained. ;-)

I think salvadore was added as a blocking reviewer automatically by the herald system.

[carlavilla]

Make the commit, np

[salvadore]

Approved by me as well.
I confirm the herald rule added me as blocking reviewer: it is necessary to have status blocking the review. If you have status approval by some other status member it is fine.

You can proceed with the commit autonomously, thanks.

website/content/en/status/report-2023-04-2023-06/boot-performance.adoc

5

As in the other review, please remove the redundant links in the last brackets.