[13:54] <zul> gday
[13:55] <smoser> (o
[13:55] <sommer> yo
[13:59] <kirkland`> o/
[14:01] <mathiaz>  /o
[14:03] <zul> is ttx running the meeting?
[14:04] <hggdh> ~o~
[14:06] <ttx> hm
[14:06] <ttx> sorry for being late
[14:06] <ttx> busy triaging sdamba bugs for our marvelous Bugzapping bugday
[14:06] <ttx> #startmeeting
[14:06] <MootBot> Meeting started at 08:06. The chair is ttx.
[14:06] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[14:07]  * jjohansen fades in
[14:07] <ttx> Agenda at https://wiki.ubuntu.com/ServerTeam/Meeting
[14:07] <ttx> jib is on a plane somewhere, so I'll chair. zul is our scribe today
[14:07] <ttx> [TOPIC] Review ACTION points from previous meeting
[14:07] <MootBot> New Topic:  Review ACTION points from previous meeting
[14:07] <ttx> * mathiaz to sync up with cjwatson re: ubuntu-server upload team
[14:08] <mathiaz> ttx: not done
[14:08] <ttx> [ACTION] mathiaz to sync up with cjwatson re: ubuntu-server upload team
[14:08] <MootBot> ACTION received:  mathiaz to sync up with cjwatson re: ubuntu-server upload team
[14:08] <ttx> [TOPIC] Beta1 status review
[14:08] <MootBot> New Topic:  Beta1 status review
[14:09] <ttx> Beta1Freeze is tomorrow... Only beta1-targeted bugs will be accepted, which doesn't prevent you from queueing less important bugs
[14:09] <ttx> That should affect several specs
[14:10] <ttx> eucalyptus-merging-and-packaging: we might want to target extra bugfixes (currently only the upgrade stuff is targeted)
[14:10] <kirkland`> ttx: i have a qemu-kvm upload coming
[14:10] <ttx> kirkland`: we'll review the list before I leave for vacation
[14:10] <kirkland`> ttx: okay
[14:11] <ttx> apt-mirror/ec2: this should be delivbered without image changes, by reusing the current DNS setup
[14:11] <ttx> papercuts, bugzapping, puppet-testsuite: fixes of lesser importance should be queued for post beta1freeze
[14:11] <ttx> Beta1-targeted bugs :
[14:12] <ttx> bug 499389
[14:12] <ttx> zul: you're on it ?
[14:12] <zul> worked on that last night im just want to talk to mvo about it
[14:12] <ttx> ok.
[14:12] <ttx> bug 526480 -- still pending MIR team review
[14:12] <ttx> bug 519513
[14:13] <ttx> kirkland: looking good ?
[14:14] <kirkland> ttx: i think so
[14:14] <kirkland> ttx: working on it today
[14:14] <kirkland> ttx: should have something by EoW
[14:14] <ttx> kirkland: cool !
[14:15] <ttx> Questions/comments on Beta1 ?
[14:15] <ttx> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[14:15] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[14:16] <ttx> hggdh: hi !
[14:16] <ttx> hggdh: around ?
[14:16] <mathiaz> kirkland: are you done with the UEC testing with the DC hardware?
[14:17] <ttx> ok, let's do kernel forst
[14:17] <ttx> [TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)
[14:17] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)
[14:17] <ttx> jjohansen: hi !
[14:17] <jjohansen> hi
[14:17] <jjohansen> so we still have Bug #527208 outstanding
[14:17] <ttx> whats'up in the lower rings ?
[14:18] <jjohansen> it won't make beta1 as the kernel closed monday
[14:18] <hggdh> ttx, I am here -- looking at logs
[14:18] <ttx> hggdh: we'll come back to you in a few
[14:18] <ttx> we also have https://bugs.launchpad.net/bugs/531823
[14:19] <ttx> will we have a workaround for this one soon, or after beta 1 ?
[14:19] <jjohansen> for the Lucid or Karmic bug?
[14:20] <ttx> jjohansen: lucid ?
[14:20] <jjohansen> Soon I hope
[14:20] <ttx> but with kernel frozen that will be post-beta 1 ?
[14:21] <jjohansen> correct
[14:21] <ttx> jjohansen: ok, maybe comment and update milestone to reflect that
[14:21] <ttx> anything else for kernel ?
[14:21] <jjohansen> yes
[14:22] <ttx> back to...
[14:22] <jjohansen> we had a late conflict ridden rebase for the EC2 kernel, so keep your eyes out for new bugs
[14:22] <mathiaz> jjohansen: IIUC the vlan-modules udeb should be available in beta1?
[14:22] <jjohansen> mathiaz: yeah
[14:22] <mathiaz> jjohansen: great - thanks
[14:23] <ttx> smoser: ^ ec2 kernel rebase
[14:23] <smoser> i see.
[14:23] <ttx> ok, back to...
[14:23] <ttx> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[14:23] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[14:23] <ttx> hggdh: hi :)
[14:23] <hggdh> hi
[14:23] <ttx> what's up ?
[14:24] <hggdh> we have now atlas failing on the regression PPA. I do not understand the error:http://pastebin.ubuntu.com/392548/
[14:24] <hggdh> ans MySQL is still failing
[14:24] <hggdh> I have a question: is coreutils server, or core?
[14:25] <mathiaz> hggdh: why is atlas regression tested?
[14:25] <ttx> probably foundations land, mathiaz could confirm
[14:25] <zul> what is atlas btw?
[14:25] <mathiaz> hggdh: coreutils is fondation IMO
[14:25] <hggdh> mathiaz: I do not know why atlas, it was already there
[14:26] <ttx> hggdh: ask soren about it when you get a chance
[14:26] <mathiaz> hggdh: well - it's in universe and I'm not sure it's server related
[14:26] <mathiaz> zul: atlas - Automatically Tuned Linear Algebra Software
[14:26] <ttx> zul/mathiaz: mysql is still blocking on the certificate ?
[14:27] <ttx> who can fix that ?
[14:27] <mathiaz> ttx: I'd have to look at the logs
[14:27] <hggdh> even more it states it is related to numerical software...
[14:27] <hggdh> will ask Soren
[14:27] <zul> ttx: i have a fix but its failing somewhere else now
[14:27] <mathiaz> hggdh: IIUC it's 5.0 that fails
[14:27] <ttx> zul: you're on it ?
[14:28] <hggdh> mathiaz: mysql-dfsg-5.0 5.1.30really5.0.83-0ubuntu3
[14:28] <zul> ttx: yeah ill take some time to look at it agian
[14:28] <mathiaz> hggdh: 5.0 is scheduled to be removed from the archive in lucid
[14:28] <ttx> mathiaz: you mean we shouldn't care ?
[14:28] <mathiaz> hggdh: so there is not point in regression testing 5.0 in lucid
[14:29] <ttx> looks like the contents of the regression rig needs to be updated
[14:29] <hggdh> sounds like it
[14:29] <hggdh> suggestions welcome
[14:29] <ttx> [ACTION] hggdh to remove mysql5.0 and question atlas in the build regression test rig
[14:29] <MootBot> ACTION received:  hggdh to remove mysql5.0 and question atlas in the build regression test rig
[14:29] <mathiaz> hggdh: is there a list of packages being published?
[14:29] <mathiaz> hggdh: and is there a summary of the build failure (and since when)?
[14:30] <hggdh> mathiaz: yet unknown for first Q, yes, for second. At least I receive emails on the failures
[14:30] <mathiaz> hggdh: IMO there isn't much visibility on what is done in the regression testing PPA
[14:31] <ttx> hggdh: try to see inside the QA team how you want to handle that, not sure sharing soren's rig is the best way going forward
[14:31] <hggdh> I will look at it now. So far I just left it running (and did not worry)
[14:31] <mathiaz> hggdh: I don't know what's is tested and get notified only when there are build failures
[14:31] <mathiaz> hggdh: right - at least there is something in place
[14:31] <ttx> hggdh: did you start looking into the UEC test rig ?
[14:31] <hggdh> so we need to revisit it
[14:32] <mathiaz> hggdh: and it's been useful so far IMO
[14:32] <mathiaz> hggdh: the process may need to be reviewed at next UDS
[14:32] <hggdh> ttx: no really. kirkland gave me some links to look at, but suggested to wait for the current tests to end
[14:32] <ttx> hggdh: ok
[14:32] <ttx> anything else for the QA team ?
[14:33] <mathiaz> hggdh: right - once kirkland is done, I'll give you an overview of the beast
[14:33] <hggdh> not right now
[14:33] <kirkland> mathiaz: hggdh: i'm done now!
[14:33] <kirkland> mathiaz: it's all yours
[14:33] <ttx> [TOPIC] Euca2ools/Boto 1.9 test coverage
[14:33] <MootBot> New Topic:  Euca2ools/Boto 1.9 test coverage
[14:33] <mathiaz> hggdh: ^^ - ok we should sync up later after the meeting then
[14:34] <hggdh> mathiaz: roj
[14:34] <ttx> Background: we run our euca2ools with boto 1.9 while upstream tests with boto 1.8
[14:34] <ttx> We also tend to run always the same basic set of commands (I know I do)
[14:35] <ttx> so in order to get confidence that lesser-used commands are working, I prepared a test coverage page
[14:35] <ttx> https://wiki.ubuntu.com/Boto19TestCoverage
[14:35] <ttx> When you use a euca2ools command succesfully, please update that page.
[14:35] <ttx> For the mre complex commands, the idea is to test the optional parameters as well, which will take more time
[14:36] <ttx> I know smoser has been running quite a few of those already, we just need to make sure we cover them all.
[14:36] <ttx> questions ?
[14:37] <ttx> (this will probably be a beta2 target)
[14:37] <smoser> and, please, when you find something broken, open a bug
[14:37] <smoser> and copy me, its probably easily fixed, but not if we dont' know about it.
[14:37] <ttx> bonus points if you can check if the bug also exists with boto 1.8
[14:37] <ttx> smoser: any way to easily test with boto 1.8 ?
[14:38] <smoser> which is, actually easy to do. i will post instructions on how.
[14:38] <ttx> smoser: ok, just update the wikipage
[14:38] <smoser> yes
[14:38] <ttx> [TOPIC] Server Papercuts
[14:38] <MootBot> New Topic:  Server Papercuts
[14:38] <ttx> Status for beta-1 : https://launchpad.net/server-papercuts/+milestone/lucid-beta-1
[14:38] <ttx> 4 bugs still open from a total of 14
[14:39] <ttx> Please feel free to fix what you can, especially before Beta1Freeze
[14:39] <ttx> No nominations this week, which is quite disappointing
[14:40] <ttx> maybe some more blogging needs to be done about it
[14:40] <ttx> i can't beleieve we identified all the pain points
[14:40] <ttx> We only have 5 targets for beta2, so 9 more should be identified
[14:41] <ttx> Comments ?
[14:41] <zul> maybe blog about it a bit more
[14:42] <ttx> [ACTION] ttx to blog about the beta-1 campaign so far, to trigger new candidates
[14:42] <MootBot> ACTION received:  ttx to blog about the beta-1 campaign so far, to trigger new candidates
[14:42] <ttx> [TOPIC] Bugzapping status (kirkland)
[14:42] <MootBot> New Topic:  Bugzapping status (kirkland)
[14:42] <ttx> kirkland: quick status ? Samba started today.
[14:42] <mathiaz> ttx: aha - that explains the sudden increase in samba related bug mail
[14:43] <kirkland> ttx: i think it went well so far
[14:43] <zul> mathiaz: its not just me ;)
[14:43] <kirkland> ttx: qemu-kvm's bugs cut in half
[14:43] <ttx> kirkland: is there anything planned for next week already ?
[14:43] <kirkland> ttx: and i'm a lot more confident in our qemu-kvm offering now
[14:43] <kirkland> ttx: not planned, no ... i could lead a libvirt one, i suppose
[14:43] <kirkland> ttx: but i'd be happy to see someone else lead one too
[14:43] <kirkland> s/too/instead/g
[14:44] <ttx> For those interested, we are running a two-day samba bugzapping effort... Today is bugtriage day, in #ubuntu-bugs with the QA team
[14:44] <ttx> (combined with a bugday, which proves very fruitful)
[14:44] <ttx> At the end of today we should have bugfixing targets for tomorrow.
[14:44] <kirkland> ttx: week after next is eucalyptus/euca2ools
[14:45] <ttx> We'll coordinate bugfixing tomorrow in #ubuntu-server
[14:45] <mathiaz> and there is a mysql one scheduled as well
[14:45] <ttx> mathiaz: when is it ?
[14:45] <mathiaz> ttx: week of April 1st
[14:45] <mathiaz> ttx: just before Beta2 freeze
[14:45] <ttx> sounds like a bad joke.
[14:46] <ttx> anything else on the bugzapping subject ?
[14:46] <mathiaz> ttx: :) it's gonna be the last days of March
[14:46] <kirkland> not from me
[14:46] <ttx> [TOPIC] Server documentation status (ttx, sommer)
[14:46] <MootBot> New Topic:  Server documentation status (ttx, sommer)
[14:46] <kirkland> well, thanks to all who have participated
[14:46] <mathiaz> ttx: nothing on the 1st of April (it's BetaFreeze2 actually)
[14:46] <ttx> I wanted to get a current status on the server documentation
[14:46] <ttx> sommer: around ?
[14:47] <ttx> I identified a few outdated things in the current guide
[14:47] <ttx> was wondering if help was needed to fix it
[14:47] <ttx> example: it talks about screen-profiles, likewise-open5
[14:47] <ttx> requirements look like they need a refresh
[14:47] <ttx> UEC is absent
[14:48] <ttx> See http://doc.ubuntu.com/ubuntu/serverguide/C/
[14:49] <ttx> OK, I'll sync with sommer by email on the subject -- feel free to chime in with the outdated stuff you find
[14:49] <kirkland> ttx: i'll gladly update the screen-profiles -> byobu bits
[14:49] <ttx> [ACTIOn] ttx to bring up status of server doc in an email thread
[14:49] <MootBot> ACTION received:  ttx to bring up status of server doc in an email thread
[14:50] <ttx> [TOPIC] Server team upload rights (Daviey, mathiaz)
[14:50] <MootBot> New Topic:  Server team upload rights (Daviey, mathiaz)
[14:50] <ttx> mathiaz: delayed to next week ?
[14:50] <mathiaz> ttx: yes
[14:50] <ttx> [TOPIC] Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review  (mathiaz)
[14:50] <MootBot> New Topic:  Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review  (mathiaz)
[14:50] <mathiaz> so I cleaned up the nominations lists
[14:51] <mathiaz> there are two nominations for karmic:
[14:51] <mathiaz> bug 530945
[14:51] <mathiaz> bug 34181
[14:52] <mathiaz> I'm going to decline the latter
[14:52] <ttx> yes
[14:52] <ttx> I'd tend to accept the nomination for the first one
[14:52] <ttx> Andres knows what he is doing :)
[14:53] <ttx> He will probably push the SRU through
[14:53] <mathiaz> ok - karmic bugs processed
[14:53] <zul> we might want 182572 in hardy
[14:53] <mathiaz> http://qa.ubuntu.com/reports/ubuntu-server-team/fixedbugs.ubuntu-server.latest.html
[14:53] <MootBot> LINK received:  http://qa.ubuntu.com/reports/ubuntu-server-team/fixedbugs.ubuntu-server.latest.html
[14:53] <mathiaz> anything worth ^^ in there
[14:54] <mathiaz> bug 182572
[14:54] <mathiaz> kirkland: anything SRU worthy that came out of the qemu bug zap?
[14:54] <ttx> zul: it's ostly cosmetic
[14:54] <kirkland> mathiaz: i don't think so
[14:55] <ttx> nothing from me
[14:55] <mathiaz> allright then
[14:55] <mathiaz> that's all for the SRU review
[14:55] <ttx> [TOPIC] Open Discussion
[14:55] <MootBot> New Topic:  Open Discussion
[14:56] <zul> php 5.3.1 is mostly done
[14:56] <hggdh> this is the current list of packages being regression-tested (from Soren):
[14:56] <zul> debian has 5.3.2 which fixes a couple of issues with things like mediawiki
[14:56] <Daviey> zul: 5.3.2 bug fix only release didn't seem like a good idea?
[14:56] <Daviey> bah, too slow
[14:57] <zul> Daviey: im thniking of it for beta2
[14:57] <ttx> smoser: help needed testing EBS root ?
[14:57] <smoser> anyone who wants to start an EBS root volume and kick it a bit is my friend
[14:57] <smoser> and will be awarded a or other beverage if they tell me their experiences
[14:57] <zul> as in kick it when its down? ;)
[14:58] <mathiaz> smoser: is the information on which EBS volume to test available somewhere?
[14:58] <hggdh> packages = libvirt postgresql 8.3 and 8.4, mysql 5.0, openldap, php5, python2.6, and atlas
[14:58] <smoser> mathiaz, just in my email to the list at the moment.
[14:58] <smoser> to multiple lists
[14:58] <smoser> hold on, let me dig url
[14:58] <mathiaz> and I'd also like to congratulate the whole team for the New,Undecided daily bug triagging
[14:58] <mathiaz> the whole backlog has been processed last week
[14:59] <smoser> http://groups.google.com/group/ec2ubuntu/browse_thread/thread/a7fdc6f714f71085/5efd475e9e536a9f?lnk=gst&q=ebs+root#5efd475e9e536a9f
[14:59] <MootBot> LINK received:  http://groups.google.com/group/ec2ubuntu/browse_thread/thread/a7fdc6f714f71085/5efd475e9e536a9f?lnk=gst&q=ebs+root#5efd475e9e536a9f
[14:59] <mathiaz> so congrats to all!
[14:59]  * ttx highfives with all the team
[14:59] <mathiaz> now we should just stay on cruise control
[14:59] <mathiaz> so make sure to review the list on your assigned day
[14:59] <ttx> ok
[14:59] <kirkland> \o/
[15:00] <ttx> [TOPIC] Announce next meeting date and time
[15:00] <MootBot> New Topic:  Announce next meeting date and time
[15:00] <ttx> Next week, same time, same place
[15:00] <ttx> #endmeeting
[15:00] <MootBot> Meeting finished at 09:00.
[16:00] <lool> heya
[16:00] <barry> hi everybody.  welcome to this week's foundations team meeting
[16:00] <barry> #startmeeting
[16:00] <MootBot> Meeting started at 10:00. The chair is barry.
[16:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:00] <tremolux> hey!
[16:00] <cjwatson> hi
[16:01] <ev> hello
[16:01]  * slangasek waves
[16:01] <barry> it's my first time chairing, so let me know if i forget anything :)
[16:01] <Keybuk> the donuts
[16:01] <doko> hi
[16:01] <ev>  fatty
[16:01] <barry> [LINK] https://wiki.ubuntu.com/FoundationsTeam/Meetings/2010/0310
[16:01] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/Meetings/2010/0310
[16:01] <Keybuk> (says the guy who just pounded his fists into the sofa screaming "I was just going to say that!")
[16:01] <barry> Keybuk: didn't you get the bagels i sent?
[16:02] <Keybuk> barry: ev must have eaten them all before I got here
[16:02]  * barry can't do anything about that
[16:02] <ev> yeah, proper bagels wouldn't stand a chance
[16:02] <ev> anyway
[16:02] <barry> lessee, james_w, doko, slangasek are you here?
[16:02] <james_w> hi
[16:02] <barry> oops, sorry slangasek
[16:03]  * cjwatson sneaks his activity report in under the wire
[16:03] <slangasek> yes, you may have overlooked me amid all the lust for fried pastries :)
[16:03] <barry> i think mvo sends his virtual apology
[16:03] <barry> :)
[16:03] <Keybuk> I thought we'd tempted you into going to voodoo donuts
[16:03] <slangasek> Keybuk: I went to voodoo donuts - I didn't eat any of them :)
[16:04] <barry> [TOPIC] lightning round
[16:04] <MootBot> New Topic:  lightning round
[16:04] <barry> >>> team = ['Keybuk', 'barry', 'cjwatson', 'ev', 'james_w', 'lool', 'mvo', 'slangasek', 'slangasek', 'tremolux']
[16:04] <barry> >>> import random
[16:04] <barry> >>> order = team[:]
[16:04] <barry> >>> random.shuffle(order)
[16:04] <barry> >>> print ', '.join(order)
[16:04] <barry> tremolux, Keybuk, ev, slangasek, mvo, cjwatson, slangasek, james_w, barry, lool
[16:04] <ev> lol
[16:04] <barry>  
[16:04] <tremolux> heh
[16:04] <tremolux> I've been working on OEM tasks from last Thu through yesterday.
[16:04] <tremolux>  Now back to my Software Center todo list, bug fixing and triage, etc.
[16:04] <tremolux>  (done)
[16:05] <Keybuk> I rewrote the Plymouth VT handling code,
[16:05] <Keybuk> then I rewrote the Plymouth X transition/handover code,
[16:05] <Keybuk> then I rewrote bits of various plugins to make them work,
[16:05] <Keybuk> then I fixed the binary to remove various race conditions,
[16:05] <Keybuk> NOW FETCH ME WIL WHEATON!
[16:05]  * barry realizes he has a bug and should have used a set :)
[16:05] <ev> mostly ubiquity UI changes after a meeting the other day with the design team (sorry release team), looking into an apt-setup bug whereby if you have a USB disk that exposes a fake CD device, apt-setup fails.
[16:06] <ev> (done)
[16:06] <doko> barry: should slangasek report twice, and me not at all? ;p
[16:06] <slangasek> doko: you can be me first!
[16:06] <barry> doko: that's my bug.  you can be slangasek II today
[16:07] <slangasek> continuing work on casper plymouth support
[16:07] <slangasek> FFes, we have them
[16:07] <slangasek> working on the supportable-binaries spec
[16:07] <slangasek> (done)
[16:07] <lool> Was on travel to London; doing a lot of interviews and working on random ARM bugs.
[16:07] <doko> vacation last week; now working on llvm updates, preparing icedtea6-1.8 release, python updates to new subminor releases
[16:07] <lool> (done)
[16:07] <doko> (done)
[16:07] <lool> Uh /me is confused
[16:08] <lool> (scrolled back to wrong line, sorry)
[16:08] <james_w> fixing bugs in bzr-builddeb, still need to get that synced from unstable, chasing failures, and working with LP developers on the build from branch feature. More of the same to come.
[16:08] <james_w> (done)
[16:08] <cjwatson> you're all very confused
[16:08] <cjwatson> hm, no mvo
[16:08]  * slangasek grins
[16:08] <cjwatson> done: parted 2.2; grub 1.98; failed to finish console-setup/plymouth interaction fixes but had a good go at it and should be able to finish in time
[16:08] <cjwatson> blocked: nothing
[16:08] <cjwatson> todo: partman-base fixes for advanced format drives (doing the hardware setup today); dpkg performance/correctness backports, nearly ready to go; running around like headless chicken fixing bugs for beta 1
[16:08] <cjwatson> --
[16:09] <barry> Several branches merged for SC ratings and reviews.  Still to decide whether
[16:09] <barry> we're going to make it.  Good discussion on canonical-tech about the url
[16:09] <barry> structure for r&r server.  Computer Janitor dbus refactoring mostly done,
[16:09] <barry> waiting for review.  Would love to get minor ui exception to clean the gui of
[16:09] <barry> unused elements.  Starting implementation work for PEP 3147 today. (done)
[16:09] <barry> anybody we haven't heard from? :)
[16:09] <barry> [TOPIC] Outstanding action items from last meeting
[16:09] <MootBot> New Topic:  Outstanding action items from last meeting
[16:09] <barry> none that i'm aware of.  am i missing anything?
[16:10] <barry> [TOPIC] Milestoned bugs
[16:10] <MootBot> New Topic:  Milestoned bugs
[16:10] <barry> [LINK] https://bugs.launchpad.net/ubuntu/lucid/+bugs?field.milestone%3Alist=21446
[16:10] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/lucid/+bugs?field.milestone%3Alist=21446
[16:11] <barry> not sure what to say about this, does anybody have anything on this topic?
[16:11] <cjwatson> yow, we're up since last week
[16:12] <lool> new arm bugs in the mix
[16:12] <cjwatson> is there a view of the milestone list that shows assignees?
[16:12] <slangasek> no :(
[16:12] <barry> yeah, that kind of sucks
[16:12] <slangasek> not in LP - there are some external reports, though I don't know that those are current either
[16:12] <slangasek> (nor have the URLs to hand)
[16:14] <barry> [TOPIC] Targeted bugs
[16:14] <MootBot> New Topic:  Targeted bugs
[16:14] <barry> [LINK] https://bugs.launchpad.net/ubuntu/lucid/+bugs
[16:14] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/lucid/+bugs
[16:14] <barry> these also don't show assignees
[16:15] <barry> any thoughts on these bugs?
[16:15] <cjwatson> if somebody could track down an appropriate report, that would be great
[16:16] <cjwatson> what I really want to know is which bugs aren't being dealt with
[16:16]  * slangasek nods
[16:16] <cjwatson> there's https://edgelaunchpad.net/ubuntu/+milestone/ubuntu-10.04-beta-1, although it's suboptimal in other ways
[16:16] <cjwatson> err
[16:16] <cjwatson> https://launchpad.net/ubuntu/+milestone/ubuntu-10.04-beta-1
[16:17] <slangasek> it includes all the milestoned bugs, not just the targeted ones, yes
[16:17] <cjwatson> and doesn't show the package.  and shows fix-released bugs.
[16:17] <cjwatson> (and invalid and wontfix)
[16:17] <cjwatson> in fact in general it sucks, just differently
[16:18] <barry> cjwatson: do you think the reports exist but we just aren't sure where, or that they don't exist (at all, or in a useful format)?
[16:18] <cjwatson> I'm fairly sure they don't exist in Launchpad; they have existed externally in the past but I'm not sure where or if they're up to date
[16:18] <cjwatson> was it Bryce who used to maintain one?
[16:18] <barry> agreed about launchpad
[16:20] <barry> cjwatson: if you let me know what it is you'd like to see (either in irc or via email) i can take a crack at a launchpadlib script to produce the report.  dunno where i'd stick it right now, but i'd link it off the foundations wiki page
[16:21] <cjwatson> ok, action me?
[16:21] <barry> cjwatson: yep, and then action me
[16:21] <barry> [ACTION] cjwatson to spec out requirements for launchpadlib bug report script
[16:21] <MootBot> ACTION received:  cjwatson to spec out requirements for launchpadlib bug report script
[16:21] <barry> [ACTION] barry to implement script
[16:21] <MootBot> ACTION received:  barry to implement script
[16:22] <barry> sound okay?
[16:23] <cjwatson> yeah, I'd like this part of the meeting to be farming out tasks that aren't being handled, rather than everyone sitting madly opening tabs in firefox
[16:24] <barry> that sounds like a much more productive use of our time.  maybe combine milestoned and targeted bugs topics
[16:25] <barry> cjwatson: we can take this offline.  moving on...
[16:25] <barry> [TOPIC] Sponsorship queue
[16:25] <MootBot> New Topic:  Sponsorship queue
[16:25] <barry> [LINK] http://qa.ubuntu.com/reports/sponsoring/
[16:25] <MootBot> LINK received:  http://qa.ubuntu.com/reports/sponsoring/
[16:26] <barry> again, apologies.  i'm not sure what i should say here
[16:27] <barry> [TOPIC] Any business from activity reports
[16:27] <MootBot> New Topic:  Any business from activity reports
[16:27] <barry> nothing from reports; does anybody have anything not on the agenda?
[16:27] <barry> reminder: send me your reports if you haven't already :)
[16:27]  * slangasek nods
[16:27] <cjwatson> I was wondering if anyone had thoughts on bug 513197
[16:28] <cjwatson> I have been meaning to get round to merging this for some time, and it would be a shame to release without the stability fixes
[16:28] <cjwatson> OTOH it has feature enhancements as well ...
[16:31] <barry> would be nice to have.  i was just trying to mount an ntfs usb drive for a friend over the weekend to get some data off of it.  mostly worked but had a few minor problems
[16:31] <barry> anything else not on the agenda?
[16:31] <slangasek> cjwatson: I suppose there's enough there to send it through for an FFe
[16:32] <barry> how about...
[16:32] <barry> [TOPIC] Good news!
[16:33] <MootBot> New Topic:  Good news!
[16:33] <cjwatson> slangasek: 'k
[16:33] <barry> python 2.6.5rc2 coming out today.  2.6.5 final planned for 2010-03-19.  2.7a4 and 3.1.2rc1 were released last week.
[16:35] <barry> [TOPIC] Chair for next meeting
[16:35] <MootBot> New Topic:  Chair for next meeting
[16:35] <cjwatson> it's probably about my turn again?
[16:36] <barry> cjwatson: sounds good.  thanks!
[16:36] <barry> [TOPIC] AOB
[16:36] <MootBot> New Topic:  AOB
[16:37] <barry> i'm feeling like we're done :)
[16:37] <barry> #endmeeting
[16:37] <MootBot> Meeting finished at 10:37.
[16:37] <barry> thanks everybody!
[16:37] <tremolux> thanks!
[16:38] <ev> thanks!
[16:57]  * ara waves
[16:57] <bladernr_> \0/
[16:57]  * bladernr_ and his giant head have arrived
[16:58]  * charlie-tca waves too
[16:58]  * bdmurray waves
[16:58]  * marjo waves
[16:59]  * stgraber waves (but will only be there for 2 minutes ;))
[16:59] <pedro_> hello!!
[16:59]  * fader_ waves.
[16:59] <marjo> #startmeeting QA Team Meeting
[17:00] <MootBot> Meeting started at 10:59. The chair is marjo.
[17:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:00] <marjo> hi folks
[17:00] <marjo> Agenda:
[17:00] <marjo>     * SRU testing -- sbeattie (Steve Beattie)
[17:00] <marjo>     * Bug Day status -- pvillavi
[17:00] <marjo>     * Ubiquity testing -- ara
[17:00] <marjo> [TOPIC] * SRU testing -- sbeattie (Steve Beattie)
[17:00] <MootBot> New Topic:  * SRU testing -- sbeattie (Steve Beattie)
[17:00] <sbeattie> SRU Activity report for the past two weeks (since 2010-02-24):
[17:00] <sbeattie> * karmic: 7 new packages in -proposed (ec2-init, eucalyptus, linux-fsl-imx51, logcheck, rrdtool, tzdata, xorg-server) and 12 packages pushed to -updates (bld, d4x, eucalyptus, foomatic-filters, gcalctool, image-store-proxy, linux, linux-backports-modules-2.6.31, linux-ec2, openoffice.org, python-profiler, ubuntu-dev-tools)
[17:00] <sbeattie> * jaunty: 2 new packages in -proposed (cups, tzdata) and 2 packages pushed to -updates (amsn, openoffice.org)
[17:00] <sbeattie> * intrepid: 1 new package in -proposed (tzdata) and 1 package pushed to -updates (openoffice.org)
[17:00] <sbeattie> * hardy: 2 new packages in -proposed (cupsys, tzdata) and 3 package pushed to -updates (linux, openoffice.org, virtualbox-ose-modules)
[17:01] <sbeattie> * dapper: 1 new package in -proposed (langpack-locales)
[17:01] <sbeattie> Thanks to Paul Elliott (omahn), Michael Nagel, Ralf Doering, Erik B. Andersen, and Evan Broder for testing SRUs the past two weeks.
[17:01] <sbeattie> (end report)
[17:01] <marjo> thx sbeattie
[17:01] <marjo> any questions re SRU?
[17:02] <marjo> [TOPIC]  * Bug Day status -- pvillavi aka pedro
[17:02] <MootBot> New Topic:   * Bug Day status -- pvillavi aka pedro
[17:03] <pedro_> This week the Ubuntu Server Team is concentrating on Samba
[17:03] <pedro_> mostly doing bug fixing and triaging
[17:03] <pedro_> the triaging part is happening today with an special Bug Day we organized for them
[17:03] <pedro_> you can follow up the progress on https://wiki.ubuntu.com/UbuntuBugDay/20100310
[17:04] <pedro_> the bug fixing part is going to happen tomorrow
[17:04] <pedro_> for that you can find more information on ttx post about it http://fnords.wordpress.com/
[17:05]  * ttx hugs pedro_
[17:05] <pedro_> again if you have some spare minutes please join us, specially if you have access to a windows 7 machine and can test with it
[17:05]  * pedro_ hugs ttx back
[17:05] <pedro_> for tomorrow!
[17:06] <pedro_> Kyle Law organized a bug day on which the target is Ubiquity
[17:06] <pedro_> https://wiki.ubuntu.com/UbuntuBugDay/20100311
[17:07] <pedro_> I saw that there's an Ubiquity item on the agenda as well so seems tomorrow is going to be an Ubiquity day for lot of people ;-)
[17:07] <marjo> pedro: yes, ubiquity needs some extra love these days
[17:08] <pedro_> marjo, cool! we hope to have a great participation from our community on that
[17:08]  * pedro_ hugs the bugsquad
[17:08] <pedro_> marjo, that's all from here ;-)
[17:08] <marjo> pedro_ thx!
[17:08] <marjo> [TOPIC] Ubiquity testing -- ara
[17:08] <MootBot> New Topic:  Ubiquity testing -- ara
[17:08] <ara> hello!
[17:08] <ara> to continue with ubiquity...
[17:09] <ara> we are trying to test its changes from now, until the release of Lucid. The objective is to catch bugs earlier, and avoid late rebuilds during ISO testing.
[17:09] <ara> I already sent a couple of emails to the ubuntu-qa mailing list
[17:09] <ara> last week we tested 2.1.30, and this week it is the turn of 2.1.33
[17:10] <ara> Of course, we are not covering all the testcases, but just some combinations of them.
[17:10] <ara> Finishing a test won't do any harm, and we only have 11.
[17:10] <ara> So, if you have a little time to cover one or two testcases, we will easily reach full coverage by the end of the week.
[17:10] <ara> you can find the testcases at http://pairwise.qa.ubuntu.com/
[17:10] <ara> does anybody have any questions about the process?
[17:10] <YokoZar> I'll note that there were a variety of Ubiquity regressions in the past few releases (eg Jaunty->Intrepid I think had a problem where if you mounted a disk it wouldn't unmount it for you at install time, but Hardy would)
[17:11] <YokoZar> My question would be about adding test cases for issues like that
[17:11] <YokoZar> or rather specific tests for each regression we've had in the past
[17:11] <ara> YokoZar, that would be awesome, we have a new feature in the ISO test tracker that allow to add optional testcases
[17:12] <ara> YokoZar, our problem, always, is to reach all the coverage
[17:12] <ara> YokoZar, adding 100 new testcases won't help, if nobody covers them
[17:12] <YokoZar> Of course
[17:12] <YokoZar> Although these sorts of Ubiquity issues aren't necessarily limited to just pre-release ISO testing but rather could be an ongoing thing like you noted
[17:13] <ara> YokoZar, feel free to send your testcases suggestions to the ubuntu-qa mailing list to discuss them there
[17:13] <ara> YokoZar, or do you have any example right now?
[17:13] <sbeattie> ara: do we shuffle the pairings in each round of testing, or are they the same pairs as from the 2.1.30 testing?
[17:14] <charlie-tca> Xubuntu does not have current desktop images, for anyone trying to do this
[17:14] <YokoZar> Oh, regarding Ubiquity, I did notice a whole bunch of grammar errors and out of date things in the slideshow itself
[17:14] <ara> sbeattie, I am afraid this week and last one were the same (I did it quickly this morning), but indeed, your suggestion makes sense. I will shuffle them for next week
[17:14] <YokoZar> I suspect this isn't something that's "tested" regularly
[17:15] <ara> YokoZar, this is not the place to discuss current bugs of ubiquity
[17:15] <YokoZar> I'm not sure what the process is for updating that sort of thing as the slideshow is new though
[17:15] <bdmurray> well that's easy enough to look at / fix without install testing
[17:15] <YokoZar> I guess it's just more ubiquity bugs in general then that we catch with testing
[17:17] <marjo> any other questions re ubiquity testing?
[17:17] <marjo> thx ara!
[17:17] <marjo> [TOPIC] New Agenda Topics?
[17:17] <MootBot> New Topic:  New Agenda Topics?
[17:18] <marjo> folks: any new topics for today?
[17:18] <marjo> if not, i propose we adjourn the meeting
[17:19] <marjo> going once
[17:19] <marjo> twice
[17:19] <marjo> ok ttx has quit; must be end of meeting
[17:19] <fader_> Heh
[17:19] <marjo> thx all!
[17:19] <ara> thanks!
[17:19] <marjo> #endmeeting
[17:19] <MootBot> Meeting finished at 11:19.
[17:20] <ara> bye bye
[17:20] <pedro_> thanks!
[17:23] <arcaous> hello
[17:25] <arcaous> the matrix has you
[17:29] <kamusin> haha
[19:01] <highvoltage> hi
[19:02] <alkisg> Hi all
[19:02] <mgariepy> hi
[19:02]  * stgraber waves
[19:02] <ubudog> hello
[19:02] <mgariepy> i will be there this afternoon but i'm following 2 meetings. i won't be there to interact much.
[19:03] <ubudog> next up is the server team meeting right?
[19:03] <highvoltage> ubudog: yep
[19:03] <ubudog> should start about now
[19:03] <highvoltage> anything we need to add for the agenda tonight?
[19:03] <highvoltage> ubudog: oh this is the Edubuntu meeting starting now
[19:03] <ubudog> oh ok
[19:04] <ubudog> why isn't the membership meeting on the fridge calender for thursday?
[19:04] <highvoltage> ubudog: server meeting was 5 hours ago according to the Fridge calendar
[19:04] <ubudog> hmm
[19:05] <highvoltage> for technical things from my side,
[19:05] <Lns> hi guys
[19:05] <ubudog> hello
[19:05] <highvoltage> the ltsp-live script is now working. I'm just going to clean up a bit and then update the ltsp package
[19:06] <stgraber> yeah !
[19:06] <highvoltage> it still needs a menu entry but that's nothing big at least
[19:06] <highvoltage> we also still need the squashfs on the dvd but I'll pest -vvv lamont and hopefully that will help :)
[19:07] <highvoltage> the live install cd will reuse some of the live ltsp stuff, I also still need to do the zenity dialog that runs from the ubiquity hook, I should have that done by the enf of the week
[19:07] <stgraber> great
[19:08] <highvoltage> from the artwork dept, the missing icon we have in our theme is due to bug 525295
[19:09] <highvoltage> it should be fixed soon, not so much we have to do there, I'll keep an eye on it though and if we have to I'll do a workaround in the icon theme
[19:09] <highvoltage> gdm seems to just use the default gnome wallpaper now so nothing we had to change there
[19:10] <highvoltage> we still need a new LDM theme and plymouth theme, and Edubuntu logos need to be updated everywhere, but we're waiting on new Edubuntu logos from Canonical for that
[19:10] <highvoltage> stgraber: did canonical perhaps give you any kind of ETA for that?
[19:10] <stgraber> yeah, eta was a week ago ;)
[19:10] <stgraber> I'll poke Iain a bit and see when we can expect to get the new logo
[19:11] <Lns> we just need an 'E' and a 'd' and we can make it ourselves =p
[19:11] <highvoltage> Lns: give me an "E"!
[19:11] <stgraber> yeah, that's the issue, these two letters haven't been approved yet
[19:11]  * Lns loves the new font for ubuntu logo
[19:11] <highvoltage> we'll just grab the E and the d from the old ubuntu-title font :)
[19:12] <stgraber> highvoltage: not sure we want that ;)
[19:12] <Lns> ooo, that's a good idea =) an 'edu' that is a bit different
[19:12] <highvoltage> that would be a branding nightmare :)
[19:12] <Lns> maybe bolded or something?
[19:13] <highvoltage> that's basically where things stand from my side at the moment
[19:14] <highvoltage> oh and there's an annoying ltsp bug where ldm-server's installation just stops but it's a known issue
[19:14] <stgraber> fixed
[19:14] <stgraber> uploaded 2 hours ago
[19:14] <highvoltage> \o/
[19:14] <Lns> nice stgraber =)
[19:15] <stgraber> well, "I guess it's fixed". I'm currently 7000km away from my LTSP setup ;)
[19:16] <highvoltage> stgraber: coming from you, "I guess it's fixed" is good enough for me :)
[19:16] <highvoltage> overall we're not looking too bad for Lucid.
[19:16] <stgraber> indeed
[19:17] <highvoltage> if we could get that squashfs image and logos within the next week or so, then we can focus on bugs and getting the website/marketing/etc good
[19:17] <stgraber> something else, for these of you who didn't see my post on -devel is that we have edubuntu-dev approved as uploader for the edubuntu package set in lucid
[19:17] <highvoltage> and also start drawing up ideas for lucid+1
[19:17] <highvoltage> stgraber: wow, I missed that, that is great news, we've been waiting for that for a long time
[19:18] <highvoltage> stgraber: shall we make the next meeting an EC meeting so that we can approve uploaders?
[19:18] <stgraber> yeah, I suggested doing that in that mail
[19:19] <stgraber> so we really should make the next meeting an EC meeting, we should probably look at the documentation in detail as it's basically the EC approving new edubuntu-dev members who will also be EC members :)
[19:19] <stgraber> so that will be quite interesting ;)
[19:20] <highvoltage> it's one of the problems with having a small team
[19:20] <highvoltage> I guess it was like that when the first Ubuntu teams started out as well
[19:21] <highvoltage> yikes I haven't read mailing lists today at all (been on of those days)
[19:21] <stgraber> hehe
[19:22] <highvoltage> stgraber: so does the package set cover all packages in our seeds?
[19:22] <highvoltage> or just the educational ones?
[19:22] <stgraber> other than that, I'm planning another ldm + ltsp upload quite soon, currently producing snapshot builds on request in my PPA and will tag + upload, ideally before beta (next week)
[19:22] <stgraber> highvoltage: only the edubuntu-specific ones
[19:22] <stgraber> highvoltage: and it's not complete yet, for example the menueditor isn't part of the set currently
[19:22] <highvoltage> ok
[19:22] <stgraber> I attached the list of the packages in the set to that mail
[19:23] <highvoltage> sbalneav will be glad
[19:24] <alkisg> We should also emphasize our "stable" ppa - maybe even provide an easy way for people to put it in their sources
[19:25] <stgraber> alkisg: add-apt-repository should be easy enough, maybe apt-url can do that too
[19:25] <highvoltage> next week once our technical work should be mostly done, I'm going to work a bit with hedgemadge so that we can get our website more or less sorted. I don't want to leave that to the last minute before release
[19:26] <highvoltage> next week would probably also be a good timme to start working on some release notes/announcements so that we don't have to do that right at the end as well
[19:26] <stgraber> having beta released next week, I'll at least update the release notes to include any relevant edubuntu item (like the fact we're missing the squashfs, if not fixed by then)
[19:27] <highvoltage> the stable ppa- have we decided what that will be yet?
[19:27] <stgraber> for the actual release, we'll probably just do as usual, copy/paste from Ubuntu, include our edubuntu-specific items, work on it on the wiki + copy it to the website afterwards
[19:30] <highvoltage> I guess it will just be a ppa owned by edubuntu-dev
[19:30] <stgraber> yep, that'd make sense
[19:30] <highvoltage> oh, it's allready registered
[19:31] <highvoltage> 3 of them, Edubuntu Testing Archive, Edubuntu Stable Updates, Edubuntu Work in Progress
[19:31]  * mhall119|work is here
[19:31] <alkisg> It'd be nice if we shipped selected updates through them
[19:32] <alkisg> E.g. ltsp or italc updates...
[19:33] <highvoltage> yep. people who want the latest and greatest (and bleeding edge) ltsp versions will probably use stgraber's ppa
[19:33] <alkisg> Sure - I was mostly thinking of bug-fixing updates
[19:33] <highvoltage> but it will probably be a good idea to copy some ltsp package versions over to the edubuntu ppa to make some important fixes available to them
[19:34] <highvoltage> ltsp is at least important enough to be SRU'd for most issues
[19:34] <alkisg> Well, "ldm hangs on logout" never got an SRU
[19:35] <stgraber> nobody ever worked on one ;)
[19:36] <alkisg> k, but a ppa would make that much easier. In the same sense that people are using stgraber's ppa for ltsp, they could be using edubuntu's stable ppa for selected updates
[19:36] <highvoltage> yeah the bug fix must be available first before the paackage can be updated :)
[19:37] <alkisg> E.g. new sabayon that's actually working... etc
[19:37] <highvoltage> I assumed we would use that for new packages as well that's not in a release yet, that we've tested and know is usuable?
[19:38] <highvoltage> anything else for the meeting? Seems like we pretty much covered everything
[19:39] <stgraber> nothing on my side
[19:39]  * alkisg will try to have CK/PK fixes for ltsp fat clients in time for beta
[19:40] <highvoltage> I just want to say thanks to each one of you who've been involved so far. been great working with you and I think Lucid will be a great release judging by what we have so far
[19:40] <highvoltage> it's going to give us something real good to build lucid+1 one
[19:40] <stgraber> yep, +1
[19:40] <highvoltage> *on
[19:40] <alkisg> Right, it's a really good (and fresh) start
[19:41] <highvoltage> I'd really like to see some of LaserJock's ideals realised for the M release
[19:41] <highvoltage> have some interaction with educators and find out what they want and see how much we can do for them
[19:42] <highvoltage> K12-LTSP has some simple scripts that does things like push an icon to all users' desktops
[19:42] <highvoltage> it's a simple thing but people like it. I think there's a bunch of things like that we could look at
[19:43] <alkisg> Yes, a collection of scripts would be great
[19:43]  * alkisg is working on that :)
[19:43] <highvoltage> I know and I'm counting on that :)
[19:43] <highvoltage> alkisg: that would also be nice for the PPA
[19:44] <highvoltage> ok I'm going to call the meeting to an end unless there's anything else?
[19:44] <highvoltage> ok I guess it's off to #edubuntu then.
[19:44] <highvoltage> *gong*
[19:45] <alkisg> Thanks all
[23:35] <jfrorie> ne1 from the laptop qa team online?