[16:49] <udsbotu> uds-room-208: 5 minutes left in this session!
[16:50] <udsbotu> uds-room-208: 4 minutes left in this session!
[16:51] <udsbotu> uds-room-208: 3 minutes left in this session!
[16:52] <udsbotu> uds-room-208: 2 minutes left in this session!
[16:53] <udsbotu> uds-room-208: 1 minute left in this session!
[16:54] <udsbotu> uds-room-208: This session has ended.
[17:57] <SpamapS> WHAT is higher priority than triage?!
[17:58] <SpamapS> sponsorship queue has been really good
[17:59] <SpamapS> I am there
[17:59] <SpamapS> I am everywhere
[17:59] <SpamapS> Wife is having baby soon.. don't want to miss it :)
[17:59] <SpamapS> In fact, I have to run to an appointment in 30 min
[17:59] <SpamapS> so don't start late
[18:02] <SpamapS> +1 thats what I do exactly as well.
[18:03] <SpamapS> apport has code to aggregate them
[18:05] <SpamapS> Frankly, I like the expiring of old unanswered reports.
[18:06] <SpamapS> A bug report that a reporter cannot explain and that a developer cannot progress *IS* Invalid
[18:07] <SpamapS> you can re-open your invalid report
[18:10] <SpamapS> If a developer is working on the problem and needs no more information, that is In Progress, not Incomplete.
[18:10] <rbasak> SpamapS: the problem with Invalid is that that it won't appear on a search if we try and investigate the issue later
[18:10] <Ursinha> SpamapS, but invalid reports don't show by default and it might be rude to the reporter to invalidate (specially if the problem is valid)
[18:11] <Ursinha> SpamapS, I was talking about missing information
[18:12] <rbasak> Say there are ten bugs of the same issue. The first one gets marked invalid. The second one gets marked Invalid. Etc. When actually we want to notice in aggregate that ten of the same report warrants significant further information.
[18:12] <SpamapS> I'm actually comfortable with looking at the bugs that everyone else has already looked at for that reason. New status on mysql means more to me than others, because I have worked on that package.
[18:13] <SpamapS> Per the Invalid status, I see the flaw in moving things to Invalid too soon.
[18:13] <rbasak> The trouble is that it effectively spams our triage list.
[18:14] <SpamapS> I don't seek to clear each queue. I work each tab each equally. 1 from New/Undecided, 1 from New Bugs, ..etc. etc.
[18:15] <SpamapS> IMO, we're just behind.
[18:16] <SpamapS> I would like to have a way to hide the bugs that have been looked at by everybody.
[18:17] <SpamapS> the response will make it "Incomplete ( with response )"
[18:18] <med_> so SpamapS you want the status to change when all reviewers have eyeballed it (and unable to work it)
[18:18] <SpamapS> rbasak: re the age sort. I work one from the oldest list, and then one from the newest.. so top, then bottom, then top..
[18:18] <rbasak> SpamapS: I think you're working around the real problem. That isn't really a solution.
[18:19] <SpamapS> Because the newest ones are the easiest, but the oldest ones are, as you say, the ones that need to be revisited.
[18:20] <SpamapS> rbasak: indeed, I want them to go away from my view when I've looked at them.
[18:20] <SpamapS> I think its worth leaving it on everybody else's lists though.
[18:21] <arosales> Could we just tag it as "screened" meaning someone has taken a first look at it, but not yet triaged?
[18:21] <SpamapS> guys I have to run, good discussion. I trust you all to come up with good ideas!
[18:21] <arosales> see you SpamapS
[18:49] <udsbotu> uds-room-208: 5 minutes left in this session!
[18:50] <udsbotu> uds-room-208: 4 minutes left in this session!
[18:51] <udsbotu> uds-room-208: 3 minutes left in this session!
[18:52] <udsbotu> uds-room-208: 2 minutes left in this session!
[18:53] <udsbotu> uds-room-208: 1 minute left in this session!
[18:54] <udsbotu> uds-room-208: This session has ended.