[14:50] <zul> gday
[14:53] <nealmcb> sommer, ttx: howdy!
[14:54] <sommer> yo :-)
[14:54] <ttx> dude
[14:56] <hggdh> ~o~
[14:56]  * nealmcb english has so many different greetings :)
[14:56] <smoser> \0
[14:57] <Daviey> o/
[14:58] <mathiaz> ~~O~~
[14:59] <jjohansen> \o
[15:00] <kirkland> o/
[15:01] <jiboumans> morning folks
[15:01] <jiboumans> #startmeeting
[15:01] <MootBot> Meeting started at 09:01. The chair is jiboumans.
[15:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:01] <jiboumans> [TOPIC] Review ACTION points from previous meeting
[15:01] <MootBot> New Topic:  Review ACTION points from previous meeting
[15:01] <jiboumans> mathiaz to fix the "server fixed bugs" broken script
[15:01] <mathiaz> jiboumans: not done
[15:02] <jiboumans> mathiaz: when can we expect it to be tackled?
[15:02] <mathiaz> jiboumans: this week - now that release is out of the door
[15:02] <jiboumans> mathiaz: ack
[15:02] <jiboumans> ttx to confirm with jib lucid SRU resource allocation
[15:02] <ttx> jiboumans: I mentioned it to you
[15:02] <mathiaz> jiboumans: I should have some more time to look around these lower important todos
[15:02] <ttx> jiboumans: not sure that confirms it yet
[15:03] <jiboumans> ttx: i believe we have a UDS session on this, no?
[15:03] <ttx> jiboumans: yes
[15:03] <jiboumans> mathiaz: it happens, improvement point for next time :)
[15:03] <ttx> "Lucid SRU process review"
[15:03] <jiboumans> ttx: excellent, consider it done then
[15:03] <jiboumans> now, this meeting will focus on the releaes and UDS instead of the usual topics, so bear with us please
[15:04] <jiboumans> [TOPIC] Release status (ttx)
[15:04] <MootBot> New Topic:  Release status (ttx)
[15:04] <jiboumans> how's the war room looking ttx?
[15:04] <ttx> yay
[15:04] <ttx> DefCon 3 so far
[15:04] <ttx> No respin expected
[15:04] <mathiaz> ttx: what does that mean?
[15:04] <mathiaz> ttx: level 3?
[15:04] <ttx> nobody running in circles
[15:04] <nealmcb> :)
[15:04] <jiboumans> mathiaz: you're woefully underprepared for an invasion of your borders sir
[15:05] <zul> drinking yet?
[15:05] <ttx> DefCon 2 would be "pilots scramble to their aircrafs
[15:05] <mathiaz> jiboumans: totally - where I live there isn'
[15:05] <ttx> and DefCon 1 would be permission to engage
[15:05] <mathiaz> jiboumans: totally - where I live there isn't any point in getting prepare for an invasion
[15:05] <zul> release lucid....drunk fix later..
[15:05] <ttx> the absinthe bottle is still full
[15:05]  * hggdh meanwhile drinks a marvelous Brazilan coffee
[15:05] <jiboumans> ttx: any known issues come up that will be release noted or SRU'd early?
[15:06]  * zul hands mathiaz a book about the war of 1812
[15:06] <Daviey> I understand it's tradition for the server boss to buy drinks at UDS for the entire ~ubuntu-server team.. so it's not all bad, eh jiboumans ?
[15:06] <ttx> yes
[15:06] <jiboumans> Daviey: i must have not gotten that memo
[15:06] <ttx> I updated https://wiki.ubuntu.com/ServerTeam/Meeting
[15:06] <mathiaz> jiboumans: you'll get - don't worry
[15:06] <ttx> ah
[15:06] <ttx> I mean https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[15:07] <jiboumans> ttx++ excellent
[15:07] <ttx> We have 4 things ion the release note list
[15:07] <ttx> 4 early targets for SRU
[15:07] <ttx> If you see anything missing, please shout
[15:07] <ttx> (now)
[15:07] <hggdh> ttx, may I propose bug 567592 also?
[15:07] <jiboumans> for the logs:
[15:07] <jiboumans> 423252 (breaks NSS using LDAP+SSL on upgrades from Hardy)
[15:07] <jiboumans> 571057 (breaks OpenLDAP configs on upgrades from Lucid dev milestones)
[15:07] <jiboumans> 570805 (regression in Ubuntu Server installation times on ext4)
[15:07] <jiboumans> 557429 (potential breakage in a scenario with degraded RAID arrays being assembled)
[15:07] <zul> ttx: i know at least one other php one
[15:08] <ttx> hggdh: for release noting ?
[15:08] <mathiaz> bug 423252 <- that won't be SRUable in the short time
[15:08] <hggdh> ttx: for SRU-ing
[15:08] <mathiaz> as there isn't a confirmed fix
[15:08] <hggdh> early
[15:08] <jiboumans> hang on, those were the release note bugs
[15:08] <ttx> mathiaz: right that's why it's on the "under investigation" list
[15:08] <jiboumans> these are the SRUable bugs:
[15:09] <jiboumans> eucalyptus: 567371,565101 (kirkland)
[15:09] <jiboumans> tomcat6: 563642 (ttx)
[15:09] <jiboumans> php5: 541439 (zul)
[15:09] <jiboumans> vmbuilder: 536942,386463,493020,497258,517067,535397,536940,539727,540446,524020 (soren)
[15:09] <zul> heh soren has some work to do
[15:09] <ttx> yes, volcano smoke prevented him to fix those in time
[15:09] <kirkland> jiboumans: i'm prepping a eucalyptus upload right now that addresses 566793, 567371, 565101
[15:09] <ttx> hggdh: ok, I'll look into it
[15:10] <ttx> kirkland: i'll add the missing bugreference, thanks for the pointer
[15:10] <jiboumans> [ACTION] hggdh, zul to get their release note/early SRU bugs known to ttx
[15:10] <MootBot> ACTION received:  hggdh, zul to get their release note/early SRU bugs known to ttx
[15:10] <jiboumans> ttx: any other news from the war room?
[15:10] <zul> ttx: what about the crypt lvm bug?
[15:10] <ttx> zul: the repeated prompt ?
[15:10] <zul> yeah shouldnt that be in the release notes as well?
[15:10] <ttx> zul: I don't think so
[15:11] <Daviey> Is soren going to be able to manage the *long* list of early SRU's?
[15:11] <ttx> it sucks but it's hardly blocking anything
[15:11] <zul> ttx: ack
[15:11] <ttx> Daviey: patches welcome, as usual
[15:11] <ttx> nothing else from the war room
[15:11] <jiboumans> [TOPIC] UEC release status (kirkland)
[15:11] <MootBot> New Topic:  UEC release status (kirkland)
[15:11] <jiboumans> thanks ttx
[15:11] <kirkland> jiboumans: check
[15:12] <kirkland> jiboumans: no release critical issues
[15:12] <ttx> just remember to mark DONE or POSTPONED the remaining work items for 10.04
[15:12] <ttx> by tomorrow eod :)
[15:12] <jiboumans> [ACTION] ALL to mark DONE or POSTPONED the remaining work items for 10.04 by Thu 29 April EOD
[15:12] <MootBot> ACTION received:  ALL to mark DONE or POSTPONED the remaining work items for 10.04 by Thu 29 April EOD
[15:13] <jiboumans> kirkland: the upload you're doing will be a zero day SRU then?
[15:13] <kirkland> jiboumans: i have uploaded now
[15:13] <kirkland> jiboumans: it will be in lucid-proposed as soon as the ubuntu-sru team accepts it
[15:13] <kirkland> jiboumans: normally, it's supposed to bake in -proposed for ~1 week
[15:13] <jiboumans> kirkland: right, but too late for any ISOs of course
[15:13] <jiboumans> understood
[15:14] <kirkland> jiboumans: yes, these won't be on the 10.04 iso (but will be on 10.04.1)
[15:14] <jiboumans> kirkland: does it address all the open bugs we'd hope to have fixed real soon around release, or do we have any open ones left?
[15:14] <kirkland> jiboumans: we could ask for a rush processing of the 1 week bake, since we've been testing it for nearly a week already now
[15:14] <ttx> jiboumans: those are mostly bugs you encounter running over a period of time (not installer issues) so updating is ok
[15:14] <kirkland> jiboumans: these are mostly scalability one
[15:14] <kirkland> jiboumans: i suspect as soon as people actually start deploying 10.04 UEC, we'll get some new, hard ones
[15:15] <jiboumans> kirkland: i'm sure
[15:15] <kirkland> jiboumans: i think ttx had a few more he wanted looked at
[15:15] <ttx> yes, the securitygroup thing I haven't had time to reproduce
[15:15] <kirkland> jiboumans: and smoser still has some upstarty/plymouth-ish issues, ISTR
[15:15] <jiboumans> kirkland: for ec2, surely. we'll cover that next
[15:15] <ttx> yes our images are still pretty brittle when run over UEC
[15:16] <jiboumans> then let's cover that next
[15:16] <jiboumans> [TOPIC] EC2 release status (smoser)
[15:16] <smoser> not brittle
[15:16] <MootBot> New Topic:  EC2 release status (smoser)
[15:16] <jiboumans> thanks kirkland, tt
[15:16] <jiboumans> *ttx
[15:16] <smoser> in most cases things are fine. under high heavy load on UEC the metadata service doesn't come up for minutes.
[15:16] <smoser> the images don't wait long enough
[15:16] <smoser> so yes, maybe brittle
[15:17] <jiboumans> ttx: i trust that is noted somewhere?
[15:17] <ttx> I meant the "can't be contacted by ssh" thing
[15:17] <ttx> jiboumans: it's difficult to releasenote it since we have trouble to understand when it hits
[15:17] <smoser> hold on. getting bugs.
[15:17] <ttx> "UEC image may fail to boot on UEC" isn't a good releasenote text
[15:17] <smoser> bug 565018
[15:18] <smoser> bug 566792
[15:18] <ttx> the second one is under load, right
[15:18] <smoser> i hope to address 566792 sometime very soon after release, or at least part of it.
[15:19] <ttx> but the first one can be hit on a single try, if you're unlucky
[15:19] <smoser> the first bug (instance not reachable via ssh), i have no good explanations under what conditions it fails
[15:19] <smoser> it seems timing related.
[15:19] <hggdh> 566792 seems to happen more when CLC, Walrus, and CC are on differetn machines
[15:19] <smoser> Hmm..
[15:20] <smoser> i guess there should be a third bug. i will open one.
[15:20] <smoser> the 'meta data service comes up slowly' portion of bug 566792 is easily workaroundable in image
[15:20] <smoser> but your boots will just take 3 minutes
[15:21] <jiboumans> beats not booting at all
[15:21] <smoser> the "meta data service returned empty data an http status 200" is not so easily workaroundable.
[15:21] <smoser> that is much harder to reproduce.
[15:21] <smoser> opening bug now.
[15:21] <jiboumans> smoser: any issues with the images themselves?
[15:21] <smoser> well, no. :)
[15:22] <smoser> not after they're booted
[15:22] <jiboumans> smoser++ excellent
[15:22] <hggdh> er
[15:22] <ttx> jiboumans: they run relatively fine on EC2
[15:22] <hggdh> there is bug 567592, hitting plymouth, and may be germane here
[15:22] <jiboumans> ttx: when you say 'relatively' i expect you can tell me when they don't?
[15:22] <smoser> very good on ec2.
[15:22] <ttx> We could have a generic "UEC image may fail to boot on UEC" release note pointing to the bugs still in progress
[15:23] <ttx> jiboumans: I meant "comparatively"
[15:23] <smoser> hggdh, how often do you see that bug ?
[15:23] <hggdh> smoser: every boot I have the console log I see it. I think this may play a role
[15:24] <smoser> "have the console log" ?
[15:24] <hggdh> not the cannot remove, but the ral cause -- plymouth barfs when trying to write to a pts
[15:24] <nealmcb>  
[15:24] <hggdh> smoser: the failed instances
[15:24]  * nealmcb oops
[15:24] <smoser> i dont think thats true.
[15:25] <smoser> you're saying every time you can't reach an instance it has that in it.
[15:25] <smoser> ?
[15:25] <hggdh> I am saying every UEC image boot has it -- plymouth dies with a SIGSEGV
[15:25] <hggdh> and this may cause problems for mountall, and cascade
[15:26] <smoser> correct.
[15:26] <smoser> but not every instance fails in that bug (read only filesystem)
[15:26] <hggdh> indeed, no. But the read-only is (as Collin found) a *possible* consequence, not the cause
[15:27] <smoser> ok.
[15:27] <smoser> i wasn't read-up-to-date on that
[15:27] <hggdh> this is why I would really like to have a new UEC image with Collin's fixes, to test it again
[15:27] <ttx> hggdh: we have a fix for that already ?
[15:28] <hggdh> cjwatson just proposed fixes for it, this morning
[15:29] <ttx> right, we expect to roll Lucid UEC images regularly, so we could have an updated image with the fix quite fast if that fixes it
[15:29] <ttx> there are a few other boot-related fixes in the queue
[15:30] <jiboumans> ok, thanks for that
[15:30] <jiboumans> moving on
[15:30] <jiboumans> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[15:30] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[15:30] <jiboumans> my question: release status? :)
[15:30] <hggdh> jiboumans: seems as ready as possible, with the given exceptions (bugs) above
[15:31] <zul> jiboumans: not paniacing
[15:31] <jiboumans> hggdh: that's great news
[15:31]  * jiboumans attaches the head back to his chicken
[15:31] <smoser> bug 571271 opened for "simple timeout issue"
[15:31] <hggdh> another point
[15:32] <hggdh> I am adding a blueprint (joint QA/Server) for UEC testing. Even with mathiaz scripts (and bless him!), it is extremely costly in time to run the test
[15:33] <hggdh> even more with the dpkg/fsync currently in place :-(
[15:33] <jiboumans> hggdh: engineering or machine time?
[15:33] <hggdh> both of them
[15:33] <hggdh> a re-setup usually takes some two hours, and each stress about another 2 hours
[15:34] <jiboumans> that's costly indeed
[15:34] <jiboumans> let's take some time at UDS to see how we can improve that timewise. if it takes extra hardware, we can probably arrange that too
[15:35] <hggdh> thank you. I will add the blueprint in a few
[15:35] <jiboumans> [ACTION] hggdh to outline testing bottlenecks for UEC testing UDS sessions
[15:35] <MootBot> ACTION received:  hggdh to outline testing bottlenecks for UEC testing UDS sessions
[15:35] <jiboumans> hggdh: any ohter updates from the QA team?
[15:35] <hggdh> no, life is good now ;-)
[15:35] <jiboumans> any questions for hggdh?
[15:36] <jiboumans> i'll take that as a no
[15:36] <jiboumans> [TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)
[15:36] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)
[15:36] <jiboumans> hggdh: thank you
[15:36] <jjohansen> hi
[15:36] <jiboumans> hi there
[15:36] <jiboumans> my question is unchanged: release status? :)
[15:37] <jjohansen> heh, well unfortunately not really changed since last week
[15:37] <jjohansen> the kernel has been frozen and only a couple critical changes have been applied
[15:38] <jjohansen> everything is being queued for SRU
[15:38] <jiboumans> any of those changes or SRU affecting server issues?
[15:38] <jjohansen> no
[15:38] <jiboumans> jjohansen: ok, thanks
[15:39] <jiboumans> i had one specific question about the ext4 performance degrade we saw in benchmarks
[15:39] <jjohansen> okay
[15:39] <jiboumans> this is a public one of those:   http://www.phoronix.com/scan.php?page=article&item=ubuntu_lts_perf&num=2
[15:39] <jiboumans> it's a few weeks old though; have we managed to do anything with/about that ?
[15:40] <jjohansen> hrmm, I actually haven't seen anything about that pass by but give me a sec to check with csurbi
[15:41] <jjohansen> if I recall correctly this particular test wasn't really hitting the disk but I wasn't the one looking into it
[15:42] <jjohansen> jiboumans: I will have to get back to you on specifics as csurbi isn't around atm
[15:42] <jiboumans> jjohansen: no problem. could you coordinate with ttx to see if we should release note anything?
[15:42] <jjohansen> will do
[15:42] <jiboumans> thank you
[15:43] <jiboumans> any other questions or updates for the kernel?
[15:43] <jjohansen> one other little thing, it looks like trying to go pv-ops for EC2 will be a target for M
[15:43] <zul> cool...good luck! ;)
[15:44] <jiboumans> jjohansen: nice to hear
[15:44] <jiboumans> alright, moving on
[15:44] <jiboumans> [TOPIC] Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review (mathiaz)
[15:44] <MootBot> New Topic:  Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review (mathiaz)
[15:44] <jiboumans> i expect very little, but best to check :)
[15:45] <mathiaz> no bugs nominated for any release
[15:45] <mathiaz> anything worth SRU in the last week?
[15:45] <mathiaz> and next week I'll add lucid to the list
[15:45] <mathiaz> so expect a longer SRU review as we go through the lucid nominations
[15:45] <zul> nope
[15:46] <mathiaz> it may require more than one meeting though
[15:46]  * jiboumans renames this the SRU meeting
[15:46] <jiboumans> mathiaz: understood and thanks
[15:46] <jiboumans> [TOPIC] Final call for blueprints for UDS Maverick
[15:46] <MootBot> New Topic:  Final call for blueprints for UDS Maverick
[15:47] <jiboumans> Starting monday, we'll do the planning for the sessions of UDS maverick
[15:47] <jiboumans> if you'd like to have a guaranteed session slot, please make sure your blueprint is created by this Friday end of business
[15:48] <jiboumans> Please also take a look here for currently proposed sessions at UDS: https://wiki.ubuntu.com/ServerTeam/MaverickIdeaPool
[15:48] <jiboumans> if you have any ideas, no matter how experimental, feel free to add those to the above wiki page as well
[15:49] <jiboumans> [TOPIC] Open Discussion
[15:49] <MootBot> New Topic:  Open Discussion
[15:49] <jiboumans> please, go ahead :)
[15:50] <jiboumans> alright, moving on
[15:50] <jiboumans> [TOPIC] New meeting time for the Maverick cycle
[15:50] <MootBot> New Topic:  New meeting time for the Maverick cycle
[15:51]  * hggdh really pays attention now
[15:51] <jiboumans> *drum roll*
[15:51] <ttx> let's all act surprised !
[15:51] <RoAkSoAx> lol
[15:51] <jiboumans> Given that release days/freezes are on Thursday, we'd like to move the meeting to Tuesday 6 pm UTC
[15:51] <hggdh> YES!
[15:51] <jiboumans> this aligns better with west coast attendance (hi jjohansen)
[15:52] <hggdh> (sorry, ttx)
[15:52] <ttx> 1800 UTC, you mean
[15:52] <jiboumans> and is one of the few slots left on the Tuesday meeting schedule
[15:52] <jjohansen> yes it does
[15:52] <jjohansen> :)
[15:52] <jiboumans> ttx: if it makes you feel better
[15:52] <jiboumans> all those opposed say 'nay'
[15:52] <ttx> that makes me feel more accurate :P
[15:52] <jiboumans> no objections, the new meeting time stands
[15:53] <jiboumans> \o/
[15:53]  * hggdh agrees with ttx
[15:53] <Daviey> (if it's changed, the date on the ubuntu fridge cal needs updating)
[15:53] <hggdh> oh, no early mornings...
[15:53] <jiboumans> [TOPIC] Announce next meeting date and time
[15:53] <MootBot> New Topic:  Announce next meeting date and time
[15:53] <jiboumans> kirkland, ttx and myself will be at a company meeting next week, and UDS is the week after
[15:53] <mathiaz> I can run the meeting next Tuesday
[15:53] <jiboumans> is there mileage in a meeting next week, or shall we postpone till after UDS?
[15:54] <jiboumans> mathiaz: thanks for the offer. worth it for you to go through SRUs etc?
[15:54] <ttx> hggdh: oh, meetings after dinner
[15:54] <mathiaz> jiboumans: yes
[15:54] <jiboumans> ok, then
[15:54] <soren> jiboumans: Will you? Even with the new meeting time?
[15:54] <mathiaz> even if it lasts just 10 minutes
[15:54] <jiboumans> soren: i will always. not sure what i will, but i will
[15:55] <jiboumans> mathiaz: excellent
[15:55] <jiboumans> next meeting time is Tuesday May 4th at 1800 UTC
[15:55] <soren> jiboumans: Be at the company meeting at the time of the meeting.
[15:55] <jiboumans> soren: technically, i'll be in a plane over the atlantic
[15:55] <soren> Maybe my intel is wrong :)
[15:55] <ttx> soren: your intel is wrong
[15:55] <jiboumans> thanks for highlighting that crucial distinction :)
[15:55] <jiboumans> alright all, thanks for attending
[15:55] <jiboumans> #endmeeting
[15:55] <MootBot> Meeting finished at 09:55.
[15:56] <nealmcb> sounds like mileage in that meeting to me :)
[15:56] <Daviey> jiboumans: New meeting time is long term?
[15:56] <mathiaz> Daviey: yes :)
[15:56] <Daviey> okay, thanks
[15:56]  * Daviey prods the firdge people
[15:56] <Daviey> fridge*
[15:57] <jiboumans> Daviey: thank you
[16:01] <mvo> hi, meeting? or no meeting?
[16:02] <oubiwann> mvo: no meeting
[16:02] <mvo> ok
[16:02] <mvo> thnaks
[17:53]  * ara waves
[17:53]  * bdmurray waves back
[17:54]  * bladernr \0o/
[17:59] <pedro_> hola!
[17:59]  * marjo waves
[18:00] <ameetp> o/
[18:00]  * fader_ waves.
[18:01] <marjo> #startmeeting QA Team
[18:01] <MootBot> Meeting started at 12:01. The chair is marjo.
[18:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:01] <marjo> [TOPIC] Agenda
[18:01] <MootBot> New Topic:  Agenda
[18:01] <marjo> # SRU testing -- sbeattie (Steve Beattie)
[18:01] <marjo> # Bug Day status -- pvillavi
[18:01] <marjo> # UDS QA Track - ara
[18:01] <marjo> [TOPIC] SRU testing -- sbeattie
[18:01] <MootBot> New Topic:  SRU testing -- sbeattie
[18:03] <sbeattie> SRU Activity report for the past week (since 2010-04-21):
[18:03] <sbeattie> * lucid: 1 new package in -proposed (librsvg)
[18:03] <sbeattie> * karmic: 2 new packages in -proposed (eclipse, sun-java6)
[18:03] <sbeattie>       and 2 packages pushed to -updates (packagekit, vsftpd)
[18:03] <sbeattie> * jaunty: 1 new package in -proposed (sun-java6)
[18:03] <sbeattie> * intrepid: no SRU activity
[18:03] <sbeattie> * hardy: 1 new package in -proposed (sun-java6)
[18:03] <sbeattie> * dapper: no SRU activity
[18:03] <sbeattie> There wasn't a lot of testing activity this past week
[18:03] <sbeattie> Thanks to unggnu, Uri for testing SRUs.
[18:04] <marjo> sbeattie: should pick up next week?
[18:04] <sbeattie> marjo: heh, yes, will definitely pick up next week.
[18:04] <ara> sbeattie, yes, with the classic after release quick SRUs
[18:05] <marjo> sbeattie: anything else?
[18:05] <sbeattie> marjo: nope that's it from me
[18:05] <marjo> [TOPIC] Bug Day status -- pvillavi
[18:05] <MootBot> New Topic:  Bug Day status -- pvillavi
[18:05] <pedro_> On Thursday 22 we had a bug day based on Evince: https://wiki.ubuntu.com/UbuntuBugDay/20100422
[18:05] <pedro_> ~30 bugs were triaged, Thanks a lot to our hug days heroes: charlie-tca, kamusin, sbarjola and yofel
[18:06] <pedro_> As for Tomorrow, our target will be the New and Confirmed bugs without a package:
[18:06] <pedro_> https://wiki.ubuntu.com/UbuntuBugDay/20100429
[18:07] <pedro_> There's a *lot* of bugs to be triaged so if you have some time and want to learn a bit more about bug triage join us. We always recommend this task as one of the easiest for starting to doing bug Triage
[18:08] <ara> is #ubuntu-bugs the best place to go to participate?
[18:08] <pedro_> if you want to start helping your lovely Ubuntu project, this is a perfect time
[18:08] <pedro_> ara, yes #ubuntu-bugs is the right place
[18:08] <ara> pedro_, ok, thanks
[18:08] <pedro_> that's all from here marjo
[18:08] <marjo> pedro_ thx!
[18:09] <pedro_> my pleasure
[18:09] <marjo> [TOPIC] UDS QA Track - ara
[18:09] <MootBot> New Topic:  UDS QA Track - ara
[18:09] <ara> hello!
[18:10] <ara> just a quick reminder that I am waiting for blueprints to schedule in the qatrack
[18:10] <ara> this is the list of sessions that I have scheduled so far
[18:10] <ara>  * Checkbox Improvements - https://blueprints.launchpad.net/checkbox/+spec/qa-m-checkbox
[18:10] <ara>  * Improving ISO testing of Ubuntu and its derivatives - https://blueprints.launchpad.net/ubuntu/+spec/qa-community-m-improve-iso-testing
[18:10] <ara>  * BugSquad Roadmap - https://blueprints.launchpad.net/ubuntu/+spec/qa-m-bugsquad-roadmap
[18:10] <ara>  * Structured Testing Programs - https://blueprints.launchpad.net/ubuntu/+spec/qa-m-community-structured-testing
[18:10] <ara>  * Improving Communication - https://blueprints.launchpad.net/ubuntu/+spec/qa-m-improving-communication
[18:10] <ara>  * Improving Community Laptop Testing - https://blueprints.launchpad.net/ubuntu/+spec/qa-m-laptop-testing
[18:10] <ara>  * Promoting LoCo Testing Teams - https://blueprints.launchpad.net/ubuntu/+spec/qa-m-loco-testing
[18:10] <ara>  * Running Mago tests on a daily basis -  https://blueprints.launchpad.net/ubuntu/+spec/qa-m-mago-daily
[18:10] <ara> if your session is not there, please, let me know
[18:10] <sbeattie> ara: yeah, sorry, I still need to create the apport-udeb blueprint.
[18:11] <ara> sbeattie, no worries :)
[18:11] <ara> also, you can start subscribing to those blueprints, if you want to participate in the discussion
[18:11] <marjo> ara: thx for doing those
[18:11] <sbeattie> ara: also, I talked with the security team, and a roundtable about desktop testing state of the art and how to collobarate, and they thought it was a good idea, so I'll create a discussion blueprint for that.
[18:12] <ara> sbeattie, great!
[18:12]  * ara really wants to participate in that one
[18:12] <marjo> ara: that would be a good time to get an update on sikuli
[18:12] <sbeattie> heh, I think you're an essential attendee for that.
[18:12] <ara> marjo, indeed
[18:13] <ara> that's all from me
[18:13] <marjo> ara: thx
[18:13] <marjo> [TOPIC] QA Team Workitems Status
[18:13] <MootBot> New Topic:  QA Team Workitems Status
[18:14] <marjo> http://people.canonical.com/~pitti/workitems/canonical-platform-qa.html
[18:14] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-platform-qa.html
[18:14] <marjo> as you all can see, the QA team has been very productive during Lucid
[18:15] <marjo> lots of work items done & not many postponed
[18:15] <marjo> thx to everyone who contributed
[18:15] <marjo> we need to keep up the momentum going into next release
[18:15] <marjo> thx
[18:16] <marjo> [TOPIC] Final testing status
[18:16] <MootBot> New Topic:  Final testing status
[18:17] <ara> There are some remaining test cases for amd64
[18:17] <ara> most of them are marked as Started
[18:17] <marjo> http://iso.qa.ubuntu.com/qatracker/build/all/all
[18:17] <MootBot> LINK received:  http://iso.qa.ubuntu.com/qatracker/build/all/all
[18:17] <cr3> ara: I'm burning those images as we speak
[18:17] <ara> cr3, nice :) thanks!
[18:17] <bladernr> ara:  I'm right in the middle of one, myself
[18:17] <fader_> Same here
[18:17] <marjo> ara: i tried to recruit everyone to cover all the remaining test cases including optional ones
[18:18] <cyphermox> yup
[18:18]  * sbeattie is working on getting iscsi set up.
[18:18] <fader_> slangasek just asked if anyone can cover the xubuntu amd64 netboot test, as it's the only one left without anyone starting on it
[18:18] <marjo> the only challenge would be http://iso.qa.ubuntu.com/qatracker/result/4133/497
[18:18] <ara> sbeattie, did you read my notes on that?
[18:18] <ara> sbeattie, the set up with kvm, I mean
[18:19] <sbeattie> ara: yes, I'm using that as a guide, thanks!
[18:19] <ara> sbeattie, great
[18:19] <marjo> ara: thx for writing up your notes on that
[18:19] <marjo> and posting it
[18:19] <hggdh> marjo: I think I can mark the UEC separate install as done -- I did it on the UEC stress tests
[18:19] <marjo> hggdh: ok, go for it
[18:20] <marjo> fader: thx
[18:20] <hggdh> marjo: I am wrong -- this is the separate network topo, the one the rig cannot test right now
[18:20] <hggdh> sorry
[18:20] <marjo> hggdh: oh well
[18:21] <hggdh> only ttx and kirkland can test it, to my knowledge
[18:21] <marjo> hggdh: ack
[18:21] <ttx> only me, since it requires 2 reasonably-fasy NIC on one of the laptops -- and I don't have my rig with me
[18:22] <ttx> s/fasy/fast/
[18:22] <hggdh> marjo: something to discuss on the blueprint I proposed for the server/QA
[18:22] <marjo> hggdh: definite +1
[18:23] <hggdh> for the record: https://blueprints.edge.launchpad.net/ubuntu/+spec/server-maverick-uec-testing
[18:23] <marjo> folks: thx for pitching in; i think we're going to hit very high test coverage
[18:24] <hggdh> ttx: please ask jib to approve it
[18:24] <marjo> folks: any other topics for today? if not, i propose we all go back to testing
[18:24] <ttx> hggdh: it's on our list, it will be approved
[18:24] <marjo> ttx: thx
[18:24] <hggdh> cool
[18:25] <marjo> going once
[18:25] <marjo> going twice
[18:25] <marjo> meeting adjourned
[18:25] <marjo> go lucid!
[18:25] <marjo> #endmeeting
[18:25] <MootBot> Meeting finished at 12:25.
[18:25] <marjo> thx everyone!
[18:25] <ara> cheers
[18:26] <pedro_> thanks
[19:20] <ghostcube> bportal.de
[19:20] <ghostcube> damn xchat
[19:20] <ghostcube> sorry guys
[20:00]  * stgraber waves
[20:00] <highvoltage> hello all
[20:00] <alkisg> Hi people
[20:00] <isforinsects> hi there
[20:01] <highvoltage> anyone willing to take notes? I usually do but I have a huge headace (I asume caused by internet withdrawal)
[20:01] <stgraber> I'll do it
[20:02] <stgraber> highvoltage: is your latency back to something reasonable ?
[20:02] <highvoltage> stgraber: irssi says lag: 1.44, so it seems good enough for the meeting at least
[20:02] <Lns> hi!
[20:03] <stgraber> ok ;)
[20:03] <stgraber> so I guess that meeting should probably be quite focused on the release tomorrow and UDS
[20:03] <highvoltage> I just want to say that it's an extreme relief that the release is tomorrow and that the iso ended up being in great shape
[20:04] <alkisg> Many thanks to all of you who worked hard for this release
[20:04] <stgraber> we need http://www.edubuntu.org/news/10.04-release to contain our release announcement, we also need to check and update the Ubuntu release notes and technical overview to make sure we didn't miss anything there
[20:05] <bencrisford> hullo everyone
[20:05] <stgraber> ISO images are fine, tested with nothing major that'd require them to be regenerated, so I'm pretty confident that those will be the final ones
[20:06] <highvoltage> stgraber: according to http://www.seacom.mu/news/news_details.asp?iID=132 my connection should be coming back up in about 3 hours
[20:06] <bencrisford> highvoltage:  :D
[20:06] <highvoltage> so late tonight and tomorrow morning I should be able to jump in at least
[20:06] <highvoltage> stgraber: yay!
[20:07] <stgraber> highvoltage: yeah ! will be great to have you back online completely ;)
[20:07] <bencrisford> are we drafting the announcment in a gobby doc?  that way could eliminate errors/things getting missed out
[20:08] <stgraber> we should do that yes
[20:08] <highvoltage> stgraber: there's two things that I keep remembering that we left out
[20:08] <stgraber> we can probably base it on the 9.10 one and add the changes that are already described in Ubuntu's release notes, though in more details
[20:09] <highvoltage> stgraber: I always remember it when I'm driving and when I'm in the shower :)
[20:09] <highvoltage> we haven't mentioned fat clients yet, that is new in lucid right?
[20:09] <highvoltage> or did we have that in karmic already?
[20:09] <highvoltage> iirc LTSP 5.2 only came in lucid
[20:10] <stgraber> proper fat client support is lucid indeed, though not enabled by default in either ubuntu or edubuntu
[20:10] <stgraber> but probably worth mentionning at the same place as ltsp live
[20:11] <highvoltage> I think we mentioned improvements in ltsp in previous releases, but yes I guess since we don't provide it in a default install then perhaps it is indeed not worth mentioning there
[20:11]  * alkisg has been working with fat clients for the past months, had no problems whatsoever
[20:11] <alkisg> It's as much there in the default install as localapps... it's an optional thing of course, but it's there
[20:11] <highvoltage> alkisg: that's really good to hear :)
[20:12] <stgraber> highvoltage: mentioning it is probably fine, though it'd probably be better to add it as some kind of note rather than having it announced as a whole new feature
[20:12] <stgraber> highvoltage: either that or we can mention ltsp 5.2 in the list of softwares included and mention it there
[20:12] <highvoltage> *nod*
[20:13] <stgraber> so, for that release announcement, should we start a new gobby document just after the meeting containing the content of the 9.10 announcement and work from that ?
[20:13] <bencrisford> sounds good
[20:13] <highvoltage> +1
[20:15]  * stgraber created edubuntu-lucid-announcement for that
[20:16] <stgraber> so, next is topics for UDS, unless we have something else to discuss for tomorrow's release ?
[20:16] <stgraber> highvoltage: what was the name of the gobby document for maverick ?
[20:16] <stgraber> highvoltage: the one I found appears to be empty
[20:16] <highvoltage> stgraber: I'm unsure... checking...
[20:18] <highvoltage> stgraber: ah right, I emptied it :)
[20:19] <highvoltage> I moved it to the wiki page so I removed the contents so that someone wouldn't continue editing it there
[20:19] <stgraber> ah yes, because it's on the wiki ;)
[20:19] <stgraber> so that's fine
[20:19] <stgraber> maybe you should post the URL in the gobby ?
[20:19] <stgraber> that'd make things less confusing ;)
[20:19] <highvoltage> https://wiki.kubuntu.org/Edubuntu/Specifications/Brainstorming/Maverick
[20:19] <highvoltage> ok will do
[20:20] <highvoltage> or at least, https://wiki.ubuntu.com/Edubuntu/Specifications/Brainstorming/Maverick
[20:21] <stgraber> I created edubuntu-uds-maverick in case we want somewhere to write a list of the specs we want as well as a short description (so we can then copy/psate to LP)
[20:25] <bencrisford> stgraber: think I fixed a typo in your typing, if I was wrong, please correct me!
[20:26] <bencrisford> i didn't know whether to fix it or not :
[20:26] <stgraber> sure, feel free to correct my typos ;)
[20:26] <bencrisford> I really feel that we should schedule the sessions ASAP
[20:26] <bencrisford> and decide on times during this meeting
[20:26] <stgraber> (and my english as well if the grammar sounds weird ;))
[20:27] <bencrisford> because that way we can make it so as many remote participants as possible can participate
[20:27] <stgraber> well, we can't decide times, that's the tricky part
[20:27] <bencrisford> really..?  there is alot free on the schedule, do you get assigned times rather than choosing?
[20:27] <stgraber> we have to put them on LP and poke some team leads to put them on the schedule, then they'll be assigned time slots depending on how plans to attend them physically
[20:27] <stgraber> so to avoid conflicts with other sessions
[20:27] <bencrisford> oh, ok :/
[20:28] <stgraber> so if I put myself as "participation essential" on two sessions as the same time, the script (or human) will likely move on of the two to another slot
[20:28]  * bencrisford prays to the god of UDS that he can make some of the sessions (remotely, but still)
[20:28] <stgraber> the final schedule is usually the one displayed at 9am in the lobby ;)
[20:28] <highvoltage> heh :)
[20:28] <bencrisford> :o
[20:28] <bencrisford> :(
[20:28] <stgraber> (and it may change slightly at lunch time)
[20:28] <bencrisford> lol
[20:29] <mhall119> oy, missed another one
[20:29] <highvoltage> stgraber: do we need a session for the remote-installer?
[20:29] <bencrisford> its *possible* i can do some during the day (via my nokia and other PCs with frenode chat), but im pretty much only around in the evening
[20:30] <highvoltage> stgraber: hah! I was *just* about to start typing that
[20:30]  * bencrisford thinks his little red "t" in the doc looks quite cute
[20:32] <highvoltage> stgraber: I realise LDAP/Kerberos would fall under the server track/team, but should we add it to our list so long or do it directly from the server team side?
[20:32] <stgraber> highvoltage: not sure, it's probably not worth a 1 hour session, might merge that into the last one ?
[20:32] <stgraber> or with the first one ?
[20:33] <highvoltage> stgraber: ok we can add it to installer-improvements
[20:33] <highvoltage> stgraber: these are more for sessions rather than specifications right?
[20:33] <stgraber> ldap/kerberos should be already on the server team's todo list I guess
[20:34] <stgraber> well, the idea is that for each we'll register a spec and get that scheduled (as all sessions need a spec)
[20:35] <highvoltage> ok, right
[20:35] <stgraber> so ideally, each point should last more than 30min or be merged in another
[20:36] <stgraber> (I know I tend to be attending a lot of session at UDS, so it's always better if we can avoid spending half of the session looking at our mails)
[20:37] <highvoltage> ok. it seems like we more or less know what we want to do, I can't see anything that would really cause lots of disagreement or be difficult to implement
[20:38] <highvoltage> it's kind of difficult for me to imagine how uds will happen especially since I still don't know whether I'll be able to make it there :/
[20:38] <highvoltage> we can probably discuss a bunch of stuff outside of 'official' sessions on #edubuntu
[20:39] <highvoltage> at least you are there so you could ask the installer/artwork/etc teams if we need quick and good feedback
[20:40] <stgraber> yeah, I uess that what we really need to have scheduled is session where we need people from outside of the existing edubuntu community.
[20:40] <stgraber> smaller edubuntu-specific details can be discussed off-uds
[20:40] <stgraber> (as long as it's on some kind of roadmap ;))
[20:41] <highvoltage> yep, so I guess we should at least have a session for installer plans
[20:41] <highvoltage> I'm not sure how much work adding those screenshots and descriptions would be, but it's glade files at least
[20:42] <highvoltage> would still be nice to get some expert advice though
[20:42] <stgraber> yep, UDS should be good for that
[20:44] <bencrisford> do the streams in the meeting rooms get recorded?  or are they just live?  or are they even doing that this time around?
[20:45] <highvoltage> bencrisford: audio is live and video recorded for later
[20:45] <bencrisford> video?  in every session?
[20:46] <highvoltage> bencrisford: yep, there has been before. not sure if they'll do it for this one
[20:46] <bencrisford> highvoltage: I hope so, that would make things so much easier
[20:46] <stgraber> last time it was only for a few sessions
[20:46] <stgraber> these are marked as videotaped on the schedule
[20:46] <bencrisford> I think I remember there being some at karmic
[20:46] <bencrisford> but it was mainly like the plenarys and stuff
[20:47] <highvoltage> bencrisford: I was at the karmic one and that one was very well videod
[20:47] <bencrisford> highvoltage: really?  I don't remember that :/
[20:47] <bencrisford> I remember I was free all week
[20:47] <bencrisford> so I was live streaming and IRCing
[20:48] <highvoltage> bencrisford: the video wasn't live
[20:49] <bencrisford> highvoltage: but I don't remember seeing it after
[20:50] <highvoltage> it came quite a bit after (like, months).
[20:50] <highvoltage> I think having that much video was just too much
[20:51] <bencrisford> http://video.ubuntu.com/uds/karmic/
[20:51] <bencrisford> is that it?
[20:51] <bencrisford> there is quite alot there :/
[20:51] <bencrisford> how'd I miss that
[20:52] <highvoltage> seems like that's just the plenaries though
[20:52] <highvoltage> aaaanyway...
[20:52] <highvoltage> something left for this meeting?
[20:54] <bencrisford> highvoltage: yes!
[20:54] <bencrisford> I nearly forgot
[20:55] <bencrisford> I was gonna bring up what to do about the teams blueprint and RichEd
[20:55] <bencrisford> do we try and contact him?  he has a mobile number on his wiki page apparently, and mdke suggested we could maybe send him an SMS, I said I would bring it up here
[20:55] <highvoltage> bencrisford: didn't mdke re-assign it to you?
[20:56] <bencrisford> yes, but mdke suggested contacting him to inform him of the change and inviting him back if he wants in
[20:56] <highvoltage> bencrisford: I've tried to contact him for even months before he left canonical and couldn't get in touch with him
[20:56] <bencrisford> we both agreed however that that isnt that important
[20:56] <bencrisford> ok
[20:57] <bencrisford> well I dont see what else we can do, and it isnt exactly imperative
[20:57] <highvoltage> you're free to try to sms him if you want, but I'm 100% sure it would be a waste of time
[20:58] <bencrisford> ok, I don't think its that important
[20:58] <bencrisford> but it would be decent of us to let him know whats happening with the blueprint he created
[20:58] <bencrisford> I guess he wouldnt expect us to put this much effort into it though
[20:59] <bencrisford> so its more than reasonable to give up I guess
[21:00] <highvoltage> bencrisford: I don't think you have to give up, if you want to work on it, please do so
[21:00] <bencrisford> highvoltage: work on contacting him?
[21:00] <highvoltage> bencrisford: richard hasn't been part of the project or cantactable in a very long time
[21:01] <bencrisford> ok, I understand that
[21:01] <highvoltage> bencrisford: we don't have any responsibility or commitment to find him first before moving on with anything
[21:02] <bencrisford> highvoltage: I think he does have a right to know, but we shouldnt go out of our way to inform him
[21:03] <bencrisford> if its just sending an email, I am more than happy to, but in this scenario, I think its best not to waste time that could be spent on our project, contacting someone who doesn't seem to care
[21:03] <highvoltage> bencrisford: if it will make you feel better, send an email/sms to all his known contact details
[21:03] <bencrisford> highvoltage: it wont make me feel better :), it was just suggested and it seemed a good idea, but like I say, in this scenario it probably isnt
[21:04] <bencrisford> I honestly don't feel as strongly about it as it might seem, i'm just following up what I started
[21:04] <highvoltage> bencrisford: I know why mdke suggested it, and I don't think mdke knows richard or had much interactions with him
[21:04] <bencrisford> I do understand that, and mdke understood too once I explained
[21:04] <bencrisford> but I thought I should bring it up here to make sure I have done the right thing by not contacting him
[21:05] <highvoltage> yes, you did
[21:05] <highvoltage> I can't make that any cleare
[21:05] <highvoltage> I can't make that any clearer
[21:05] <highvoltage> you
[21:06] <highvoltage> (sorry, on netbook keyboard, can't type as fast as I'd like :) )
[21:06] <bencrisford> regarding the actual blueprint, I would suggest having an IRC "session" post-UDS to work on it
[21:06] <bencrisford> you guys can discuss community at UDS
[21:06] <highvoltage> sounds good
[21:06] <bencrisford> and then I am happy to start working on it with whoever else is
[21:07] <bencrisford> we just need to seperate the teams into say, 3 groups?
[21:08] <bencrisford> 1) No/little attention needed, 2) Necessary team (needs attention), 3) Unnecessary team (needs deletion)
[21:08] <highvoltage> let's take it to #edubuntu since we're over our meeting time anyway :)
[21:08] <bencrisford> woops, so we are
[21:08] <highvoltage> (yep that sounds good)
[21:08] <bencrisford> dont forget to gong!
[21:08] <highvoltage> bencrisford: your turn!
[21:08] <bencrisford> highvoltage: my turn to what?
[21:08] <highvoltage> to hit the gong
[21:09]  * highvoltage hands bencrisford the big sticky thing
[21:09] <bencrisford> :O
[21:09]  * bencrisford is honoured
[21:09] <bencrisford> *GONGGGGG*
[21:09]  * bencrisford puts all his strength into an almighty swing
[21:09] <highvoltage> nice one
[21:09] <bencrisford> :D