tgreenx

@mattias-p Do you consider the document satisfying enough nowadays? I am following it every release and it does seem up to date to me.

@matsduf Can this issue be closed? We have installation instructions for FreeBSD in [every component](https://github.com/zonemaster/zonemaster/tree/v2023.1.3/docs/public/installation). And https://github.com/zonemaster/zonemaster/blob/v2023.1.3/docs/internal/distrib-testing/FreeBSD-build-environment.md.

@mattias-p As @matsduf pointed out I think this can be closed. [Step 18 of the Release Process](https://github.com/zonemaster/zonemaster/blob/v2023.1.3/docs/internal/maintenance/ReleaseProcess-release.md#18-merge-master-into-develop) covers this issue. This was solved by https://github.com/zonemaster/zonemaster/pull/1066.

@matsduf Can the current rewrite of DNSSEC10 (#1179) take into account this issue?

Solved in v2022.2 by https://github.com/zonemaster/zonemaster-gui/pull/341.

Solved by #1149 (and implemented in https://github.com/zonemaster/zonemaster-engine/pull/1219, release v2023.1).

Relates to #1188

Solved by #870 in release v2022.2.

Hi @Ressy66, in v2023.1 we have added a new Test Case specification, [Zone11](https://github.com/zonemaster/zonemaster/blob/v2023.1.3/docs/public/specifications/tests/Zone-TP/zone11.md) ("SPF policy validation"), but it has not yet been implemented (see https://github.com/zonemaster/zonemaster-engine/issues/1279). Once it is implemented (planned...

@matsduf There is no "Changes" template still to this day but the document, while it has changed a bit from the start, is looking consistent enough. Do you want to...