Comment templates for common actions and situations during issue management.

• Set: merge-quarterly: ?

Comment:

^Triage: Bugfix release, merge to quarterly branch

• Keywords: security
• CC: ports-secteam
• Priority: High
• Severity: Affects Many People
• Set: merge-quarterly: ?

Comment:

^Triage: Security release, merge to quarterly branch

Comment:

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

• Keywords: needs-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

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 [?]

Comment:

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

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

• Set: maintainer-feedback: X

Comment:

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

• Assignee: <reporter>

Comment:

^Triage: Reporter is committer, assign accordingly.

• Assignee: <yourself>
• Status: Closed
• Resolution: <as appropriate>

Comment:

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

• Assignee: <committer>
• Status: In Progress
• review Keywords (for example, needs-qa might no longer apply).

Comment:

^Triage: Assign to the resolving committer

Notes:

• assignees kde@ (KDE) and x11@ (graphics) are exceptional, do not assign to a person unless the person chooses the assignment
• if an assignee is a group with a publicly archived list (examples include kde@, net@, and python@), or if an assignee is a private group, then place the former assignee on the CC list
  • bugs@ is exceptional, it need not be on any CC list
• if it's not certain that the person's commit will lead to resolution, then think twice before assigning to the person.

• Summary: Remove tags (except [exp-run] and [new port])

Comment:

^Triage: [TAGS] in issue Summary are deprecated

• Assignee: <you>
• Status: Closed
• Resolution: Not A Bug

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.

• Assignee: <reporter>
• Keywords: needs-qa

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>