Used for training new triagers and up-skilling existing project developers on a group basis, rather than individually (scale!).

Use in combination with Bugzilla DO's and DON'TS, The PERFECT Ports Issue and Bugzilla Keywords

Specific examples demonstrating each will be added in future iterations

Field names and values are in italics

General

Basics

Statuses

Resolutions

Metadata: Correct and Complete

These items apply to all issues, in all (any) state

Notify Relevant/Interested Contributors

Examples

Closed/Closing Issues

Ports Specific

Base Specific

Onboarding

Comment Templates

Get things merged: Updates that are bugfix releases

Comment:

^Triage: Bugfix release, merge to quarterly branch

Get things merged: Updates that are security releases

Comment:

^Triage: Security release, merge to quarterly branch

Get things merged: Updates that might be relevant to quarterly users

Comment:

^Triage: Are quarterly users affected? If so, please set merge-quarterly flag to: ?

Updates without QA

Comment:

^Triage: Please confirm this change passes QA (portlint, poudriere at least)

For details and instructions, see:

https://docs.freebsd.org/en/books/porters-handbook/#testing

Comment:

^Triage: If there is a changelog or release notes URL available for this version, please add it to the URL field

Reporter is not MAINTAINER, doesn't set maintainer-approval (to ?)

Comment:

^Triage: Please set the maintainer-approval attachment flag (to ?) and set the requestee field to the e-mail address of the maintainer to ask for maintainer approval

Attachment -> Details -> maintainer-approval [?]

Reporter is MAINTAINER, doesn't set maintainer-approval (to +)

Comment:

^Triage: Please set the maintainer-approval attachment flag (to +) on patches for ports you maintain to signify approval

Attachment -> Details -> maintainer-approval [+]

Reporter is MAINTAINER, sets maintainer-feedback (to +)

Comment:

^Triage: Maintainer-feedback flag (+) not required unless requested (?) first

Reporter is a committer, doesn't self-assign, MAINTAINER is not committer

Comment:

^Triage: Reporter is committer, assign accordingly.

Closing an issue with !FIXED resolution (in particular ''Unable to Reproduce'')

Comment:

^Triage: If this is still reproducible, please re-open this issue with additional information and steps to reproduce if not already provided

Commit references the issue (``PR: XXXX``), but committer has not assigned themselves

Comment:

^Triage: Assign to committer resolving

Note: Keep/Add original Assignee on CC list if its a group or mailing list (like net@, python@, etc)

[tags] are used in issue Summary

Comment:

^Triage: [tags] in issue Titles are deprecated

Issue is a 'general support' question

Comment:

^Triage: Thank you for your report. Our issue tracker is used for issues identified to be bugs and enhancements.

For general support, questions and issues, the following channels are available to the community:

  https://www.freebsd.org/support.html

If your issue is isolated to be a bug and is reproducible on an up-to-date and supported FreeBSD version, please re-open this issue with additional information and steps to reproduce.

Reporter is Committer but without a specific repository bit

Comment:

^Triage: Reporter is committer, assign accordingly

Any committer may commit to any repository with an accepted review from any committer with existing access to that repository.

Committers may obtain review via a Differential in Phabricator, adding the "Contributor Reviewers ($Repository)" group as a Reviewer, reaching out to other committers; directly or via mailing lists, or setting the attachment flag to: maintainer-approval ? <person-youd-like-to-review>

Bugzilla/TriageTraining (last edited 2021-09-30T22:36:39+0000 by KubilayKocak)