Triage Templates
Comment templates for common actions and situations during issue management.
Contents
- Triage Templates
- Get things merged: Updates that are bugfix releases
- Get things merged: Updates that are security releases
- Get things merged: Updates that might be relevant to quarterly users
- Updates without QA
- Updates without changelog link
- Reporter is not MAINTAINER, doesn't set maintainer-approval (to ?)
- Reporter is MAINTAINER, doesn't set maintainer-approval (to +)
- Reporter is MAINTAINER, sets maintainer-feedback (to +)
- Reporter is a committer, doesn't self-assign, MAINTAINER is not committer, exp-run is not ?
- Closing an issue with !FIXED resolution (in particular ''Unable to Reproduce'')
- A resolving commit references the report number (PR: ⋯) and the report is not assigned to the committer
- [tags] are used in issue Summary
- Issue is a 'general support' question
- Reporter is Committer but without a specific repository bit
Get things merged: Updates that are bugfix releases
Set: merge-quarterly: ?
Comment:
^Triage: Bugfix release, merge to quarterly branch
Get things merged: Updates that are security releases
Keywords: security
CC: ports-secteam
Priority: High
Severity: Affects Many People
Set: merge-quarterly: ?
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
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
Updates without changelog link
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 +)
Set: maintainer-feedback: X
Comment:
^Triage: Maintainer-feedback flag (+) not required unless requested (?) first
Reporter is a committer, doesn't self-assign, MAINTAINER is not committer, exp-run is not ?
Assignee: <reporter>
Comment:
^Triage: Reporter is committer, assign accordingly.
Closing an issue with !FIXED resolution (in particular ''Unable to Reproduce'')
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
A resolving commit references the report number (PR: ⋯) and the report is not assigned to the committer
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.
[tags] are used in issue Summary
Summary: Remove tags (except [exp-run] and [new port])
Comment:
^Triage: [TAGS] in issue Summary are deprecated
Issue is a 'general support' question
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.
Reporter is Committer but without a specific repository bit
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>