Bug 198152 - Issues with >1 cat/port (with maintainers) references in title get no Assignee, only CC's
Summary: Issues with >1 cat/port (with maintainers) references in title get no Assigne...
Status: Open
Alias: None
Product: Services
Classification: Unclassified
Component: Bug Tracker (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Only Me
Assignee: Bugmeister
URL:
Keywords: feature, needs-qa
Depends on:
Blocks:
 
Reported: 2015-03-02 10:46 UTC by Kubilay Kocak
Modified: 2015-03-02 10:47 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kubilay Kocak freebsd_committer freebsd_triage 2015-03-02 10:46:20 UTC
If an issue summary contains multiple cat/port references (both with MAINTAINER, the current auto-assigner process results in no assignee. This is a degenerate (via ambiguity) case.

For example:

Title: cat1/port1: Build breaks when cat2/port2 is installed

Current result after auto-assigner:

Assignee: freebsd-ports-bugs
CC: maintainer-port1,
    maintainer-port2

The port then (ideally) needs to be assigned to the correct maintainer, in a separate and additional step. See bug 198136 as an example

Should this be changed to:

Assignee: maintainer-port1
CC: maintainer-port2

More precisely, that for:

a) Issue summaries containing multiple cat/port references,
b) The first referenced cat/port MAINTAINER is set as Assignee,
c) IF and ONLY if the first referenced port is maintained (not ports@), AND
d) All subsequent referenced cat/port maintainers are added to CC for those that are maintained (not ports@)

Note: If the first references port is UNMAINTAINED, standard rules would apply (Assignee: freebsd-ports-bugs) as is currently the case.

If the first cat/port reference is not the port with the issue (false-positive), then it should be re-assigned. This doesn't increase workflow overhead compared to the current state.