docs/52041: testing new mdoc-bug class

[Gary W. Swearingen]

Giorgos Keramidas <keramida at freebsd.org> writes:

> Argh!  I hadn't noticed this class.  This makes it silly to make a class
> for doc-src bugs, since then we'd have change-request PRs for both SGML
> and manpages.

We already had that -- the "change-request" class overlaps with all of
the other classes including the old "doc-bug" one.  Splitting "doc-bug"
doesn't add to the silliness.

It seems that the "class" is dividing in two ways: "bugs vs. non-bugs"
and "base code vs. (src & doc) docs vs. ports".  Ideally, you'd have two
fields for this.

To keep the current fields (but with new elements), I'd probably just
remove the bug/change information from "class" (and maybe add a new
"change-request" (or "NA") element to the "severity" field).

But the easiest fix is probably to have classes something like this:

    base-sw-bug,         base-sw-change,
    base-doc-bug,        base-doc-change,
    fdp-doc-bug,         fdp-doc-change,
    port-user-bug,       port-user-change,
    port-maintainer-bug, port-maintainer-change