=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 17 Sep 17:00: QA Team | 18 Sep 00:30: ubuntu-pa LoCo Team | 18 Sep 12:00: Ubuntu Mobile Team | 18 Sep 13:00: Desktop Team | 18 Sep 14:00: Ubuntu Java | 19 Sep 04:00: MOTU Team === ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 18 Sep 00:30: ubuntu-pa LoCo Team | 18 Sep 12:00: Ubuntu Mobile Team | 18 Sep 13:00: Desktop Team | 18 Sep 14:00: Ubuntu Java | 19 Sep 04:00: MOTU Team | 19 Sep 22:00: Platform Team === bazhang is now known as bad_citizen === bad_citizen is now known as bazhang === asac_ is now known as asac === davmor2 is now known as davmor2_dinner === davmor2_dinner is now known as davmor2 === chuck__ is now known as zul [15:59] hello [16:00] Greetings all. [16:00] evening [16:00] * TheMuso is sitting up in bed attending the meeting, so he can drop straight to sleep afterwards. :) [16:01] hi [16:01] * slangasek waves [16:01] * evand watches TheMuso nod off ;) [16:01] hola [16:02] evand: I am sitting up to make sure I don't nod off. [16:02] Now if I didn't care, I would lie down. :p [16:02] heh [16:04] hi, sorry I apparently got disconnected at the most inconvenient time possible [16:04] * cjwatson pokes the still-lying topic [16:06] ArneGoetje,asac,bryce,evand,james_w,liw,TheMuso,slangasek: ping? (I only saw calc saying he was here before I dropped off) [16:06] doko is in hospital for scheduled surgery [16:06] cjwatson, plingelingelingeplong [16:06] cjwatson: pong [16:06] I'm here. [16:07] hi all, sorry I'm late [16:07] cjwatson: hi [16:07] yo [16:08] hi [16:09] * TheMuso is glad its not a very cold night in his neck of the woods. [16:09] perhaps somebody local could phone bryce and wake him up [16:10] anyway, let's get started [16:10] outstanding actions [16:10] Chris to upload openoffice.org3 to the ~openoffice-pkgs PPA without Sun branding (pending an agreement) [16:10] (calling bryce) [16:10] we have an agreement now, Chris said he was in progress; ETA? [16:10] cjwatson: not done yet, but working on it [16:10] (delayed by Hurricane Ike) [16:11] cjwatson: it appears i can upload now with the branding as of last email? [16:11] yes [16:11] ok [16:12] i'm clearing up enough space to try to do both the 2.4.1 and 3.0 builds on my laptop [16:12] morning [16:12] having to nuke a bunch of test vm's etc [16:12] morning bryce [16:12] hi bryce [16:13] calc: so this week? [16:13] cjwatson: should be done by next meeting, yes [16:13] * calc hopes to be back home in a couple days as well [16:14] ok, thanks, please let me know of any delay; I would recommend *not* rebasing on rc2 (if released in the interim) until you have rc1 out [16:14] next week being beta freeze i'm going to try really hard to get both done [16:15] ok [16:15] # Alexander to write mobile broadband MIRs [16:15] we need to get at least one or two other people MIR review powahs; in the meantime since pitti is away I guess I will arrogate that to myself and seek forgiveness rather than permission [16:15] cjwatson: yes. its pending. its what i am currently doing in parallel to firefox sec updates [16:16] cjwatson: how long will pitti be gone? this week? [16:17] he's at the Linux Plumbers' Conference in Portland; I think he's back on Monday [16:17] ok. Ill give you the MIR then as soon as I have it. so we can directly proceed after alpha-6 is out [16:17] thanks [16:17] cjwatson: actually its not a hard runtime dependency as its now [16:17] I'll carry both those items over then [16:17] just build-time and then dynamically loaded [16:18] aye, but we want it anyway, right? [16:18] but it has to get into main anyway, so i dont think that matters [16:18] cjwatson: yes. most likely we want that on CD [16:18] btw, anyone who has 3g can already pre-test it by using the network-manager team PPA [16:19] I have been instructed :-) to get a new phone before release week, since I'm intending to be in London and it's not impossible I might have to get home at short notice [16:19] so next time I get a chance to go into town I'll arrange for 3G stuff [16:19] asac: is the modeswitch stuff implemented already? [16:19] ok, items from activity reports [16:20] ArneGoetje: i talked to a few guys and from what i understood the modeswitch should be done by kernel team. i sent rtg a mail to sync up on outstanding wifi/3g issues [16:21] doko raised a problem with OpenJDK's compiler targetting Java 1.6 bytecode right now, which breaks older VMs; but he isn't here to discuss it so we'll have to skip that [16:21] asac: ok, thanks. please keep me posted. :) [16:21] ArneGoetje: i updated the bug yesterday ... didnt i? [16:21] at least i asked rtg in there for input [16:22] TheMuso: you mentioned that we might end up sticking with PulseAudio 0.9.10 for intrepid. What are the consequences of that? I understood earlier that we needed >=0.9.11 to match current ALSA [16:22] asac: I just saw you modifying the bug title, that's all [16:22] TheMuso: also on your activity report, have you had positive test feedback on dmraid so far? I nudged a few of the old d-i bug reports about it [16:22] really glad to hear that Debian are keen to take that [16:23] cjwatson: We don't need 0.9.11 to match current alsa at all. If we were to use libcanbbera's pulseaudio output support for event sounds in GNOME, we would need 0.9.11 or later, but its not imperative. [16:23] oh, that was it, event sounds. how are we going to fix those then? [16:24] cjwatson: The only real issue with 0.9.10 is settling on a good set of values to make sure pulseaudio performs ok with different applications, other than gstreamer/native pulse applications, as there is a push to send all alsa applications through pulseaudio when running pulseaudio and GNOME. [16:24] (I know you said we needed a new sound theme) [16:25] cjwatson: re dmraid, not many d-i people in debian can test, although they are using my empty disks for qemu etc to help with testing. My changes have been committed to svn, with a few improvements. I need to build these improvements and merge them into our packages and test, as they fix a few minor things in partman-base. [16:26] cjwatson: With event sounds, GNOME 2.24 uses a library called libcanberra, which is providing much flexibility wth sound events, including the ability to use ogg files. [16:26] The sound events scheme is similar to the xdg icon naming specification. [16:27] So I need to modify ubuntu-sounds to contain ogg files, as well as the metadata to make libcanberra happy to play events etc, as well as make a few changes in a few GNOME libraries to make sure libcanberra works as it should. [16:27] Still testing all of this, but should have it ready in a few days. [16:27] what backend would libcanberra end up using? just plain alsa? [16:27] cjwatson: Alsa, which would be directed through pulse when pulseaudio is running. [16:27] oh, I see, so just indirect [16:28] liw: any feedback on system-cleaner so far? [16:28] cjwatson, no feedback so far [16:28] cjwatson: Yes, and assuming we ship 0.9.12 or greater in jaunty, libcanberra can then use pulse directly, which will give us positioned sounds. [16:28] liw: you don't appear to be subscribed to its bugmail ... [16:28] oh, oops [16:28] (https://bugs.launchpad.net/ubuntu/+source/system-cleaner/+subscribe) [16:29] * liw forgot Ubuntu is different [16:29] haha [16:29] there's two bugs for you at least [16:30] yup, I'll get to those asap [16:31] ok, I can't see any other meeting-relevant items in activity reports, shout if I'm missing something [16:31] the one remaining milestoned bug for alpha-6 is bug 267682; are you guys still shooting to get that sorted out for alpha-6? if it's truly a kernel bug that sounds ... challenging [16:32] Launchpad bug 267682 in linux "Hotkeys no longer working in Intrepid on Thinkpads" [Critical,Triaged] https://launchpad.net/bugs/267682 [16:32] yeah I've still be looking at that [16:32] according to recent comments it's an acpi-support issue [16:33] Steve makes a good point that the kernel was that way in hardy as well, unless there's something we're all missing [16:33] if the latest comments are correct (and in digging in a little, I believe them), the kernel stopped accepting acpi-fakekey events for keys higher than some number, which I gather includes the hotkeys [16:33] so this doesn't entirely make sense [16:34] though I don't see the harm in trying a test kernel on sample hardware to try to rule it out [16:34] yeah [16:34] well, registername just sent another follow-up indicating he really thinks the problem is present in hardy too, so he's definitely talking about a separate bug [16:35] if someone could roll a test kernel I might squeeze in a reboot today, but I suspect this is a red herring [16:35] slangasek: ah okay. In looking through acpi-support I spotted quite a few "hotkeys don't work" bug reports. So either there's a fundamental pervasive problem that's been around for a year or two, or there's a number of bugs that have similar symptoms but different causes [16:36] the latter is always a possibility with a package that hasn't been tended to all that well of late [16:36] perhaps both - but mdz was explicit that this was a regression against hardy for him :) [16:36] slangasek: how do you think we should go about investigating this further? Grab a kernel guy? Or is there someone who knows acpi-support well? [16:37] sladen is the only one I'm aware of that knows acpi-support well, but I've had difficulty getting any answer from him about it besides "set it on fire and kick it overboard" [16:37] lol [16:38] hmm [16:38] anyway, I think the bug is going to end up having to be deferred for obvious reasons, but we should still keep chipping at it [16:38] I can talk to timo again about it === pochu_ is now known as pochu [16:39] I also have hotkey problems on my laptop, although I don't know that it's the same bug, but I can keep poking at that, just in case [16:39] ultimately, I think somebody on this team is going to have to figure out how the hell acpi-support and pm-utils works, since we keep getting asked about it :) [16:39] and then teach a few others? [16:39] cjwatson: am I correct in understanding that acpi-support is a ubuntu-specific package? [16:40] cjwatson: I would like to have this on the agenda for UDS Jaunty [16:40] bryce, Debian has it [16:40] bryce: it originated in Ubuntu [16:40] it was the Thom and Matthew show [16:41] slangasek: sounds good [16:41] ah okay [16:41] anyway, I /really/ don't see how acpi-support's presence can be to /blame/ for these keys not working since acpid should AFAIK still echo the events to its socket [16:41] so if something else wants the events, should pick it up that way [16:41] so then should we ask tim gardner to take a look from the kernel side? [16:42] definitely, once he digs himself out from under Dell [16:42] cjwatson: or is there a better kernel guy to talk to? [16:42] ask pgraner [16:42] ok will do [16:42] (tell him I sent you) [16:43] on UDS, I should note that I have scheduled paternity leave over UDS; I don't think it's going to be feasible for me to be about 12 hours by plane and train away at that stage in the pregnancy (or infancy) [16:43] cjwatson: do we have a fall back for wifi on the kernel team? [16:43] cjwatson: congrats :-) [16:43] asac: I'm not certain, ask pgraner :0 [16:43] :) [16:43] hehe ok [16:43] so this means that either my replacement manager will have started by then and can run the show, or else somebody else is going to have to sub as best they can [16:44] I'm holding out for the former at the moment [16:44] "holding out" = "assuming"? [16:44] anyway, I'll still be involved in planning either way [16:44] liw: = hoping [16:45] we have a shortlisted candidate so the chances look reasonable [16:45] just checking, my English often fails [16:48] sponsorship queue: thank you to several of you for putting this in your reports; I'll not spend time going over it now since the queue is getting very noticeably shorter [16:48] finally, I feel like the last week has been doom and gloom (thanks particularly to asac for putting up with lots of Mozilla-related flak). Anyone have any good news they want to share? :-) [16:49] hmm, been testing a lot of hardware lately, and with the .27 kernel and latest X bits, a lot of issues notably disappeared [16:50] good news: none of my hardware has physically broken this week [16:50] Myself and Jordi from Debian are merging Ubuntu alsa bits back into debian, to reduce the delta there. With luck, we can make at least some alsa packages syncs for jaunt. [16:50] jaunty [16:51] And I finally feel I am getting a handle on audio stuff for Ubuntu, and dealing with upstream. Just got to sort out the kernel side for hardware enablement, but I don't think that will be much of a problem, and, I am getting to like git... [16:52] If that could be considered good news... :p [16:52] heresy! [16:52] ;) [16:53] I'm getting to like git fast-export | bzr fast-import -, if that's close enough? :-) [16:53] heh [16:53] (that's how I'm maintaining ubuntu-policy) [16:54] the good news from my area is that they are now down to 33% outage in my zip code (61% for houston area overall) :) [16:54] * TheMuso counts the numer of upstream projects tat he tracks that use git... Hrm most of them, if you include their subcomponents. [16:55] oh, I suppose I have one: if you're interested in content that the BBC (the UK's government-funded broadcaster) puts out, there is now a chunk of current/archived content available for free via a totem plugin [16:55] I saw the changelogs for that. [16:55] Sounds nice. [16:55] edit -> preferences -> plugins and enable the BBC plugin, then click on the Playlist dropdown and select BBC, if you want to try it out [16:55] Top Gear? [16:55] most of it's audio-only so far [16:55] ah, rats [16:55] wow [16:55] no Top Gear AFAICS right now, although my stepson asked me about that too ;-) [16:55] cjwatson, for everyone or only UK residents who have paid their TV license? [16:55] liw: different feeds depending on geoip [16:55] Pirate Bay it is [16:56] it's still running off a staging server and hasn't had anywhere near all the content fleshed out yet [16:56] google has some of the topgear episodes, not sure if they keep it up to date though [16:56] but should be pretty cool once that happens [16:56] There were aso some good music/audio entries for the free culture showcase. [16:57] anyway, that's all I have; any other business? [16:57] I was fortunate enough to be on the selection panel, and was impressed with what I saw. [16:57] s/saw/heard/ [16:57] Fosscamp: any list out yet who is going/approved? [16:57] What's our policy regarding packages coming from Debian where the maintainer decided to not use a patch system (eject)? [16:58] evand: I thought it was to patch the package the same way? [16:58] ArneGoetje: oh, not so far, I should do something about that [16:58] evand: what TheMuso said, just apply the patch directly [16:58] TheMuso: I figured, but I wanted to be sure before I uploaded. [16:58] ok, noted [17:00] I think we're done, then [17:00] thanks all, will do minutes tomorrow morning [17:00] thanks... good night [17:00] thanks [17:00] thank you [17:01] Thanks, and good night. [17:01] thanks [17:02] thanks [17:02] * slangasek waves, thanks [17:57] hello everybody! [17:57] hey! [17:59] hello everybody [18:00] hi [18:00] * mvo waves [18:00] hey [18:00] hi all :-) [18:00] howdy [18:01] ogasawara, schwuk: ping [18:02] heno: pong [18:02] I believe ogasawara is at the LPC today [18:03] right, she may not be able to attend [18:03] the first agenda item is her's [18:03] hey ogasawara :) [18:03] #startmeeting [18:04] just in time then [18:04] hm, I though the bot was fixed :( [18:04] [TOPIC] Automated bug replies [18:04] Has anyone worked on a meta-can-text? [18:05] I think a note saying the reply is scripted would be good [18:05] Do you mean a message to include in automated replies? [18:06] that hasn't been written yet - I'd like to get ideas about what we should try to include when we do send these automated replies [18:06] like heno mentioned - clearly stating this is an automated reply [18:06] if the bug is closed in the process it should probably be suggested it be reopened for a human to read any replies [18:07] beyond that, I don't know if we can predict the likelihood of a response [18:07] the one issue I wonder about is if the automated reply will be ignored if the reporter knows it wasn't coming from a "real" person [18:07] (I should mention that the agenda is at https://wiki.ubuntu.com/QATeam/Meetings) [18:07] so I think it would also be good to explain how replies to automated posts will be handled [18:08] agreed [18:08] It might help to have it as a footnote to the message too [18:08] some people may even filter on a fragment of the canned text :) [18:09] I'll try to write something up in a wiki and send it to the ml [18:10] ok, thanks [18:10] we can take it from there [18:10] Topic: Getting QATeam/ReleaseReports in shape for the next release meeting [18:11] see https://wiki.ubuntu.com/QATeam/ReleaseReports [18:11] sbeattie made a landing page for this [18:12] I've separated out individual report pages [18:12] when is the next release meeting? 26 or 29? [18:12] 26 is Friday [18:12] we have some regression candidate bugs we should look at and also the list sent to the ml by nullack [18:12] so I guess is 26th [18:12] ok so maybe there's a typo there at https://wiki.ubuntu.com/QATeam/ReleaseReports/20080926 ? [18:13] looks like it. [18:13] wery possibly :) [18:13] alright [18:13] fridge agrees on the 26th: http://fridge.ubuntu.com/node/1621 [18:14] heno: do you mind if I <> the upcoming report in that landing page? [18:14] akin to having the current agenda show up on the qa meeting page? [18:15] sbeattie: will that be confusing in that you can't edit it there? perhaps add a comment in the wiki source as well to clarify [18:15] but, yeah sure [18:16] bdmurray, pedro_, ogasawara: could you look at the bugs nullack suggested for this list? [18:17] heno: sure [18:17] yep no problem [18:17] heno: sure [18:18] slangasek: I know there was a discussion about this in #u-bugs earlier - would you prefer we milestone/nominate these in-our-view-hot-bugs before the meeting or just bring a wiki page with candidates to the meeting [18:20] heno: last week slangasek and I talked a bit about the problems with nominations - specifically that a denied nomination can't be renominated [18:20] right [18:21] sorry, I'm late. [18:21] bdmurray: what was the conclusion? [18:21] * heno waves to stgraber [18:22] heno: not nominating due to the amount of noise there [18:22] ok [18:23] and only a few of us have the power to milestone, right? [18:23] heno: actually it's all of bug control [18:23] fewer people have the ability to deal with nominations [18:23] so an internal discussion in the QA team before the meeting seems appropriate [18:24] yes, I remember you've pointed out that to be a bit backwards [18:24] right [18:25] slangasek may be afk - let's talk about regressions: [18:25] they should also be considered for that list [18:26] sbeattie has made a lovely overview page: http://people.ubuntu.com/~sbeattie/regression_tracker.html [18:27] many of them have unknown importance etc though - how should we triage these? [18:28] should we do a weekly pass over them? make it a topic of this meeting? [18:28] bdmurray: thoughts? [18:28] "regression potential"? what's that? [18:28] could it be a candidate for a hug day? regression bugs [18:28] there sure are a lot of new ones on there === chuck__ is now known as zul [18:29] I mean, how are potential regressions evaluated as such? [18:29] cr3: https://wiki.ubuntu.com/QATeam/RegressionTracking [18:29] sbeattie: you're not listing the ones without a package at your page right? [18:29] pedro_: hrm, I suspect not. [18:29] sbeattie: perhaps your page should link to the explanation [18:29] ara: i'd say no, there's not a lot for hug day IMHO [18:30] heno: yeah, agreed [18:30] pedro_, ara: I also think we need to look more often than that [18:30] sbeattie: where does release come from? [18:30] heno: yup [18:31] turaround time is important as we near release [18:31] bdmurray: whether it's been nominated for that release. [18:31] sbeattie: nominated and not approved? or an approved nomination? [18:32] sbeattie: can we get this on qa.u.c and ogasawara, can we in turn parse it and add the regression count on each package page? [18:32] bdmurray: I *think* approved nominations; that is, it would show up on https://bugs.launchpad.net/ubuntu/[release]/+bugs [18:32] heno: I'll need to take a closer look at the parsing but it should be easy enough to add to the pkg stat pages [18:33] heno: yes, and I can have it emit something more parseable than html. [18:34] Could we split it up btwn milestoned and not milestoned and also by importance? [18:34] ah, that would be good [18:35] bdmurray: sure. [18:35] is Wouter Stomp here? (what is his nick) [18:35] I think I tagged many of these [18:36] he, not I ! [18:36] sorry, stealing credit there :) [18:37] its too bad there is no record of who or when something was tagged [18:37] he did my ndiswrapper one [18:37] bdmurray: agreed! [18:38] Does anyone want to take ownership of the regression list, coordinating with others to get it triaged and added to the support list? [18:39] sbeattie? can you check with Wouter and nullack if they want to help you with that? [18:39] sure [18:39] great, thanks! [18:39] sbeattie: we might be able to check the mailing list for taggers and tag dates [18:39] s/might/should/ [18:40] we should probably look at the list briefly at each weekly meeting between now and release [18:40] bdmurray: yeah, was thinking the same thing. [18:40] that covers both the regression and reporting topics [18:41] Topic: Testing day preparations [18:41] ara: has just announced Monday's big testing day [18:42] ara: you're not on planet yet - do you have access to the QA blog? [18:42] guys, those with a blog, please, post about it :-) [18:42] this would be appropriate for that [18:42] heno: never tried [18:42] that too :) [18:42] stgraber: can you get ara set up? [18:43] sure [18:43] which list was it posted to? I must have missed it, I can blog it though [18:43] thanks [18:43] jcastro: ubuntu-qa [18:43] jcastro: ubuntu-qa i think [18:44] I'll be around to give advice on testing day - anyone else? [18:44] me too [18:44] count me in [18:44] I'm always around [18:45] it'll be in #ubuntu-testing correct? [18:45] cr3, schwuk: how about we run a session on how the auto install work is progressing? [18:45] bdmurray: yep [18:45] it's still very opaque to people [18:46] we are in the process of opening it up, it takes time [18:46] the kvm testing documentation is quite sparse too [18:46] ara: what's your Ubuntu QA username ? (ISO tracker or Brainstorm) [18:46] stgraber: areta [18:46] first, we have been working on adding installer testing which consists of checkbox-log packaged as a udeb which monitors the syslog for particular phases of the installation [18:46] we could run a session or two in a different chan (classroom or u-qa) [18:47] cr3: right, can you prepare a little session about it for Monday? [18:47] heno: here or as part of the testing day? [18:47] the checkbox-log is called from a daemon forked at early-command time which first reports that the machine has booted and then reports various phases [18:47] like the devel week or open week sessions [18:48] heno: sure, what's on Monday? [18:48] as part of testing day (sorry if that was unclear) [18:48] cr3: read scrollback :) [18:49] heno: installer testing will not be available for community though [18:49] getting people set up with the rsync script ahead of time might be a good idea. [18:50] ara: can you coordinate the timing of those? perhaps we can do one on SRU testing and one on desktop testing too [18:50] heno: sure [18:50] jcastro: it'll be alpha 6 testing though so I'm not certain rsync is necessary [18:50] ara: done, you should have access to the blog [18:50] cr3: right, I'm just asking for an overview presentation given on Monday [18:50] bdmurray: ok [18:50] jcastro: so running posts about how to get setup for testing day as well as publiscising it? [18:50] heno: will do [18:50] stgraber: thanks [18:51] cr3: It's quite informal - look at some examples logs from open week [18:51] ara: http://blog.qa.ubuntu.com/node/add/story [18:51] heno: is the idea to get people to sign up to the tracker if so it might be good if we could get a fresh batch of iso's listed for the monday [18:51] a short intro followed by Q&A [18:51] schwuk: well, the mirrors get slower as we get closer to release, if people want to start on monday and chip in when they can we can get them syncing the ISOs and registered on the tracker ahead of time [18:52] davmor2: we should list the Alpha 6 (released) images [18:52] we don't do that often, but the tracker can do that [18:52] I think it will be best then we get a fresh set of readings :) [18:53] would we get more duplicate bug reports though? [18:53] jcastro: I agree that it's important to show people how to be prepared [18:54] could we link to the alpha 6 caveats to avoid that? [18:54] not such a big deal for this testing day but for later milestones it's crucial [18:55] right, let's link to that on the testing day page [18:55] can we also make it easy for people to search for recently filed bugs somehow? [18:56] 'ubuquity bugs filed since sept 19th', say [18:56] maybe iso-testing tagged sorted by newest first in LP [18:56] I know bughelper can do that, should that be what we recommend? [18:57] bdmurray: many alpha 6 bugs may be reported by the general non-iso-testing public though [18:57] during the weekend, say [18:58] right, the bugnumbers query can be a bit slow but we could pregenerate a list for some packages I imagine [18:58] one more point relating to testing day: Tidying up the test documentation - what should we prioritise before the even and what is suitable for editing during it? [18:59] bdmurray: can you do that for top 10 packages, say? [18:59] ara: what's your view on the current state of the testing docs now? [19:00] heno: I think that the most important page, ISO/Procedures is quite clean. About what is suitable, I had proposed to clean and improve the test cases [19:00] heno: as explained in https://testcases.qa.ubuntu.com/Ubuntu/Applications [19:00] not all have had the pedro_/jcastro makeover :) [19:00] heno: yes [19:00] thanks! [19:01] I've started adding the screenshots which I can finish off once testing is out of the way [19:01] ara: ok, so the how-tos are in good shape IYO and well ask for help with the cases on the day? [19:01] thanks davmor2 [19:02] maybe we should focus on 1 type of testing like Live CD? [19:02] ara: temporarily I've not added the screenshot to it's holding page I'll wizz through those at the same time [19:03] davmor2: ok [19:03] bdmurray: good plan, we can always expand on the day if we need to [19:04] that gives us a better chance of getting a full test result matrix :) [19:04] let's wrap up [19:04] any other business? [19:05] Alpha 6 candidates need some testing love of course! [19:05] #endmeeting [19:05] thanks everyone! [19:05] thanks! [19:06] thanks! [19:06] ta [20:19] heno: I would prefer that, for bugs the QA team believes need to be on the radar, they be milestoned and targeted in advance [22:22] ping stgraber [22:46] nizarus: pong [22:47] sorry stgraber but is there any news about the next emea cuncil ? [22:47] IIRC it was rescheduled to this tomorrow [22:47] s/this// [22:49] the wiki page is not updated yet ! [22:49] 20:39PriceChildWe won't hold it today, but will put the new ate on our page and the fridge [22:49] 20:39 PriceChild: We won't hold it today, but will put the new ate on our page and the fridge [22:49] so that won't be tomorrow either, it'll be when we'll announce it :) [22:49] http://irclogs.ubuntu.com/2008/09/11/%23ubuntu-meeting.html [22:50]