[11:59] <brainwash> please nominate xubuntu-default-settings for trusty and utopic bug 1292290
[12:54] <teward> brainwash: you sure it's against that package and not xfce4-settings?
[12:57] <brainwash> teward: yes, I've linked my branch for vivid to the report already. the problem is caused by xubuntu-default-settings, but the underlying issue needs to be handled/fixed in xfce4-settings
[12:58] <brainwash> and I'll try to SRU an updated xubuntu-default-settings package for trusty and utopic
[12:58] <teward> brainwash: well, the SRU won't happen until it lands in Vivid
[12:59] <teward> i'll nominate but you have to keep in mind it needs to land in Vivid or be fixed in Vivid before it can truly be SRU'd backwards
[12:59] <brainwash> I know
[13:00] <teward> 'course it gets nominated for both packages against trusty and utopic >.>
[13:00] <brainwash> doesn't matter I guess
[13:00] <teward> nomination done though
[13:00] <brainwash> thank you :)
[15:04] <octoquad> Can I mark this bug report as won't fix: https://bugs.launchpad.net/ubuntu/+source/evolution-exchange/+bug/111936 Found it while looking for duplicates.
[15:08] <penguin42> octoquad: I can do that for you
[15:09] <penguin42> octoquad: if it won't let you do it - but yes it seems the right thing to do
[15:09] <octoquad> ok, busy triaging and do some housekeeping for Ubuntu Gnome
[15:09] <octoquad> thanks penguin42
[15:10] <octoquad> I assume that unassigning the person or team responsible should also happen at the same time, correct?
[15:11] <penguin42> octoquad: Nah, I'd just leave that
[15:11] <penguin42> octoquad: I'd never unassign from a person, from a team seems less of an issue, but it's probably best to let them sort it out
[15:12] <octoquad> penguin42, you will have to do it for me, I'm not part of the Ubuntu Bug Squad only Ubuntu Gnome Bug Squad so Won't fix is disabled for me.
[15:12] <octoquad> I think I should just apply now and get it over with lol
[15:14] <penguin42> ok, will do
[15:15] <brainwash> apply to bug-control?
[15:15] <penguin42> octoquad: done
[15:18] <octoquad> brainwash, yes, just applied.
[15:18] <octoquad> thanks penguin42
[15:19] <brainwash> octoquad: on the mailing list?
[15:19] <octoquad> brainwash, sorry to Ubuntu BugSquad team
[15:19] <octoquad> https://launchpad.net/~bugsquad.
[15:20] <brainwash> oh, but then you will have to apply for bug-control too
[15:20] <octoquad> fun times
[15:20] <octoquad> ok
[15:20] <brainwash> otherwise you won't be able to mark reports as won't fix etc
[15:21] <octoquad> thanks brainwash, I will apply after I've been accepted to Bug Squad.
[15:22] <brainwash> octoquad: heh, I should apply too. I'm only in bugsquad :)
[15:22] <octoquad> :)
[15:22] <octoquad> bug list could definitely do with some housekeeping. Do they have a bug housekeeping week once a year?
[15:23] <octoquad> or cycle
[15:26] <brainwash> you mean something like automatically closing reports if the affected release is not supported anymore?
[15:28] <octoquad> hmm, yeah I suppose but that can only work if the report is new and there are 0 comments. Sometimes the bug can be present over multiple cycles, so it's pretty tough to automate. I think Invalid to Expire is pretty neat, but there bugs that are 8 years old and triaged as an example or confirmed.
[15:28] <penguin42> generally I think there are things that automatically close bugs that are for a release that's now out of support
[15:28] <penguin42> so bugs do fall through the net if they are still affected
[15:41] <brainwash> octoquad: I'm doing the clean up job for Xubuntu/Xfce bug reports now and I wish too that there was some automate system to remind the bug reporter to re-test and update the report after some time without activity
[15:46] <octoquad> brainwash, that's a pretty useful. What would you recommend as the default automated response time 30/60/90/120/240/365 days? Maybe it can do it automatically for all periods and then just close due to no response?
[15:47] <octoquad> at 365 days
[15:48]  * penguin42 thought there was already a 'no activity on this bug' type of thing
[15:49] <octoquad> penguin42, yes, only if it has been marked as incomplete and no activity for 60 or 90 days depending on the project bug tracking configuration.
[15:50] <octoquad> my bad, there is no way to set the number of days.
[15:50] <octoquad> https://wiki.ubuntu.com/Bugs/Triage?action=show&redirect=Bugs%2FHowToTriage#Invalidating
[15:50] <brainwash> but someone has to mark the report as incomplete
[15:50] <octoquad> yes
[15:51]  * penguin42 had thought there was something that did it on non-incompletes
[15:51] <brainwash> and usually many reports are just filed, but then ignored for long period of time (or forever)
[15:51] <octoquad> hehe penguin42
[15:51] <octoquad> yup
[15:54] <penguin42> it's very difficult to make generalisations - for example someone might find something is badly broken, so they just give up on it; then 2 years later you ask them to retest and they don't have the machine any more, etc
[15:55] <octoquad> yes, that is one of probably many things to take in consideration, but if the original reporter is no longer able to test and nobody else is affected, then how useful is that report?
[15:56] <penguin42> yep, although it's useful to go through and look for dupes to find out actually there are bunches of bugs that no one has managed to find are actually the same thing
[15:58] <octoquad> Have a look ubiquity, classic example penguin42 I filed a bug report for ubiquity failing to complete an installation, there a few with the same issue, but reported with different subjects and descriptions, although it might be related to what I reported, or a side effect of what I reported.
[15:59] <octoquad> Sort by age, as the bug only cropped up betweek the yesterday and today.
[15:59] <octoquad> between*
[15:59] <penguin42> yes, you get lots of that type of thing
[16:02] <octoquad> nice chatting to you two, i'll be back later. ciap
[16:02] <octoquad> ciao*
[19:38] <tobias47n9e_> Is there any chance we will still see a fix for this issue in 14.10? https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1297302