[06:55] knome: Considering perhaps http://paste.openstack.org/show/cZed8nUINAyyEi0HxMKP/ [12:42] updated gtk-theme-config (with translations) pushed [12:42] updated xubuntu-default-settings with drag-workspaces enabled and classic menu fixes pushed [12:51] Fancy. [13:03] Unit193, looks good to me [13:08] knome - started a pad for later - http://pad.ubuntu.com/trackers [13:08] biab [13:08] great [13:12] Benefit is make test will fail if validation fails. [13:15] yep [14:35] Noskcaj, do you have a deadline for a new xfdesktop release date? [15:32] bluesabre: wow, awesome MR from andrew === brainwash_ is now known as brainwash [15:58] good morning pleia2! [16:01] * pleia2 yawns and grumps [16:01] heh [16:01] back in 2 mins. [16:04] * elfy is floating about [16:05] shall we make an etherpad to collect a bug list? [16:05] http://pad.ubuntu.com/trackers [16:05] :) [16:06] \o/ [16:06] reading backscroll ftw [16:06] :D [16:07] huh, and sorry [16:08] ok, so [16:08] i made some comments on the pad already [16:08] yep - I added one [16:09] re: that comment [16:09] i think it would be generally a good idea that the "history" page was a blank "search page" when opened [16:09] yep [16:09] so *no* default loading from the database [16:10] then you could also use non-default filters [16:10] example: [16:10] i usually filter out everything else then xubuntu, but i might want to search for xubuntu and studio [16:11] another question [16:11] i guess elfy might be able to answer this... [16:11] indeed - I'd generally be wanting say Xubuntu, this month, arch [16:11] what's the difference between the "defect summary" and the bug list(s) in the history? [16:12] s/arch/testsuite/ [16:12] IF ONLY that site was running with some code i understand.. [16:12] :) [16:13] defects summary includes everything that is currently testable - precise/trusty/utopic [16:13] right [16:14] ah [16:14] so the bug lists in the history is a partial grep of the defects summary? [16:14] with the information about which *builds* the bugs are filed against [16:15] hang on - which history are you talking about here ? [16:15] lol [16:15] defects summary: http://iso.qa.ubuntu.com/qatracker/reports/defects [16:15] history: "see removed and superseded builds too" [16:15] right [16:15] yea - as I said :) [16:15] yep [16:16] because i'm sure showing the bug lists on that view slows it down by far [16:16] just don't know where you are getting the history bug list [16:16] the history shows the bug lists per build [16:16] "lists"... [16:16] the bug icons [16:17] ok - I thought there was a list I'd never found [16:17] :) [16:17] nope [16:17] right so - difference is as I said - for sure now :p [16:17] do you think we *need* the bug icons for each build in the history? [16:18] well I use them [16:18] right [16:18] not as often as I would if it didn't take a week to load though :p [16:18] yep [16:18] I'd refer back to last beta at the next one for instance [16:18] i dislike the bug icon lists generally... [16:19] i would very happily remove them and even replace with something else [16:19] same [16:19] but on the history page... i don't know what would be a sane choice [16:19] well - it's useful to see the number of critical bugs against a particular bug - and it's quick to scan red icons [16:20] s/particular build [16:21] well, on pages where you don't actually need to read the bugs I can see value [16:21] even then it could be *one* icon that opens a tooltip with a list of bugs [16:21] in some tabular form [16:21] the majority of the time mouseover bug is sufficient to trigger memory [16:22] and the majority of issues anyone is likely to have will go if you know you're only seeing things you want to - eg xubuntu for us [16:22] mmh. [16:24] actually [16:24] yes? :) [16:24] if defects summary could be filtered then you'd not need so much on the history imo [16:24] * pleia2 nods [16:24] yep. [16:24] exactly [16:24] i'd rather see a list of all bugs [16:25] then a column that tells how many builds it affects [16:25] I go to history preferentially - because of that [16:25] that sounds like changing the db structure or doing expensive queries though [16:25] defect summary is a pain unless you've got some idea of bug desc or package [16:26] so [16:26] maybe we need to file a bug against the defects summary page instead :) [16:26] I was looking for one the other day - didn't find it until I'd found the thing elsewhere and new the number [16:26] yep [16:27] actually, i'd really like all of the bug lists to be like that [16:27] even in the testcase pages [16:27] that's SO much better than the bug icons [16:27] and since all the data is loaded and output ANYWAY, it doesn't really make sense to hide the data [16:27] http://iso.qa.ubuntu.com/qatracker/milestones/315/builds/78216/testcases/1303/results [16:28] yep. [16:28] so how would you deal with the bugs listed there on the testcase page [16:28] just list them the same way as in the defects summary [16:28] necessarily if it isn't an icon you're going to need to go elsewhere [16:28] unless [16:29] and i would make the columns sortable. [16:29] maybe i need to do a PoC [16:29] if there was a way for the tracker to recognise that I was on xubuntu testcase and aren't interested in kylin bugs [16:29] knome: ++ [16:29] elfy, though you might [16:30] mmm [16:30] i guess the OPTIMAL situation was [16:30] only show bugs that are reported against the current product [16:30] and then a link that says "Show all bugs" [16:30] I can just see a page with bugs listed - even if you could sort them - going to be a long list and long page [16:30] that asynchronosly loaded the rest [16:30] elfy, to me, that's better than the bugs list now [16:31] and as i proposed in the pad [16:31] there should be a button to add to the critical bugs/bugs list [16:31] so you could practically go through the list [16:31] yeah [16:31] and clickety-click [16:31] right now it's very awkward x_x [16:31] that would work it seems [16:32] * knome checks the tracker code [16:33] pleia2: if you don't know the bug numbers and are dipping in and out - which the majority of people do - I would agree [16:34] even if you know the bug numbers, I don't want to type it :) [16:35] well I don't clear stuff on this browser - so I tend to have groups of bug numbers in there - and I just start typing and bob IS my uncle - there is the group of bugs I need to report again ;) [16:35] you are a testing machine [16:36] not so much this cycle [16:36] anyway, yeah, a newcomer won't have that, and I didn't so much [16:36] yep [16:36] a *list* on the tracker page would work better [16:37] hrr hrr. [16:37] a list, then you click on the + button to add it to the bugs list [16:37] filtering on defect summary would be awesome - more awesomer than history - but history still needs it [16:38] so a new bug for the defect summary so far [16:39] and we probably need a new bug for the testcase pages as well [16:40] to use the bug table instead of the bug icons [16:41] I mean ... [16:42] defect summary has bugs for Precise Alpha 1 on it ... [16:42] yes [16:42] and one of those goes back to natty lol [16:43] :P [16:45] hah [16:45] defects summary - small issue - but what do the column title mean [16:47] I guess com is comments, sub is subscribed, dup duplicates [16:47] yes [16:47] wouldn't bug heat be more useful than knowing who many comments there were [16:47] yes [16:48] or simply the status [16:48] and what use is dupes if there's nothing to say which dupes [16:48] well, you can go to LP and look [16:48] dupe adds heat anyway [16:48] yes [16:48] as does subscribers [16:48] i agree showing heat would be better than showing those columns [16:49] same with the bug tooltips [16:50] I'm happy to do the bugs for this - but for defect summary - 1 bug with a list? seperate bugs for each issue? [16:51] i'd say just one bug is enough [16:51] once you've filed the bugs, i can comment/edit the descriptions :) [16:51] lol [16:51] i mean, to fill in details [16:52] ha ha ha [16:54] does that cover defects summary and testcase report [16:56] hopefully [16:56] what else? [16:57] not thinking of anything else [16:57] I think the etherpad pretty well describes the issues I've been having [16:57] ok [16:58] separately, would be nice to add some bug reporting tips to some of our testcases [16:58] we can do that though :) [16:59] most new people will have no idea what ubiquity is, for instance [16:59] so adding some tips around installer instructions with "if you find a bug here, submit bug against ubiquity" [16:59] I still find the bug reporting to be the hardest part of the process :\ [17:00] pleia2: so do I ;) [17:01] * pleia2 just comes in here and asks [17:01] :) [17:01] though tbh my pet hate are people who mark an install testcase as failed because they've got an issue with a package somewhere [17:01] well, to be fair, there isn't great documentation about what passed/failed means afaik [17:02] maybe some info about that in the tracker too! [17:02] pleia2: so a bit of expansion on problems encountered ... list? [17:02] well, more like an info clicky thing on each of the fields in the tracekr [17:03] I know there's a bug out there for "Hardware profile" [17:03] https://bugs.launchpad.net/ubuntu-qa-website/+bug/1017207 [17:03] Launchpad bug 1017207 in Ubuntu QA Website "Clarify what a "URL to the hardware profile" is in tracker" [Wishlist,Triaged] [17:03] so pretty much that for all of them [17:03] pleia2: saw that this morning when I was looking at the list - I never ever use that thing [17:04] exactly [17:04] officially - if something doesn't do EXACTLY as the testcase says it should be a fail [17:05] sure, *I* know that :) [17:05] any lubuntu/xubuntu/ubuntu test at the moment should be a Fail as they all have the cangraphical-=no issue :) [17:05] indeed [17:05] if you do it via vbox at least [17:06] is there a writeup anywhere about what these fields mean? [17:06] hard to know what to write - people have failed installs because the box with the writing goes full screen width [17:06] or should we write them and voluntell knome to make a patch to link to descriptions [17:06] ochosi: indeed, we should test it out and see if there are any glaring issues [17:07] (or if it doesn't seem important, ok, but it can be tricky to know what each field means for new folks and this seems like an easy-ish one to fix) [17:07] pleia2: I'm not even sure how to go about it - I'd pass for things other people would fail critically [17:07] yeah, that seems like a problem [17:08] and then is the fail because it's a fail, or because the testcase is not quite right [17:09] pleia2, aha :) [17:09] knome: <3 [17:10] pleia2, any idea what " URL: depends on the underlying entry " means on the LP api? [17:10] how do i figure out the URL? [17:10] lp api lol [17:10] so no, not so much [17:10] its error messages always confound me [17:13] knome: so, think you can draw me some pretty pictures to show balloons this week re: defects/reports [17:14] no idea [17:14] haha [17:14] when do you meet him? [17:15] we're doing a presentation together on Thursday at Ubucon, but I'm sure I'll be seeing him Thurs-Saturday [17:15] haven't firmed up a time to chat QA yet [17:15] oh [17:15] then probably [17:15] but... no hard promises [17:15] ok [17:15] I'll do my best to describe if I have no visual aids :) [17:19] alright, if we're done here it's time for me to go out for a run [17:19] have fun pleia2 - thanks :) [17:20] thanks :) [17:23] * knome facepalms [17:23] knome: go for your life bug 1366579 [17:23] bug 1366579 in Ubuntu QA Website "Defects Summary enhancements" [Undecided,New] https://launchpad.net/bugs/1366579 [17:24] lol [17:29] ripped the testcase page stuff from the pad :) [17:31] bug 1366581 [17:31] bug 1366581 in Ubuntu QA Website "Testcase Report page enhancements" [Undecided,New] https://launchpad.net/bugs/1366581 [17:31] biab [17:48] https://api.launchpad.net/1.0/ubuntu?ws.op=searchTasks&tags=[%22iso-testing%22,%22trusty%22]&tags_combinator=All&importance=Critical [17:48] json for all critical bugs filed against trusty and reported in the iso tracker [17:49] doesn't take long to grep that list [17:49] if we only had tags for products and builds, we could create our own lists [17:49] builds would be overkill, granted... [17:50] but product would be good [18:26] bluesabre: you didn't add a comment to bug 1357090 yet, are you maybe confused by the comments like I am? this whole report is just meh [18:26] bug 1357090 in xfce4-power-manager (Ubuntu) "Black screen on resume in Xubuntu 14.04.1" [High,Confirmed] https://launchpad.net/bugs/1357090 [18:29] black screen on lid close.. black screen on logout.. :D