Thank you Gabriele Comoretto — the document as currently sitting on the ticket branch looks good to me. I will merge it and close this ticket.

The changes documented in DM-16768 are already implemented, and DMTR-111 has been regenerated accordingly.

There is the procedural aspect still to sort out, the changes in LVV-P15 if not already done and the folder organization in Jira to map tp the product tree.

Gabriele Comoretto — same comments here as on DM-16072. Specifically:

I'm getting confused about which fixes are available in which versions of Docsteady, and which DMTRs have which issues resolved. Given that, and given that I don't want to keep correcting the same errors in multiple places, I think the right thing to do here is wait until DM-16768 is resolved then re-generate and re-review DMTR-112. Do you agree?

As you know, I'm also confused about what has to be done to formally lift the test plan out of “draft” status, and I'd appreciate your guidance on that.
When the above have been completed, I think we can close this ticket (unless further issues arise).

New version of the document has been generated and is available at following link:

https://dmtr-111.lsst.io/v/DM-16076

Note: I used the previous created ticket branch, and I rebased on the latest master. In any case, the entire document has been regenerated from Jira using the new template.

John Swinbank, if you are OK with it, the PR can be opened.

I have made the following changes in Jira:

• Added a sentence to the test plan clarifying the scope of this work;
• Made some changes to the text in Jira following suggestions on the GitHub PR (some of the suggestions there were stylistic, rather than matters of correctness; I have not made changes I disagreed with, and I trust that's ok!).

A number of the comments on the PR refer to typos in Docsteady, which have been or are being addressed elsewhere.

Gabriele Comoretto, when Docsteady is ready to go, please generate a new version of the DMTR. At that point, I think we can close this ticket.

Meanwhile, given there's no disagreement with the test plan as defined in Jira, I think we're ready to execute these tests as soon as the v17 release is out.