[02:49] <Ddorda> where is this channel logged?
[02:49] <bazhang> !logs
[02:49] <Ddorda> thank you
[16:00] <cjwatson> hi
[16:00] <liw> hi
[16:00] <mvo> hi
[16:00] <cjwatson> hmm, no robbie?
[16:00] <james_w> hi
[16:01] <robbiew> hello
[16:01] <robbiew> sorry...processing emails
[16:01] <robbiew> #startmeeting
[16:01] <MootBot> Meeting started at 10:01. The chair is robbiew.
[16:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:02]  * slangasek waves
[16:02] <evand1> hi
[16:02]  * robbiew assumes everyone is here...accept al-maisan who's on holiday
[16:03]  * mvo is here
[16:03] <robbiew> [TOPIC] 8.04.3
[16:03] <MootBot> New Topic:  8.04.3
[16:03] <robbiew> the new, new release date is 07/16...right? :/
[16:04] <slangasek> yes
[16:05] <robbiew> slangasek: still no word from Desktop on bug 207072
[16:05] <slangasek> we have another kernel in -proposed now that wasn't expected; apparently a security upload had clobbered the previous one before we'd gotten it published to -updates
[16:05] <slangasek> :(
[16:05] <robbiew> double :(
[16:06] <slangasek> the kernel issue was a surprise, but shouldn't affect the timeline
[16:06] <robbiew> ok
[16:06] <cjwatson> do you need a d-i rebuild against the new kernel?
[16:07] <slangasek> cjwatson: I guess we should, to pick up the security fixes
[16:07] <mterry_> ahem, hi
[16:08] <cjwatson> slangasek: on its way
[16:08] <slangasek> thanks
[16:09] <robbiew> slangasek: should we just drop bug 207072, since I doubt we can get a tested fix in anytime soon
[16:09] <slangasek> robbiew: we /shouldn't/ drop it, given the consequences, but I don't see that we really have a choice at this point
[16:10] <robbiew> yeah
[16:10] <slangasek> if we are letting it slip 8.04.3, we at least need to have a game plan for getting it fixed soon after
[16:11] <cjwatson> how far has this one been escalated so far?
[16:11] <cjwatson> sorry, that's sort of code for "has somebody cleared slipping this bug with mdz?"
[16:11] <robbiew> heh
[16:11]  * robbiew notified via email...but he's catching up on that
[16:11] <robbiew> I have a call with him today
[16:11] <robbiew> and it will be on the agenda
[16:11] <robbiew> ;)
[16:12] <robbiew> slangasek: what was the other bug of concern?
[16:13]  * robbiew cannot recall
[16:13] <slangasek> robbiew: bug #236640
[16:13] <slangasek> I've uploaded a fix to karmic now, and will upload a hardy SRU today to address the remaining issues that Etienne has highlighted - and will prod for a quick testing turnaround
[16:13] <robbiew> ok, thanks
[16:14] <robbiew> ok..moving on
[16:15] <robbiew> [TOPIC] Karmic Alpha 3 Deliverables
[16:15] <MootBot> New Topic:  Karmic Alpha 3 Deliverables
[16:15] <robbiew> evand1: usb-creator for windows....still alpha 3, or should be push back?
[16:16] <evand1> I think Alpha 3 is still reasonable
[16:16] <robbiew> cool
[16:17] <robbiew> Keybuk: how's the i586 work progressing?  is that still on for alpha 3?
[16:17] <cjwatson> I haven't heard any progress updates on the rebuild since around the last call I had with IS; I have another one of those tomorrow and will bring it up
[16:18] <cjwatson> it's supposed to be done by now
[16:18] <Keybuk> robbiew: I've not heard any progress either
[16:18] <robbiew> hmm...okay
[16:18] <robbiew> will mark it "yellow" until I hear back on it
[16:19] <robbiew> mterry: the rsyslogd stuff is done, right?
[16:19] <mterry_> rsyslog is just waiting on MIR work, and then a seed change.  The actual code changes needed have been pushed.  Should be able to make it in time, pending MIR
[16:20] <cjwatson> have you been in touch with any of the MIR reviewers directly?
[16:20] <cjwatson> I think it'd be best to do that, to move things along
[16:20] <mterry_> kees assigned both MIR bugs to himself
[16:20] <mterry_> But I can poke him
[16:21] <mterry_> Oh, I should say pitti assigned them to kees.  :)
[16:22] <robbiew> heh...that does make a difference
[16:22] <robbiew> thanks
[16:22] <robbiew> mvo: AptURL policy...no actual code, right?
[16:22] <mvo> robbiew: some code in software-properties, but it should have all landed now
[16:23] <robbiew> ah...ok, great
[16:23]  * mvo needs to review the spec again to be sure
[16:23] <robbiew> heh
[16:23] <mvo> python-robustness may get delayed for alpha4
[16:23] <mvo> I need some input from doko for it
[16:24] <mvo> landscape should be ok from my side now too, its up to the landscape guys to test/use it now :)
[16:24] <robbiew> okay
[16:24] <robbiew> thanks
[16:25] <doko> mvo: I know ...
[16:25] <mvo> doko: no problem
[16:25] <robbiew> cjwatson: the server installer improvements is on track, correct?
[16:26] <robbiew> that was switched from Alpha 4 to 3...I think
[16:26] <cjwatson> online help is done modulo actual help text for things (we'll at least have extended partitioning help for alpha 3)
[16:26] <cjwatson> I'm in progress on the LVM/RAID stuff; a few roadblocks but I believe it's still basically on track
[16:27] <robbiew> cool...thnx
[16:28] <robbiew> [TOPIC] Sponsorship Queue
[16:28] <MootBot> New Topic:  Sponsorship Queue
[16:29]  * mvo did a bad job here last week and will make up for it this week
[16:29] <robbiew> eh..could be worse
[16:29] <robbiew> ;)
[16:30] <robbiew> as a team...we do okay
[16:30] <robbiew> nowhere near the machine-like progress of some of the Desktop team folks
[16:31] <robbiew> but...i think that's also related to what they work on
[16:31] <robbiew> cool...moving on
[16:31] <robbiew> [TOPIC] Good News
[16:31] <MootBot> New Topic:  Good News
[16:31]  * robbiew is running Karmic 64bit with grub2 and ext4
[16:31] <mterry_> heh
[16:31] <robbiew> and I'm still up :P
[16:32]  * robbiew also got his office in somewhat workable conditions...no more working from the dining room table 
[16:32]  * slangasek is running with kms on 2.6.31 and the worst of the damage is that my monitor is stretching my eyeballs
[16:33] <robbiew> lol
[16:34] <robbiew> [TOPIC] AOB
[16:34] <MootBot> New Topic:  AOB
[16:35] <robbiew> 5....
[16:35] <robbiew> 4....
[16:35]  * ScottK says thanks for the t-shirt
[16:35] <robbiew> heh
[16:35] <robbiew> np
[16:35] <robbiew> ;)
[16:35] <james_w> the new kernel in karmic is apparently better under I/O load
[16:35] <james_w> no more firefox freezes when building hopefully
[16:35]  * robbiew just realized that mterry needs a Foundations Team shirt
[16:35] <mterry_> Yes!
[16:36] <Keybuk> and some whiskey
[16:36] <robbiew> lol
[16:36] <mterry_> Gotta collect 'em all.  OEM and Foundations down...
[16:36] <robbiew> ours is WAY better ;)
[16:36]  * ScottK wants in on the whiskey ration
[16:36]  * mterry_ looks sadly at my empty whiskey bottle
[16:37] <robbiew> ok...the meeting has digressed
[16:37] <robbiew> #endmeeting
[16:37] <MootBot> Meeting finished at 10:37.
[16:37] <robbiew> lol
[16:37] <robbiew> thanks all
[16:37] <evand1> thanks
[16:37] <liw> thanks
[16:37] <mvo> thanks
[16:37] <doko> bye
[16:37] <ScottK> mvo: How's it looking for getting to the backports spec?
[16:37] <slangasek> thanks, all
[16:38] <mvo> ScottK: no progress on this, sorry
[16:39] <ScottK> mvo: OK.  Please just keep it in mind for your 'spare' time.
[17:58] <heno> hey everyone
[17:58] <bdmurray> hello
[17:59] <heno> fader: are you guys participating in the meeting or sprinting?
[18:02] <heno> various people are away today, at GCDS or sprinting
[18:02] <heno> but we can start
[18:02] <heno> #startmeeting
[18:02] <MootBot> Meeting started at 12:02. The chair is heno.
[18:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:03] <heno> agenda as always: https://wiki.ubuntu.com/QATeam/Meetings
[18:03] <heno> bdmurray: I added some items for you just now ;)
[18:03] <heno> pedro is not here, anyone want to comment on bug days?
[18:04] <heno> [TOPIC] UbuntuBugDay highlights -- ?
[18:04] <MootBot> New Topic:  UbuntuBugDay highlights -- ?
[18:05] <ogasawara> I have some highlights from yesterday's kernel bug day
[18:05] <heno> ok go!
[18:05] <ogasawara> overall stats can be seen at http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20090707.html
[18:06] <ogasawara> I'd again like to thank Andreas for helping out as well as a newcomer JFo
[18:07] <bdmurray> ogasawara: what do the up and down arrows mean?
[18:07] <ogasawara> bdmurray: deltas for rate of change
[18:07] <heno> it would be nice to have a measure of 'total bugs touched' as well
[18:08] <ogasawara> bdmurray: it was hard to see what bugs were getting touched so that tries to give a rough idea
[18:08] <heno> might not be 100% accurate of course
[18:09] <heno> thanks ogasawara
[18:09] <heno> [TOPIC] New bug control members! -- bdmurray
[18:09] <MootBot> New Topic:  New bug control members! -- bdmurray
[18:09] <heno> any this week?
[18:09] <bdmurray> No, we haven't seen any applications in a bit.
[18:10] <heno> hm, ok. summer effect I guess
[18:10] <heno> [TOPIC] Bug Squad meeting -- bdmurray
[18:10] <MootBot> New Topic:  Bug Squad meeting -- bdmurray
[18:10] <heno> anything to note for the wider QA meeting?
[18:10] <bdmurray> yesterday day we had the bug squad meeting and discussed preparing for the global jam with some triaging classes in #ubuntu-classroom
[18:11] <bdmurray> there was also some interest in the progress on the mentoring program
[18:11] <bdmurray> and some further discussion on how to go about increasing apport coverage
[18:12] <bdmurray> which is great!
[18:12] <heno> \o/
[18:12] <heno> bdmurray: are you doing a class on writing hooks at dev week?
[18:13] <heno> (or was that something else?)
[18:13] <bdmurray> Yes, I'll add myself to the schedule for that
[18:13] <heno> ok
[18:14] <heno> I've also spoken with Bjorn on the LP bugs team about the adoption spec
[18:14] <heno> they had some test failures from the new code but are working on that now
[18:14] <heno> he says we might see it this week
[18:15] <heno> (but no promises)
[18:15] <heno> [TOPIC] SRU Verifications -- sbeattie
[18:15] <MootBot> New Topic:  SRU Verifications -- sbeattie
[18:16] <sbeattie> Thanks to Alex Magaz, Damian Frick, Stu Redman, Miklos Juhasz, David M. Lee, Nizar Kerkeni, Michael B. Trausch, Jaume Sala, and bluishgreen for providing feeding on SRUs this week.
[18:16] <sbeattie> SRUs for 8.04.3 continue along.
[18:16] <heno> care and feeding of SRUs?
[18:16] <sbeattie> heno: ?
[18:16] <sbeattie> oh, sorry, feedback
[18:16] <bdmurray> heh
[18:17] <heno> right :)
[18:17] <heno> which brings us to ...
[18:17] <heno> [TOPIC] 8.04.3 status check -- heno
[18:17] <MootBot> New Topic:  8.04.3 status check -- heno
[18:18] <heno> what's the latest story on kernels and CD spins?
[18:18] <heno> sbeattie: what was decided yesterday?
[18:19] <sbeattie> new proposed kernels got accepted that include the last security update; but I don't think the corresponding debian-installer upload happened until this morning.
[18:20] <sbeattie> so isos with the new kernels need to be spun.
[18:20] <fader> sbeattie: 20090708.1 images are being tested in the certification environment at this very moment
[18:20] <sbeattie> fader: awesome!
[18:20] <fader> sbeattie: Do these contain the latest kernel?
[18:20] <sbeattie> I haven't looked yet.
[18:20] <fader> (sorry for showing up late; I'm sprinting at the moment)
[18:21] <fader> Okay, if new images show up we'll test those as well :)
[18:21] <heno> fader: that's good news but also a good question!
[18:21] <heno> cjwatson, slangasek: do you know?
[18:21] <sbeattie> fader: how long roughly is it taking for a round of automated testing to go through?
[18:22] <heno> do the latest CDs have the new kernel and installer?
[18:22] <fader> sbeattie: It takes around 30-45 minutes to make a full test run including reboots, installs, testing, etc.  Unfortunately, if a previous install failed there is a 2 hour timeout before the next image will be tested
[18:23] <fader> (This is a known issue and cr3 is planning to address this very soon)
[18:23] <sbeattie> fader: are we seeing any failures on 8.04.3?
[18:23] <heno> fader: most 8.04.3 runs I've seen the past few days have had 0 test results
[18:24] <fader> sbeattie: So far no.  Though I can't tell yet if there are machines that are failing on the install... I need to wait for all the results to come in to be able to see that
[18:24] <heno> is there a known (and fixed) issue?
[18:24] <fader> But everything that has returned results so far has passed
[18:25] <heno> ok, that's encouraging
[18:25] <fader> heno: There were two separate issues hitting us.  One was an issue where the PXE install image did not have the same kernel version as the install environment, which caused it to fail to install.
[18:26] <fader> heno: The other issue was that the certification server had a memory leak that caused it to miss its own check for new CD images and it removed the old one, leaving us with no image to install to test.
[18:26] <fader> Both of these have been addressed now, and test results are trickling in.
[18:26] <sbeattie> heh, oops.
[18:26] <sbeattie> fader: great, thanks!
[18:27] <heno> davmor2: are you around to help with some install testing as well?
[18:27] <fader> sbeattie: No worries :)  (The HTML report on the test results is still pending; sorry for the delay, but there were Real Issues as outlined above.)
[18:27] <heno> It's not listed on the tracker though
[18:28] <sbeattie> heno: right, I poked slangasek just before the meeting about when he wanted to start iso testing, but haven't heard back.
[18:29] <heno> ok, I guess we'll see over the next few hours
[18:29] <heno> any other business?
[18:30] <heno> thanks everyone!
[18:30] <heno> #endmeeting
[18:30] <MootBot> Meeting finished at 12:30.
[18:30] <sbeattie> thanks!
[18:30] <schwuk> thanks heno
[18:45] <slangasek> fader: new ISOs will have to be rolled today/tomorrow; I didn't remember to binary NEW the kernel upload until this morning, so it'll be a few hours before we have a d-i build matching the new kernel
[18:46] <fader> slangasek: Thanks for the info.  I'll keep an eye out for it and make sure we get some results for that image
[20:11] <boredandblogging> Joeb454: ping
[20:11] <boredandblogging> oops, wrong window