Bug Squad meeting, 2011-10-22 18.00h UTC

Meeting items:
1  backport request (witch component, rpm package, new rpm package request ?)
2  package request (maybe we can add a template for the new one so we can the list beautiful and readable
3  Groups permission, add status ?
4  what to do for unconfirmed bug. (like bug 2081)
5  May we use NEEDINFO keyword for an old triaged bug that isn't assigned to a maintainer, when we need to ask whether the bug still exists in current release(like 350)
6   The ASSIGNED status doesn't mean assigned, it means that the maintainer started to work on the bug. That is very confusing and not according to Bugzilla https://bugs.mageia.org/page.cgi?id=fields.html#status
7   According to the triage guide, we must sometimes set a bug to the RESOLVED - REPORTEDUPSTREAM resolution, however, our Bugzilla doesn't have the REPORTEDUPSTREAM resolution
8   https://bugs.mageia.org/show_bug.cgi?id=1364 Does it irritate most of us, to have to fill out a comment field when closing a bug as duplicate?

# 1 backport request (witch component, rpm package, new rpm package request ?)

#AGREED: Backport requests should get the component "RPM Packages" and the keyword "Backport"

#2  package request (maybe we can add a template for the new one so we can the list beautiful and readable

#AGREED leuhmanu will make a template for new package requests and enable us to try it out on his test Bugzilla

#3  Groups permission, add status ?

#AGREED postpone
#POSTPONE

#4  what to do for unconfirmed bug. (like bug 2081)
Marja overlooked this item, and no one noticed
#NEXTMEETING what to do for unconfirmed bug. (like bug 2081)

#5  May we use NEEDINFO keyword for an old triaged bug that isn't assigned to a maintainer, when we need to ask whether the bug still exists in current release(like 350)

#AGREED When more information is needed from the reporter:
1. As a try-out do the following without putting anything extra on the whiteboard, to see if it works:
2. set NEEDINFO keyword when asking for needed information in a comment
3. use a saved search for NEEDINFO untriaged bugs untouched for more than 2 weeks to ping the reporter if this wasn't done, yet
4. and close the bug when the reporter has already been pinged.(= more than 4 weeks after asking for needed info)

#AGREED When the needed info is needed for proper triage, to remove old "Triaged" keyword when setting the NEEDINFO one, but else to have both keywords.

#6   The ASSIGNED status doesn't mean assigned, it means that the maintainer started to work on the bug. That is very confusing and not according to Bugzilla https://bugs.mageia.org/page.cgi?id=fields.html#status

# SKIPPED this item because it is already being addressed sufficiently in stormi's proposal for bugstatuses and workflow

#7   According to the triage guide, we must sometimes set a bug to the RESOLVED - REPORTEDUPSTREAM resolution, however, our Bugzilla doesn't have the REPORTEDUPSTREAM resolution

#AGREED add the CLOSED/UPSTREAM status for bug reports about upstream issues we decide to close, but not add the  (WAITING_FOR_UPSTREAM) status for the ones we keep open, yet.


The meeting was closed at 20:13h UTC