[Bug 267176] Writing FreeBSD Problem Reports: corrections and update

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267176

            Bug ID: 267176
           Summary: Writing FreeBSD Problem Reports: corrections and
                    update
           Product: Documentation
           Version: Latest
          Hardware: Any
               URL: https://github.com/freebsd/freebsd-doc/blob/main/docum
                    entation/content/en/articles/problem-reports/_index.ad
                    oc
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Books & Articles
          Assignee: doc@FreeBSD.org
          Reporter: grahamperrin@freebsd.org

The article pleads for use of a keyword: 

    patch

<https://docs.freebsd.org/en/articles/problem-reports/#pr-writing-tips>: 

> … If you have a patch, say so. A PR with a patch included is much 
> more likely to be looked at than one without. Please set the 
> patch Keyword in Bugzilla. …


Deprecation was not discovered until after it was batch-added to a number of
open bug reports, which had '[patch]' in the summary line but lacked the patch
(or patch-ready) keyword. 

Corrections, to signify deprecation, have since been made to: 

    <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>
    <https://wiki.freebsd.org/Bugzilla/Keywords>

Let's correct and update this article, beginning with the misdirection to use
the patch keyword. 

See also: 

<https://wiki.freebsd.org/Bugzilla/DosAndDonts>

> …
> 
> Please, do not:
> 
> * use [TAGS] like [MAINTAINER], [UPDATE], [EXP-RUN] and [PATCH] 
>   in issue titles
> 
>   – [NEW PORT] in title for new port submissions is OK for now. 
> 
> …

<https://wiki.freebsd.org/Bugzilla/ThePerfectPortsIssue> 

<https://wiki.freebsd.org/KubilayKocak/Bugzilla/ProblemsAndIdeas> 

<https://wiki.freebsd.org/KubilayKocak/Bugzilla/Roadmap> 

…

-- 
You are receiving this mail because:
You are the assignee for the bug.