[00:30] How goes the Xubuntu testing? [00:43] doesn't look too bad [00:46] knome, Great. Thanks for letting me know. [00:49] ftr, you could have checked that from the ISO tracker yourself :P [00:55] So about the same as this morning. :D [00:56] Unit193, hello darling. [00:57] I want to know abt how to access both please [00:57] azzenovic, you'll need a launchpad account [00:58] https://iso.qa.ubuntu.com/ lists Xubuntu, and links to bugs on there. [00:58] azzenovic, http://open.knome.fi/2014/02/23/logging-in-with-ubuntu-one/ for the detailed information on obtaining one [01:01] knome, I already have one what shall i do next ? [01:02] you can now login to the ISO tracker in the url Unit193 pasted [01:02] (Typed) [01:02] pastyped [01:02] typasted [01:04] done [01:05] do you need further information? [01:09] yeah indeed what's the next step ps I am currently installing willy iso [01:09] which ISO is that? beta1? daily? [01:11] the one in the daily-live directoy [01:12] ok... well we're currently testing the beta1 release, so that's a bit unideal. [01:12] zsync. [01:15] no prob I will go with beta [01:16] ok, then select "Wily Beta 1" from the milestone list [01:16] from that page, select "Xubuntu Desktop your_architecture" [01:16] and from THAT page, select the test you are willing to run [01:17] eg. for amd64 and entire disk install, you end up at http://iso.qa.ubuntu.com/qatracker/milestones/340/builds/100663/testcases/1300/results [01:17] that page has all the information on what steps you need to take to run through the test [01:17] (yes, it's basically a regular install, but it's good to run with that page open the first few times) [01:18] at the end of the page, you have a form to add a test result - do that when you are ready with the installation [01:20] ok thx :) [01:50] i'm off to bed [01:51] nihty [01:51] +g [07:13] flocculant, also, this is of course the right channel :P [07:13] flocculant, another thing: let's talk with lderan about what data we want to pull from the QA trackers [07:14] flocculant, he said he'd be willing to hack a bit on the xml-rpc interface so it would be a bit easier to get the data we need [07:14] ok [07:14] and if you didn't notice - there's now a timeline in the tracker [07:14] I did ;) [07:14] goodie [07:15] is it going to stay as it is though? [07:15] I did read you and ochosi - but didn't get any finished thoughts [07:15] i don't know yet [07:15] eg day or week or month [07:16] improvement ideas welcome :) [07:16] :) [07:16] it's hard to say whether day/week is better in the long run [07:16] since the data isn't naturally scattered now [07:16] I think that day would be a mightnare [07:16] yep, probably [07:17] it's easy enough to change later [07:17] and week would (in a cycle) be a possible 26 sections [07:17] how about biweekly [07:17] i don't know [07:18] how works within a biweekly schedule [07:18] knome: Source in git, btw? [07:18] Unit193, nah, i'll push it in cvs [07:18] Ah, even better. [07:19] ^ *who [07:19] i mean, it doesn't have a natural rhythm for me [07:19] one thing i considered was using week numbers relative to the cycle [07:19] knome: people that think that 26 is too many, 6 is too few and 190 is silly [07:20] so week 1 for the first week of cycle - whether that was in april or october [07:20] week numbers relative is probably a useful starting point [07:20] and if we are honest about it - week 1 - 8 or so would be pretty empty :D [07:20] mhm [07:21] then their headers wouldn't appear [07:21] same with date [07:21] +s [07:21] only ones that have content are listed [07:21] I don't see that as a problem [07:21] no, quite the opposite [07:23] i was just meaning that it would make the list not 26 sections :) [07:23] but say, 18 [07:24] yep [07:24] which is IMO quite ok [07:24] i'm fine with 30ish too [07:25] I guess as long as it lists from current to eons ago I guess it's not really an issue anyway [07:25] we currently have 81 items, so that split in 26 would mean >3 per week [07:25] well, ultimately it will still be a long list [07:25] of course [07:26] a list with 100 headers with one line each would be a pain to parse [07:26] sure [07:26] ok, another Q [07:26] so week at minimum imo [07:27] do you see a specific use case for this apart from the obvious "let's see how we've done" ? [07:27] let me ponder that in the kitchen ... [07:27] sure [07:30] to be blunt - no I don't [07:31] ok, so in that case - does it matter if the output is split into weeks? [07:31] one thing i can think of is the monthly team reports [07:31] I wouldn't be that interested in knowing that foo was done *then* all I'd really be interested in knowing is that it was [07:31] but then we didn't do those since april [07:32] and the whole system is falling apart - not many teams are doing them altogether [07:32] right [07:32] and finally, [07:32] if need be, i can simply add a dropdown for the different choices... [07:33] but let's not overcomplicate it if people are happy with one view :) [07:33] yea [07:33] one point here [07:33] sure [07:34] *if* the thing is how many rather than what - could the data not be added to the burndown? [07:34] then you could see at a glance all graphy things in one place [07:34] well, it is in the burndown essentially... [07:34] just look how many notches the green bar came down [07:34] or use the tooltips to figure that out [07:35] tooltips ... [07:35] hover over the bars [07:35] just found those :D [07:35] \o/ [07:36] from a personal pov - the timeline isn't likely to add much for mine, I'd be more likely to see what others were doing [07:37] but the timeline is useful anyway then, right? [07:37] for that - yes [07:37] one thing that i'm thinking is [07:37] if it was no use to me - I would say so :) [07:37] we don't currently list the work items sorted by status anywhere [07:38] i don't know if that's a problem [07:38] likely not [07:38] a new contributor likely knows which area they want to work in [07:38] yea [07:38] eg. either artwork or QA [07:38] but [07:38] I guess XPL *might* find that useful [07:38] maybe the timeline could have the current WIP work items at the top of the list [07:38] "these are up for completion next" [07:39] simon told me he was happy with the overview [07:39] basically, the overview and the details are very close to each other [07:39] in a way [07:39] it's just a different sort order [07:40] knome: perhaps timeline could have WIP/TODO/ done by week (or whatever chunks) [07:40] nah, that'd add complexity to the DB [07:40] ok :) [07:40] and "this was todo at week X" isn't useful IMO [07:40] oh - not what I meant [07:41] oh [07:41] right, i see what you mean [07:41] I mean - at the top - this stuff is being done, needs to be done - below the rest [07:41] but wouldn't that be beating the dead horse? :P [07:41] the details tab could handle that [07:42] ok - then I see no reason to include WIP either then [07:42] so in addition to being able to filter by assignee, enable filtering by specification or status [07:42] (see where i'm going? :P) [07:42] on detail tab? [07:42] yep [07:43] so we could see ALL the todo stuff if we wanted to? [07:43] that what you mean? [07:43] yes [07:43] or all the artwork stuff [07:43] (like in the overview tab currently...) [07:44] mmm [07:44] not sure about that much detail [07:44] eg my todo or your todo [07:44] team todo I'd be more likely to read [07:44] or team WIP etc [07:45] well [07:45] those are easy enough to get to now [07:45] not team todo [07:45] i mean it's not hard to see what my WIP list is [07:45] no? [07:45] http://tracker.xubuntu.org/#tab-details/xubuntu-qa [07:46] ha - so we're describing the same thing from either end [07:46] or http://tracker.xubuntu.org/#tab-details/flocculant+teams [07:46] I mean - there's no way to find out Xubuntu todo or Xubuntu wip [07:46] i mean the latter url can be infinitely useful [07:46] ah, right [07:46] sure [07:47] that might be more useful [07:47] yep [07:58] bluesabre: ping [08:09] do a couple of hardware tests and I think we're looking pretty good [08:16] biab [09:01] bluesabre: hey! just a quick status inquiry: xfpanel-switch is uploaded? how about the patch for xfce4-panel? [09:16] bluesabre, also if you didn't notice, i developed the timeline to lure you more into making progress to see the tracker changing! [09:21] :> [09:21] so, i finally figured out what i want to do with the overview tab [09:21] bumpy ride incoming [09:22] btw, still planning to integrate this in x.org right? [09:22] "in"? [09:22] well, in terms of making it look integrated there and not a separate page [09:23] well, as i said previously, i don't think the overall layouting stuff works for both [09:23] i'll probably look into making the headers more integrated looking at some point [09:23] i think having the header from x.org would be enough [09:23] but that requires changes in the website header too [09:23] yeah, something like that [09:23] you can always