[12:57] <Extend> there is no scheduled meeting in the EMEA wiki page and i want to apply ofr Ubuntu membership
[13:05] <Eljugador> www.eljugador.net
[13:05] <Eljugador> www.eljugador.net
[13:05] <Eljugador> www.eljugador.net
[13:05] <Eljugador> :o)
[14:38] <apw> Extend, you are unlikley to find anyone here for that
[14:38] <apw> did you add yourself to the Wiki page, people who are able to help are most likely subscribed to the wiki updates
[14:38] <Extend> i already have a wiki , launchpad ..etc
[14:39] <Extend> i even signed the code of conduct
[16:02] <robbiew> hi all
[16:02] <liw> hi
[16:02] <mvo> hi
[16:02] <Keybuk> hi
[16:02] <TheMuso> Hi
[16:02] <cjwatson> afternoon
[16:02] <slangasek> morning
[16:02] <evand> hi
[16:03] <robbiew> #startmeeting
[16:03] <MootBot> Meeting started at 11:03. The chair is robbiew.
[16:03] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:03] <robbiew> With the Beta tomorrow...I guess I'd just like to open it up for any outstanding issues that people want to discuss
[16:04] <cjwatson> release notes
[16:04] <robbiew> perfect! as I had a question of where the draft is stored
[16:04] <cjwatson> slangasek: are we collecting these on JauntyJackalope/TechnicalOverview?
[16:05] <slangasek> yes
[16:05] <robbiew> ah
[16:05] <cjwatson> ok, the backlog of stuff to write up is on https://bugs.launchpad.net/ubuntu-release-notes/+bugs
[16:05] <slangasek> if you mean errata for the beta and feature highlights
[16:05] <cjwatson> mostly thinking of errata, but yes
[16:05] <slangasek> hmm
[16:06] <slangasek> I'm not sure how much of what's on ubuntu-release-notes currently is applicable to jaunty, though; there've been a number of random task openings and I haven't been triaging
[16:07] <cjwatson> right, didn't mean to say that everything there *definitely* needs a release note, but it probably all needs to be looked at
[16:08]  * slangasek nods
[16:09] <robbiew> james_w: welcome back!
[16:09] <robbiew> :)
[16:09] <james_w> thanks :-)
[16:10] <cjwatson> I hear that the true source package branches in LP are nearly ready to go
[16:10] <cjwatson> s/the //
[16:11] <cjwatson> slangasek: any cause for belief that we might need a respin?
[16:12] <cjwatson> test coverage is looking pretty good
[16:12] <Extend> any news about firefox 3.1 ?
[16:12] <slangasek> I haven't reviewed the tracker bugs from this morning; there's one additional failure on kubuntu that I haven't looked at, and mythbuntu might need some attention
[16:13] <Keybuk> we missed out on a readahead update
[16:13] <Keybuk> but that's not so important for a respin at this late stage
[16:13] <cjwatson> Extend: we're in the middle of a meeting for a team that does not deal with firefox; this channel is not the best place to ask anyway
[16:13] <cjwatson> Keybuk: did the notification called for in BetaProcess not happen?
[16:13] <Extend> cjwatson, what is the topics ?
[16:13] <cjwatson> Extend: foundations team weekly meeting
[16:13] <Keybuk> cjwatson: the notification happened
[16:14] <Keybuk> the rsync of the image is still only 99% complete
[16:14] <cjwatson> ah, that's unfortunate
[16:14] <Extend> cjwatson, i'm searching for my foundation team and waiting here
[16:14] <Keybuk> feel free to tell BT they suck and that I should have faster DSL
[16:14]  * mvo has a fix for fglrx->ati transition in bzr but its not on the CD
[16:14]  * mvo will release note that too
[16:14] <slangasek> Keybuk: ah, yuck
[16:15] <cjwatson> Keybuk: do you want that task to be assigned to somebody who can more reliably get the image in future, or do you think you'll be OK with it for final
[16:15] <cjwatson> ?
[16:16] <Keybuk> I'm happy to do it if you guys don't respin cds every 20s :p
[16:16] <robbiew> heh
[16:18] <robbiew> slangasek: on an unrelated note, randa has not forgotten about the DebConf stuff...she's just waiting to hear back on it
[16:18] <slangasek> heh, ok
[16:18] <cjwatson> slangasek: which one's the additional Kubuntu failure you haven't looked at - bug 348393?
[16:18] <slangasek> Keybuk: not something we can promise, at all though
[16:19] <slangasek> cjwatson: apparently a false alarm, http://iso.qa.ubuntu.com/qatracker/result/2467/52
[16:19] <cjwatson> Keybuk: I think if you can let us know with a good margin if you feel you aren't going to be able to do it, then somebody else who already has the image could
[16:19] <slangasek> which links to bug #348434
[16:20] <Keybuk> cjwatson: anyone can do it, just boot the live cd in vmware, install it, reboot with "profile", copy the /etc/readahead/boot into the package's debian/boot.list and sed out anything kernel-specific
[16:20] <cjwatson> slangasek: mm, that looks like a duff disk
[16:20] <cjwatson> Keybuk: yeah, that matches the instructions on the wiki I think
[16:20] <cjwatson> oh, except for "sed out anything kernel-specific"
[16:20] <cjwatson> could you update https://wiki.ubuntu.com/ReadaheadListUpdate with details?
[16:21] <cjwatson> maybe the readahead-list package should contain a script to ensure we do it consistently
[16:21] <slangasek> cjwatson: it's under virtualbox, could just be a 3d virtualization issue?
[16:21] <Keybuk> cjwatson: not sure how
[16:21] <cjwatson> slangasek: suspicious comments about squashfs errors
[16:21] <Keybuk> that script would be identical to sed -i '/$VER/d'
[16:21] <cjwatson> Keybuk: ok, just note it on the wiki then?
[16:21] <Keybuk> wiki updated
[16:23] <cjwatson> ta
[16:24] <cjwatson> robbiew: any bugs that mdz is paying attention to that we need to hit up? :)
[16:24] <robbiew> heh
[16:24] <robbiew>  https://bugs.edge.launchpad.net/ubuntu/jaunty/+source/linux/+bugs
[16:24] <robbiew> all of these :P
[16:25] <robbiew> but that's kernel
[16:25] <cjwatson> hah
[16:25] <robbiew> does anyone have bugs they want to raise?
[16:25] <robbiew> things I should now about...in case asked
[16:25] <slangasek> no, only bugs I want to smash
[16:26]  * liw raises the bug that breaks his hardware just before every release
[16:26]  * slangasek reassigns that bug to the 'fate' project
[16:26] <Keybuk> cjwatson: you mean you don't look keep a very careful eye on https://bugs.launchpad.net/ubuntu/+bugs?orderby=-importance&field.subscriber=mdz
[16:26] <Keybuk> I've had that bookmarked since I became a manager ;)
[16:26] <evand> https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+bug/325973 is annoying me to no end
[16:27] <robbiew> Keybuk: heh
[16:27] <Keybuk> robbiew: I think I suggested that one to rick; it's good to know what bugs mdz is likely to ask you about at some point in the future :p
[16:28] <robbiew> Keybuk: right, the problem is that you assume he subscribes to all bugs of "interest" ;)
[16:28] <slangasek> hmm, I see the number of jaunty-targeted bugs has ballooned since yesterday
[16:28] <slangasek> we were down to one page! <shakes fist>
[16:29] <robbiew> ok, well I suppose we can cut this meeting short...since I know there's no shortage of things folks could be doing :)
[16:30] <robbiew> any "Good News"?
[16:30] <james_w> cjwatson was correct, "source package branches" are almost available on launchpad
[16:30] <robbiew> woot!
[16:30] <james_w> the facility, not the branches yet
[16:30] <slangasek> "good news" - we're getting a bit more hotkey love in, making some backlight controls work for some sony laptops where it's never worked before
[16:31] <cjwatson> james_w: will we be able to move ~ubuntu-core-dev/foo/ubuntu to the new location reasonably easily?
[16:31] <james_w> yes
[16:31] <robbiew> slangasek: speaking of hotkey love...can we make a special call for testing those in the Beta Announcement or Release Notes...which ever is more appropriate/
[16:31] <robbiew> ?
[16:31] <james_w> though before doing that I would like to be sure that they are consistent with the rest of the packages
[16:32] <cjwatson> presumably the main problem is cases where it isn't a full-tree representation
[16:32] <james_w> exactly
[16:32] <slangasek> robbiew: yes, it's still on my todo list to write something up for the tech overview
[16:32] <james_w> tags is a secondary problem, but that I can fix up easily enough
[16:32] <robbiew> slangasek: cool, thnx
[16:33] <cjwatson> james_w: anyone using debcommit -r should be fine, at least
[16:33] <james_w> yes
[16:34] <robbiew> anything else?
[16:35] <robbiew> going once....
[16:35] <robbiew> twice....
[16:35] <robbiew> #endmeeting
[16:35] <MootBot> Meeting finished at 11:35.
[16:35] <robbiew> thanks all :)
[16:35] <liw> thanks
[16:35] <evand> thanks!
[16:35] <TheMuso> thanks
[16:35] <slangasek> thanks :)
[16:36] <mvo> thanks
[16:36] <james_w> thanks
[16:59] <davmor2> Hello Everybody
[16:59]  * ogasawara waves
[16:59] <pedro_> hello everybody
[17:00] <heno> hey all
[17:00] <ara> moshi moshi
[17:00] <fader> Howdy
[17:00] <bdmurray> hi
[17:00] <ogasawara> ara: heh :)
[17:00] <fader> Incidentally, schwuk sends his regrets, but his house has lost power and he won't make it unless the power is restored
[17:02] <heno> let's start
[17:02] <heno> #startmeeting
[17:02] <MootBot> Meeting started at 12:02. The chair is heno.
[17:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:02] <heno> It's beta week!
[17:02] <pedro_> _o/
[17:02] <eeejay> hey hey
[17:02] <heno> testing is going well :)
[17:03] <davmor2> yeap
[17:03] <heno> a few cases are lagging as usual
[17:03] <heno> fader can you get to some ESX testing today?
[17:04] <fader> heno: we're getting ESX testing daily in the certification environment
[17:04] <heno> Does anyone have a setup for the Raid test?
[17:04] <fader> I can add in some ad-hoc ISO testing if that's what you're looking for
[17:04] <heno> fader: is that installing automatically now?
[17:04] <fader> heno: yep :)
[17:04] <davmor2> heno: no single drives throughout I'm afraid
[17:05] <heno> fader: great, just tick them as done on the tracker then
[17:05] <fader> heno: Will do.
[17:05] <heno> fader: do we have a suitable setup for Raid?
[17:06] <fader> We've got at least one server with RAID hardware but I believe it has only one drive
[17:06] <charlie-tca> heno: I can run RAID on 386
[17:06] <fader> If that qualifies we can use it
[17:06] <charlie-tca> I have 3 drives installed
[17:06] <fader> charlie-tca's setup sounds more suitable :)
[17:07] <heno> charlie-tca: great, can you try http://testcases.qa.ubuntu.com/Install/ServerRAID1 ?
[17:07]  * davmor2 makes a note to get some more drives
[17:07] <charlie-tca> Sure. I'm running an OEM test now, then I will do it.
[17:07] <cr3> by the way, we've had esx testing on a daily basis since march 6th, it's really awesome!
[17:08] <heno> so we're in good shape. Help closing out the cases on http://iso.qa.ubuntu.com/qatracker/build/all/all is appreciated though!
[17:09] <heno> on with our regular agenda: https://wiki.ubuntu.com/QATeam/Meetings
[17:09] <heno> [TOPIC] UbuntuBugDay highlights -- pedro
[17:09] <MootBot> New Topic:  UbuntuBugDay highlights -- pedro
[17:10] <pedro_> We celebrated the cups hug day last Thursday it was pretty good as you can see per https://wiki.ubuntu.com/UbuntuBugDay/20090319
[17:11] <pedro_> Till Kamppeter and Martin Pitt helped us during the event answering questions regarding the reports, thanks a lot guys!
[17:12] <pedro_> from the Bugsquad side paulduf, jgoguen, bigal50, sectech and thekorn made a great work squashing those bugs
[17:12] <heno> cool!
[17:12] <heno> thanks, pedro_
[17:12] <heno> New bug control members! -- bdmurray
[17:13] <stgraber> heya
[17:13] <pedro_> np :-)
[17:13] <heno> bdmurray: I know you've been away - do you have anything on this topic today?
[17:13] <bdmurray> This week Joel Goguen was approved as a Bug Control member!  He is interested in desktop applications like Thunderbird, OpenOffice, and Pidgin.
[17:14] <bdmurray> There are no other applications pending at the moment.
[17:14] <heno> pedro_: can you put him in touch with members of the desktop team?
[17:15] <heno> asac, calc and seb I guess
[17:15] <pedro_> heno: yes! I'll put him in contact with them :-)
[17:15] <asac>  \o/
[17:15] <heno> heh
[17:15] <heno> Next Testing day topic & highlights from last UTD -- ara
[17:16] <ara> davmor2: ^
[17:16] <ara> davmor2 was organizing the latest testing day
[17:16] <davmor2> heno: it went all a bit pear shape because beta iso became available :)
[17:16] <heno> indeed, I should have updated the agenda
[17:16] <davmor2> so most of the result actual went there instead of the wiki
[17:17] <heno> yes this release has been a bit too smooth ... It's worrying ...
[17:18] <ara> heno:  :)
[17:18] <davmor2> heno: Shhhh you'll jinx it
[17:19] <heno> there is still RC and Final
[17:19] <heno> [TOPIC] Private crash report triage -- sbeattie
[17:19] <MootBot> New Topic:  Private crash report triage -- sbeattie
[17:20] <sbeattie> While doing regression triage, I ended up looking at system-config-printer and network-manager's buglists, and found 30-40 private apport bugs for each package.
[17:20] <sbeattie> some reasonably old.
[17:21] <sbeattie> Was wondering if anyone is actively focusing on these and making sure they get opened up.
[17:21] <bdmurray> Perhaps we should get a section added for Hug Days?
[17:22] <sbeattie> that would probably be a good idea.
[17:22] <heno> It's currently the responsibility of everyone (and thus no one) on bug-control
[17:22] <bdmurray> sbeattie: system-config-printer is python right?
[17:22] <sbeattie> yeah
[17:23] <bdmurray> Those are a lot easier to review than core dumps
[17:23] <heno> This would be a great topic for someone on bug-control to take on and drive
[17:24] <sbeattie> bdmurray: the apport-retracer is now deleting core-dumps automatically (in some cases?), so newer aborts are fairly easy to review as well.
[17:24] <bdmurray> sbeattie: that's good
[17:25] <bdmurray> I think the priority should be to review the most recent ones and the ones with good retraces
[17:25] <heno> agreed
[17:26] <heno> so, we'll make it a bug day theme; pedro can you incorporate that? I'll email the bugsquad list asking for interested volunteers as well
[17:27] <bdmurray> heno: bug control you mean
[17:27] <bdmurray> It might neat if we could generate an rss feed of these reports since Launchpad can't.
[17:27] <pedro_> heno: sure, I'll add it to the template for future hug days
[17:28] <heno> bdmurray: I though I would use the bugsquad list but address it mainly to bug control
[17:28] <bdmurray> Ah, that make sense then. ;-)
[17:28] <heno> which brings me to:
[17:29] <heno> [TOPIC] Plans for triaging the Beta bugs next week -- heno
[17:29] <MootBot> New Topic:  Plans for triaging the Beta bugs next week -- heno
[17:29] <heno> We usually get a good flow of bugs just after Beta
[17:29] <heno> should me make some specific plans for triaging those?
[17:30] <heno> pedro suggested an extra bug day on Tuesday
[17:30] <stgraber> is there an easy way to find them ? (tags or similar) ?
[17:30] <stgraber> or just get everything new over the last week or so
[17:30] <heno> bdmurray made a 'yesterday' list once
[17:31] <heno> could we adapt that?
[17:31] <bdmurray> I could probably whip something up like that
[17:31] <heno> rock!
[17:32] <ara> bdmurray: could you please do a couple of them? ...
[17:32] <heno> I can appeal to the de community to dedicate some time to it also
[17:32] <bdmurray> ara: What else did you have in mind?
[17:32] <ara> bdmurray: one for everything filed "yesterday" and one for everything filed "yesterday" in jaunty beta (through apport, knowing exactly it was in jaunty)
[17:33] <bdmurray> ara: okay, got it
[17:34] <ara> in beta time, when there is not much time left to fix bugs, I think it is more important to focus on well written bugs
[17:34] <bdmurray> right, maybe add in the gravity column too
[17:35] <stgraber> ara: so basically focusing only on triaged bugs ?
[17:35] <stgraber> (still need someone to filter them first though)
[17:35] <heno> it would be great if running apport-collect would promote it from the B-list to the A-list :)
[17:36] <ara> stgraber: no, no. if you file a bug through ubuntu-bug or "Report a problem", you have minimum information to start triaging
[17:36] <bdmurray> Yes, I thought having apport-collect tag the bug would be useful too.
[17:36] <ara> stgraber: it will be still "New" but you can skip traiging questions like "which version of ubuntu are you running?"
[17:37] <heno> right, so it's currently non-trivial to pick out bugs treated with apport-collect?
[17:37] <bdmurray> heno: that's correct
[17:37] <stgraber> ara: right, so just using apport's tags, showing only these who've been retraced (or at least were filed with apport)
[17:38] <heno> bdmurray: should we have a blurb about the value of running a-c is the gm stock text fragments?
[17:38] <stgraber> do we have an easy way to look for the release in apport's output (as in filter a bug list based on it) other than going through one by one (manually or using a script) ?
[17:38] <bdmurray> heno: I think that would make more sense after Jaunty releases since apport-collect is not available on Intrepid.
[17:39] <heno> bdmurray: good point
[17:39] <heno> did we agree to run a Beta bug day?
[17:42] <heno> hm, no great demand for that :)
[17:43] <heno> so, for beta bdmurray will prepare a target list and I'll address the dev community
[17:43] <heno> we can encourage people to join #ubuntu-bugs all week of course
[17:43] <heno> Beta Bug Week
[17:44] <heno> Any other topics?
[17:45] <heno> schwuk is working on a new QA landing page and will post to the list
[17:45] <davmor2> whats on the agenda for the next testing day?
[17:45] <sbeattie> QA landing page> yay!
[17:46] <sbeattie> just a reminder to tag jaunty bugs that are regressions with regression-potential so they get on both my and the release team's radar.
[17:48] <heno> davmor2: looks like there is no decision https://wiki.ubuntu.com/Testing/UbuntuTestingDay/Calendar
[17:48] <heno> ara: a server day?
[17:48] <ara> heno: I was talking with mathiaz
[17:49] <ara> and he told me that for server there's too much work to do with documentation first
[17:49] <mgunes> Hi all; somewhat late but I'm in..
[17:49] <ara> he proposed to review the server documentation as a testing day
[17:49] <ara> https://wiki.ubuntu.com/JauntyServerGuide
[17:49] <ara> "<mathiaz> the goal of the testing day would be to go through these sections and make sure that the outlined intructions are working correclty.
[17:49] <ara>  on jaunty."
[17:50] <ara> what do you think?
[17:50] <sbeattie> mgunes: hey!
[17:50] <heno> welcome back mgunes :)
[17:51] <heno> ara: I'd rather get some real testing in this lose to final
[17:51] <ara> yes, that's what I thought
[17:51] <heno> We also talked about checkbox
[17:52] <heno> How about a day looking for installer corner cases?
[17:52] <mgunes> sbeattie, heno, thanks!
[17:52] <ara> heno: example?
[17:52] <heno> not blitzing through lots of installs but doing odd-ball multiple partition stuff
[17:53] <heno> start an install and pull the power chord, that sort of thing :)
[17:54] <heno> I feel we are being a bit shallow with the ISO install testing
[17:54] <heno> going back and forth in ubiquity and d-i, trying to make it crash
[17:55] <heno> perhaps look at old bugs and try to reproduce those
[17:55] <ara> ok, we could do that :-) cjwatson will be pleased ;-)
[17:55] <heno> set your display to 800x600 and run in OEM, mode, etc.
[17:55] <davmor2> ara: yes I'm sure those are the exact words he'll use :)
[17:55] <cr3> do you mean testing those installer corner cases with checkbox?
[17:56] <ara> cr3: no, it was two different things if I understood correctly
[17:56] <heno> cr3: no, I changed topic suddenly :)
[17:56] <cr3> heno: was that checkbox relating to mathiaz's comment then?
[17:57] <heno> though we should make 'run checkbox' part of one of the install cases
[17:57] <heno> fader: you're on that, right?
[17:57] <fader> heno: It's on my list to get into the test cases yes
[17:57] <heno> cool
[17:57] <heno> ok, that's settled, let's wrap up!
[17:58] <heno> #endmeeting
[17:58] <MootBot> Meeting finished at 12:58.
[17:58] <davmor2> thanks
[17:58] <sbeattie> woo, thanks.
[17:59] <ara> thanks :)
[17:59] <ara> cheerio!
[17:59] <mgunes> thanks, see you all next time :)
[18:01] <jcastro> mgunes: good to see you around again!
[18:04] <mgunes> jcastro, you too!
[18:05] <cjwatson> heno: I think I'd prefer *not* to have an attempt to reproduce old bugs
[18:05] <cjwatson> heno: the problem is that a lot of installer bugs are very specific to certain situations and it's all too easy to assume that things are fixed if you don't quite understand what caused them in the first place
[18:06] <heno> cjwatson: heh, ok :) But finding new ones is fine?
[18:06] <cjwatson> heno: absolutely
[18:06] <cjwatson> I'd welcome that
[18:06] <heno> cool