/srv/irclogs.ubuntu.com/2010/04/28/#ubuntu-meeting.txt

=== Claudinux_ is now known as Claudinux
=== yofel_ is now known as yofel
=== noy_ is now known as noy
=== Ng_ is now known as Ng
=== rgreening_ is now known as rgreening
zulgday14:50
nealmcbsommer, ttx: howdy!14:53
sommeryo :-)14:54
ttxdude14:54
hggdh~o~14:56
* nealmcb english has so many different greetings :)14:56
smoser\014:56
Davieyo/14:57
mathiaz~~O~~14:58
jjohansen\o14:59
kirklando/15:00
jiboumansmorning folks15:01
jiboumans#startmeeting15:01
MootBotMeeting started at 09:01. The chair is jiboumans.15:01
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:01
jiboumans[TOPIC] Review ACTION points from previous meeting15:01
MootBotNew Topic:  Review ACTION points from previous meeting15:01
jiboumansmathiaz to fix the "server fixed bugs" broken script15:01
mathiazjiboumans: not done15:01
jiboumansmathiaz: when can we expect it to be tackled?15:02
mathiazjiboumans: this week - now that release is out of the door15:02
jiboumansmathiaz: ack15:02
jiboumansttx to confirm with jib lucid SRU resource allocation15:02
ttxjiboumans: I mentioned it to you15:02
mathiazjiboumans: I should have some more time to look around these lower important todos15:02
ttxjiboumans: not sure that confirms it yet15:02
jiboumansttx: i believe we have a UDS session on this, no?15:03
ttxjiboumans: yes15:03
jiboumansmathiaz: it happens, improvement point for next time :)15:03
ttx"Lucid SRU process review"15:03
jiboumansttx: excellent, consider it done then15:03
jiboumansnow, this meeting will focus on the releaes and UDS instead of the usual topics, so bear with us please15:03
jiboumans[TOPIC] Release status (ttx)15:04
MootBotNew Topic:  Release status (ttx)15:04
jiboumanshow's the war room looking ttx?15:04
ttxyay15:04
ttxDefCon 3 so far15:04
ttxNo respin expected15:04
mathiazttx: what does that mean?15:04
mathiazttx: level 3?15:04
ttxnobody running in circles15:04
nealmcb:)15:04
jiboumansmathiaz: you're woefully underprepared for an invasion of your borders sir15:04
zuldrinking yet?15:05
ttxDefCon 2 would be "pilots scramble to their aircrafs15:05
mathiazjiboumans: totally - where I live there isn'15:05
ttxand DefCon 1 would be permission to engage15:05
mathiazjiboumans: totally - where I live there isn't any point in getting prepare for an invasion15:05
zulrelease lucid....drunk fix later..15:05
ttxthe absinthe bottle is still full15:05
* hggdh meanwhile drinks a marvelous Brazilan coffee15:05
jiboumansttx: any known issues come up that will be release noted or SRU'd early?15:05
* zul hands mathiaz a book about the war of 181215:06
DavieyI 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
ttxyes15:06
jiboumansDaviey: i must have not gotten that memo15:06
ttxI updated https://wiki.ubuntu.com/ServerTeam/Meeting15:06
mathiazjiboumans: you'll get - don't worry15:06
ttxah15:06
ttxI mean https://wiki.ubuntu.com/ServerTeam/ReleaseStatus15:06
jiboumansttx++ excellent15:07
ttxWe have 4 things ion the release note list15:07
ttx4 early targets for SRU15:07
ttxIf you see anything missing, please shout15:07
ttx(now)15:07
hggdhttx, may I propose bug 567592 also?15:07
ubottuLaunchpad bug 567592 in plymouth "rm: cannot remove `/var/lib/urandom/random-seed': Read-only file system" [Undecided,New] https://launchpad.net/bugs/56759215:07
jiboumansfor the logs:15:07
jiboumans423252 (breaks NSS using LDAP+SSL on upgrades from Hardy)15:07
jiboumans571057 (breaks OpenLDAP configs on upgrades from Lucid dev milestones)15:07
jiboumans570805 (regression in Ubuntu Server installation times on ext4)15:07
jiboumans557429 (potential breakage in a scenario with degraded RAID arrays being assembled)15:07
zulttx: i know at least one other php one15:07
ttxhggdh: for release noting ?15:08
mathiazbug 423252 <- that won't be SRUable in the short time15:08
ubottuLaunchpad bug 423252 in sudo "NSS using LDAP+SSL breaks setuid applications like su and sudo" [High,Confirmed] https://launchpad.net/bugs/42325215:08
hggdhttx: for SRU-ing15:08
mathiazas there isn't a confirmed fix15:08
hggdhearly15:08
jiboumanshang on, those were the release note bugs15:08
ttxmathiaz: right that's why it's on the "under investigation" list15:08
jiboumansthese are the SRUable bugs:15:08
jiboumanseucalyptus: 567371,565101 (kirkland)15:09
jiboumanstomcat6: 563642 (ttx)15:09
jiboumansphp5: 541439 (zul)15:09
jiboumansvmbuilder: 536942,386463,493020,497258,517067,535397,536940,539727,540446,524020 (soren)15:09
zulheh soren has some work to do15:09
ttxyes, volcano smoke prevented him to fix those in time15:09
kirklandjiboumans: i'm prepping a eucalyptus upload right now that addresses 566793, 567371, 56510115:09
ttxhggdh: ok, I'll look into it15:09
ttxkirkland: i'll add the missing bugreference, thanks for the pointer15:10
jiboumans[ACTION] hggdh, zul to get their release note/early SRU bugs known to ttx15:10
MootBotACTION received:  hggdh, zul to get their release note/early SRU bugs known to ttx15:10
jiboumansttx: any other news from the war room?15:10
zulttx: what about the crypt lvm bug?15:10
ttxzul: the repeated prompt ?15:10
zulyeah shouldnt that be in the release notes as well?15:10
ttxzul: I don't think so15:10
DavieyIs soren going to be able to manage the *long* list of early SRU's?15:11
ttxit sucks but it's hardly blocking anything15:11
zulttx: ack15:11
ttxDaviey: patches welcome, as usual15:11
ttxnothing else from the war room15:11
jiboumans[TOPIC] UEC release status (kirkland)15:11
MootBotNew Topic:  UEC release status (kirkland)15:11
jiboumansthanks ttx15:11
kirklandjiboumans: check15:11
kirklandjiboumans: no release critical issues15:12
ttxjust remember to mark DONE or POSTPONED the remaining work items for 10.0415:12
ttxby tomorrow eod :)15:12
jiboumans[ACTION] ALL to mark DONE or POSTPONED the remaining work items for 10.04 by Thu 29 April EOD15:12
MootBotACTION received:  ALL to mark DONE or POSTPONED the remaining work items for 10.04 by Thu 29 April EOD15:12
jiboumanskirkland: the upload you're doing will be a zero day SRU then?15:13
kirklandjiboumans: i have uploaded now15:13
=== yofel is now known as yofel_
kirklandjiboumans: it will be in lucid-proposed as soon as the ubuntu-sru team accepts it15:13
kirklandjiboumans: normally, it's supposed to bake in -proposed for ~1 week15:13
jiboumanskirkland: right, but too late for any ISOs of course15:13
jiboumansunderstood15:13
=== yofel_ is now known as yofel__
kirklandjiboumans: yes, these won't be on the 10.04 iso (but will be on 10.04.1)15:14
jiboumanskirkland: 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
=== yofel__ is now known as yofel
kirklandjiboumans: we could ask for a rush processing of the 1 week bake, since we've been testing it for nearly a week already now15:14
ttxjiboumans: those are mostly bugs you encounter running over a period of time (not installer issues) so updating is ok15:14
kirklandjiboumans: these are mostly scalability one15:14
kirklandjiboumans: i suspect as soon as people actually start deploying 10.04 UEC, we'll get some new, hard ones15:14
jiboumanskirkland: i'm sure15:15
kirklandjiboumans: i think ttx had a few more he wanted looked at15:15
ttxyes, the securitygroup thing I haven't had time to reproduce15:15
kirklandjiboumans: and smoser still has some upstarty/plymouth-ish issues, ISTR15:15
jiboumanskirkland: for ec2, surely. we'll cover that next15:15
ttxyes our images are still pretty brittle when run over UEC15:15
jiboumansthen let's cover that next15:16
jiboumans[TOPIC] EC2 release status (smoser)15:16
smosernot brittle15:16
MootBotNew Topic:  EC2 release status (smoser)15:16
jiboumansthanks kirkland, tt15:16
jiboumans*ttx15:16
smoserin most cases things are fine. under high heavy load on UEC the metadata service doesn't come up for minutes.15:16
smoserthe images don't wait long enough15:16
smoserso yes, maybe brittle15:16
jiboumansttx: i trust that is noted somewhere?15:17
ttxI meant the "can't be contacted by ssh" thing15:17
ttxjiboumans: it's difficult to releasenote it since we have trouble to understand when it hits15:17
smoserhold on. getting bugs.15:17
ttx"UEC image may fail to boot on UEC" isn't a good releasenote text15:17
smoserbug 56501815:17
ubottuLaunchpad bug 565018 in cloud-init "instance is not reachable via ssh" [High,Confirmed] https://launchpad.net/bugs/56501815:17
smoserbug 56679215:18
ubottuLaunchpad bug 566792 in eucalyptus "UEC guests sometimes fail on consuming user data (metadata service isn't ready)" [High,Confirmed] https://launchpad.net/bugs/56679215:18
ttxthe second one is under load, right15:18
smoseri hope to address 566792 sometime very soon after release, or at least part of it.15:18
ttxbut the first one can be hit on a single try, if you're unlucky15:19
smoserthe first bug (instance not reachable via ssh), i have no good explanations under what conditions it fails15:19
smoserit seems timing related.15:19
hggdh566792 seems to happen more when CLC, Walrus, and CC are on differetn machines15:19
smoserHmm..15:19
smoseri guess there should be a third bug. i will open one.15:20
smoserthe 'meta data service comes up slowly' portion of bug 566792 is easily workaroundable in image15:20
ubottuLaunchpad bug 566792 in eucalyptus "UEC guests sometimes fail on consuming user data (metadata service isn't ready)" [High,Confirmed] https://launchpad.net/bugs/56679215:20
smoserbut your boots will just take 3 minutes15:20
jiboumansbeats not booting at all15:21
smoserthe "meta data service returned empty data an http status 200" is not so easily workaroundable.15:21
smoserthat is much harder to reproduce.15:21
smoseropening bug now.15:21
jiboumanssmoser: any issues with the images themselves?15:21
smoserwell, no. :)15:21
smosernot after they're booted15:22
jiboumanssmoser++ excellent15:22
hggdher15:22
ttxjiboumans: they run relatively fine on EC215:22
hggdhthere is bug 567592, hitting plymouth, and may be germane here15:22
ubottuLaunchpad bug 567592 in plymouth "rm: cannot remove `/var/lib/urandom/random-seed': Read-only file system" [Undecided,New] https://launchpad.net/bugs/56759215:22
jiboumansttx: when you say 'relatively' i expect you can tell me when they don't?15:22
smoservery good on ec2.15:22
ttxWe could have a generic "UEC image may fail to boot on UEC" release note pointing to the bugs still in progress15:22
ttxjiboumans: I meant "comparatively"15:23
smoserhggdh, how often do you see that bug ?15:23
hggdhsmoser: every boot I have the console log I see it. I think this may play a role15:23
smoser"have the console log" ?15:24
hggdhnot the cannot remove, but the ral cause -- plymouth barfs when trying to write to a pts15:24
nealmcb 15:24
hggdhsmoser: the failed instances15:24
* nealmcb oops15:24
smoseri dont think thats true.15:24
smoseryou're saying every time you can't reach an instance it has that in it.15:25
smoser?15:25
hggdhI am saying every UEC image boot has it -- plymouth dies with a SIGSEGV15:25
hggdhand this may cause problems for mountall, and cascade15:25
smosercorrect.15:26
smoserbut not every instance fails in that bug (read only filesystem)15:26
hggdhindeed, no. But the read-only is (as Collin found) a *possible* consequence, not the cause15:26
smoserok.15:27
smoseri wasn't read-up-to-date on that15:27
hggdhthis is why I would really like to have a new UEC image with Collin's fixes, to test it again15:27
ttxhggdh: we have a fix for that already ?15:27
hggdhcjwatson just proposed fixes for it, this morning15:28
ttxright, we expect to roll Lucid UEC images regularly, so we could have an updated image with the fix quite fast if that fixes it15:29
ttxthere are a few other boot-related fixes in the queue15:29
jiboumansok, thanks for that15:30
jiboumansmoving on15:30
jiboumans[TOPIC] Weekly Updates & Questions for the QA Team (hggdh)15:30
MootBotNew Topic:  Weekly Updates & Questions for the QA Team (hggdh)15:30
jiboumansmy question: release status? :)15:30
hggdhjiboumans: seems as ready as possible, with the given exceptions (bugs) above15:30
zuljiboumans: not paniacing15:31
jiboumanshggdh: that's great news15:31
* jiboumans attaches the head back to his chicken15:31
smoserbug 571271 opened for "simple timeout issue"15:31
ubottuLaunchpad bug 571271 in cloud-init "uec images should wait longer for metadata service" [High,Triaged] https://launchpad.net/bugs/57127115:31
hggdhanother point15:31
hggdhI 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 test15:32
hggdheven more with the dpkg/fsync currently in place :-(15:33
jiboumanshggdh: engineering or machine time?15:33
hggdhboth of them15:33
hggdha re-setup usually takes some two hours, and each stress about another 2 hours15:33
jiboumansthat's costly indeed15:34
jiboumanslet's take some time at UDS to see how we can improve that timewise. if it takes extra hardware, we can probably arrange that too15:34
hggdhthank you. I will add the blueprint in a few15:35
jiboumans[ACTION] hggdh to outline testing bottlenecks for UEC testing UDS sessions15:35
MootBotACTION received:  hggdh to outline testing bottlenecks for UEC testing UDS sessions15:35
jiboumanshggdh: any ohter updates from the QA team?15:35
hggdhno, life is good now ;-)15:35
jiboumansany questions for hggdh?15:35
jiboumansi'll take that as a no15:36
jiboumans[TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)15:36
MootBotNew Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)15:36
jiboumanshggdh: thank you15:36
jjohansenhi15:36
jiboumanshi there15:36
jiboumansmy question is unchanged: release status? :)15:36
=== Claudinux_ is now known as Claudinux
jjohansenheh, well unfortunately not really changed since last week15:37
jjohansenthe kernel has been frozen and only a couple critical changes have been applied15:37
jjohanseneverything is being queued for SRU15:38
jiboumansany of those changes or SRU affecting server issues?15:38
jjohansenno15:38
jiboumansjjohansen: ok, thanks15:38
jiboumansi had one specific question about the ext4 performance degrade we saw in benchmarks15:39
jjohansenokay15:39
jiboumansthis is a public one of those:   http://www.phoronix.com/scan.php?page=article&item=ubuntu_lts_perf&num=215:39
jiboumansit's a few weeks old though; have we managed to do anything with/about that ?15:39
jjohansenhrmm, I actually haven't seen anything about that pass by but give me a sec to check with csurbi15:40
jjohansenif I recall correctly this particular test wasn't really hitting the disk but I wasn't the one looking into it15:41
jjohansenjiboumans: I will have to get back to you on specifics as csurbi isn't around atm15:42
jiboumansjjohansen: no problem. could you coordinate with ttx to see if we should release note anything?15:42
jjohansenwill do15:42
jiboumansthank you15:42
jiboumansany other questions or updates for the kernel?15:43
jjohansenone other little thing, it looks like trying to go pv-ops for EC2 will be a target for M15:43
zulcool...good luck! ;)15:43
jiboumansjjohansen: nice to hear15:44
jiboumansalright, moving on15:44
jiboumans[TOPIC] Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review (mathiaz)15:44
MootBotNew Topic:  Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review (mathiaz)15:44
jiboumansi expect very little, but best to check :)15:44
mathiazno bugs nominated for any release15:45
mathiazanything worth SRU in the last week?15:45
mathiazand next week I'll add lucid to the list15:45
mathiazso expect a longer SRU review as we go through the lucid nominations15:45
zulnope15:45
mathiazit may require more than one meeting though15:46
* jiboumans renames this the SRU meeting15:46
jiboumansmathiaz: understood and thanks15:46
jiboumans[TOPIC] Final call for blueprints for UDS Maverick15:46
MootBotNew Topic:  Final call for blueprints for UDS Maverick15:46
jiboumansStarting monday, we'll do the planning for the sessions of UDS maverick15:47
jiboumansif you'd like to have a guaranteed session slot, please make sure your blueprint is created by this Friday end of business15:47
jiboumansPlease also take a look here for currently proposed sessions at UDS: https://wiki.ubuntu.com/ServerTeam/MaverickIdeaPool15:48
jiboumansif you have any ideas, no matter how experimental, feel free to add those to the above wiki page as well15:48
jiboumans[TOPIC] Open Discussion15:49
MootBotNew Topic:  Open Discussion15:49
jiboumansplease, go ahead :)15:49
jiboumansalright, moving on15:50
jiboumans[TOPIC] New meeting time for the Maverick cycle15:50
MootBotNew Topic:  New meeting time for the Maverick cycle15:50
* hggdh really pays attention now15:51
jiboumans*drum roll*15:51
ttxlet's all act surprised !15:51
RoAkSoAxlol15:51
jiboumansGiven that release days/freezes are on Thursday, we'd like to move the meeting to Tuesday 6 pm UTC15:51
hggdhYES!15:51
jiboumansthis aligns better with west coast attendance (hi jjohansen)15:51
hggdh(sorry, ttx)15:52
ttx1800 UTC, you mean15:52
jiboumansand is one of the few slots left on the Tuesday meeting schedule15:52
jjohansenyes it does15:52
jjohansen:)15:52
jiboumansttx: if it makes you feel better15:52
jiboumansall those opposed say 'nay'15:52
ttxthat makes me feel more accurate :P15:52
jiboumansno objections, the new meeting time stands15:52
jiboumans\o/15:53
* hggdh agrees with ttx15:53
Daviey(if it's changed, the date on the ubuntu fridge cal needs updating)15:53
hggdhoh, no early mornings...15:53
jiboumans[TOPIC] Announce next meeting date and time15:53
MootBotNew Topic:  Announce next meeting date and time15:53
jiboumanskirkland, ttx and myself will be at a company meeting next week, and UDS is the week after15:53
mathiazI can run the meeting next Tuesday15:53
jiboumansis there mileage in a meeting next week, or shall we postpone till after UDS?15:53
jiboumansmathiaz: thanks for the offer. worth it for you to go through SRUs etc?15:54
ttxhggdh: oh, meetings after dinner15:54
mathiazjiboumans: yes15:54
jiboumansok, then15:54
sorenjiboumans: Will you? Even with the new meeting time?15:54
mathiazeven if it lasts just 10 minutes15:54
jiboumanssoren: i will always. not sure what i will, but i will15:54
jiboumansmathiaz: excellent15:55
jiboumansnext meeting time is Tuesday May 4th at 1800 UTC15:55
sorenjiboumans: Be at the company meeting at the time of the meeting.15:55
jiboumanssoren: technically, i'll be in a plane over the atlantic15:55
sorenMaybe my intel is wrong :)15:55
ttxsoren: your intel is wrong15:55
jiboumansthanks for highlighting that crucial distinction :)15:55
jiboumansalright all, thanks for attending15:55
jiboumans#endmeeting15:55
MootBotMeeting finished at 09:55.15:55
nealmcbsounds like mileage in that meeting to me :)15:56
Davieyjiboumans: New meeting time is long term?15:56
mathiazDaviey: yes :)15:56
Davieyokay, thanks15:56
* Daviey prods the firdge people15:56
Davieyfridge*15:56
jiboumansDaviey: thank you15:57
mvohi, meeting? or no meeting?16:01
oubiwannmvo: no meeting16:02
mvook16:02
mvothnaks16:02
* ara waves17:53
* bdmurray waves back17:53
* bladernr \0o/17:54
pedro_hola!17:59
* marjo waves17:59
ameetpo/18:00
* fader_ waves.18:00
marjo#startmeeting QA Team18:01
MootBotMeeting started at 12:01. The chair is marjo.18:01
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]18:01
marjo[TOPIC] Agenda18:01
MootBotNew Topic:  Agenda18:01
marjo# SRU testing -- sbeattie (Steve Beattie)18:01
marjo# Bug Day status -- pvillavi18:01
marjo# UDS QA Track - ara18:01
marjo[TOPIC] SRU testing -- sbeattie18:01
MootBotNew Topic:  SRU testing -- sbeattie18:01
sbeattieSRU 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 activity18:03
sbeattie* hardy: 1 new package in -proposed (sun-java6)18:03
sbeattie* dapper: no SRU activity18:03
sbeattieThere wasn't a lot of testing activity this past week18:03
sbeattieThanks to unggnu, Uri for testing SRUs.18:03
marjosbeattie: should pick up next week?18:04
sbeattiemarjo: heh, yes, will definitely pick up next week.18:04
arasbeattie, yes, with the classic after release quick SRUs18:04
marjosbeattie: anything else?18:05
sbeattiemarjo: nope that's it from me18:05
marjo[TOPIC] Bug Day status -- pvillavi18:05
MootBotNew Topic:  Bug Day status -- pvillavi18:05
pedro_On Thursday 22 we had a bug day based on Evince: https://wiki.ubuntu.com/UbuntuBugDay/2010042218:05
pedro_~30 bugs were triaged, Thanks a lot to our hug days heroes: charlie-tca, kamusin, sbarjola and yofel18:05
pedro_As for Tomorrow, our target will be the New and Confirmed bugs without a package:18:06
pedro_https://wiki.ubuntu.com/UbuntuBugDay/2010042918:06
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 Triage18:07
arais #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 time18:08
pedro_ara, yes #ubuntu-bugs is the right place18:08
arapedro_, ok, thanks18:08
pedro_that's all from here marjo18:08
marjopedro_ thx!18:08
pedro_my pleasure18:09
marjo[TOPIC] UDS QA Track - ara18:09
MootBotNew Topic:  UDS QA Track - ara18:09
arahello!18:09
arajust a quick reminder that I am waiting for blueprints to schedule in the qatrack18:10
arathis is the list of sessions that I have scheduled so far18:10
ara * Checkbox Improvements - https://blueprints.launchpad.net/checkbox/+spec/qa-m-checkbox18:10
ara * Improving ISO testing of Ubuntu and its derivatives - https://blueprints.launchpad.net/ubuntu/+spec/qa-community-m-improve-iso-testing18:10
ara * BugSquad Roadmap - https://blueprints.launchpad.net/ubuntu/+spec/qa-m-bugsquad-roadmap18:10
ara * Structured Testing Programs - https://blueprints.launchpad.net/ubuntu/+spec/qa-m-community-structured-testing18:10
ara * Improving Communication - https://blueprints.launchpad.net/ubuntu/+spec/qa-m-improving-communication18:10
ara * Improving Community Laptop Testing - https://blueprints.launchpad.net/ubuntu/+spec/qa-m-laptop-testing18:10
ara * Promoting LoCo Testing Teams - https://blueprints.launchpad.net/ubuntu/+spec/qa-m-loco-testing18:10
ara * Running Mago tests on a daily basis -  https://blueprints.launchpad.net/ubuntu/+spec/qa-m-mago-daily18:10
araif your session is not there, please, let me know18:10
sbeattieara: yeah, sorry, I still need to create the apport-udeb blueprint.18:10
arasbeattie, no worries :)18:11
araalso, you can start subscribing to those blueprints, if you want to participate in the discussion18:11
marjoara: thx for doing those18:11
sbeattieara: 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:11
arasbeattie, great!18:12
* ara really wants to participate in that one18:12
marjoara: that would be a good time to get an update on sikuli18:12
sbeattieheh, I think you're an essential attendee for that.18:12
aramarjo, indeed18:12
arathat's all from me18:13
marjoara: thx18:13
marjo[TOPIC] QA Team Workitems Status18:13
MootBotNew Topic:  QA Team Workitems Status18:13
marjohttp://people.canonical.com/~pitti/workitems/canonical-platform-qa.html18:14
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/canonical-platform-qa.html18:14
marjoas you all can see, the QA team has been very productive during Lucid18:14
marjolots of work items done & not many postponed18:15
marjothx to everyone who contributed18:15
marjowe need to keep up the momentum going into next release18:15
marjothx18:15
marjo[TOPIC] Final testing status18:16
MootBotNew Topic:  Final testing status18:16
araThere are some remaining test cases for amd6418:17
aramost of them are marked as Started18:17
marjohttp://iso.qa.ubuntu.com/qatracker/build/all/all18:17
MootBotLINK received:  http://iso.qa.ubuntu.com/qatracker/build/all/all18:17
cr3ara: I'm burning those images as we speak18:17
aracr3, nice :) thanks!18:17
bladernrara:  I'm right in the middle of one, myself18:17
fader_Same here18:17
marjoara: i tried to recruit everyone to cover all the remaining test cases including optional ones18:17
cyphermoxyup18: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 it18:18
marjothe only challenge would be http://iso.qa.ubuntu.com/qatracker/result/4133/49718:18
arasbeattie, did you read my notes on that?18:18
arasbeattie, the set up with kvm, I mean18:18
sbeattieara: yes, I'm using that as a guide, thanks!18:19
arasbeattie, great18:19
marjoara: thx for writing up your notes on that18:19
marjoand posting it18:19
hggdhmarjo: I think I can mark the UEC separate install as done -- I did it on the UEC stress tests18:19
marjohggdh: ok, go for it18:19
marjofader: thx18:20
hggdhmarjo: I am wrong -- this is the separate network topo, the one the rig cannot test right now18:20
hggdhsorry18:20
marjohggdh: oh well18:20
hggdhonly ttx and kirkland can test it, to my knowledge18:21
marjohggdh: ack18:21
ttxonly me, since it requires 2 reasonably-fasy NIC on one of the laptops -- and I don't have my rig with me18:21
ttxs/fasy/fast/18:22
hggdhmarjo: something to discuss on the blueprint I proposed for the server/QA18:22
marjohggdh: definite +118:22
hggdhfor the record: https://blueprints.edge.launchpad.net/ubuntu/+spec/server-maverick-uec-testing18:23
marjofolks: thx for pitching in; i think we're going to hit very high test coverage18:23
hggdhttx: please ask jib to approve it18:24
marjofolks: any other topics for today? if not, i propose we all go back to testing18:24
ttxhggdh: it's on our list, it will be approved18:24
marjottx: thx18:24
hggdhcool18:24
marjogoing once18:25
marjogoing twice18:25
marjomeeting adjourned18:25
marjogo lucid!18:25
marjo#endmeeting18:25
MootBotMeeting finished at 12:25.18:25
marjothx everyone!18:25
aracheers18:25
pedro_thanks18:26
=== unimix_ is now known as unimix|work
ghostcubebportal.de19:20
ghostcubedamn xchat19:20
ghostcubesorry guys19:20
* stgraber waves20:00
highvoltagehello all20:00
alkisgHi people20:00
isforinsectshi there20:00
highvoltageanyone willing to take notes? I usually do but I have a huge headace (I asume caused by internet withdrawal)20:01
stgraberI'll do it20:01
stgraberhighvoltage: is your latency back to something reasonable ?20:02
highvoltagestgraber: irssi says lag: 1.44, so it seems good enough for the meeting at least20:02
Lnshi!20:02
stgraberok ;)20:03
stgraberso I guess that meeting should probably be quite focused on the release tomorrow and UDS20:03
highvoltageI just want to say that it's an extreme relief that the release is tomorrow and that the iso ended up being in great shape20:03
alkisgMany thanks to all of you who worked hard for this release20:04
stgraberwe 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 there20:04
bencrisfordhullo everyone20:05
stgraberISO 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 ones20:05
highvoltagestgraber: according to http://www.seacom.mu/news/news_details.asp?iID=132 my connection should be coming back up in about 3 hours20:06
bencrisfordhighvoltage:  :D20:06
highvoltageso late tonight and tomorrow morning I should be able to jump in at least20:06
highvoltagestgraber: yay!20:06
stgraberhighvoltage: yeah ! will be great to have you back online completely ;)20:07
bencrisfordare we drafting the announcment in a gobby doc?  that way could eliminate errors/things getting missed out20:07
stgraberwe should do that yes20:08
highvoltagestgraber: there's two things that I keep remembering that we left out20:08
stgraberwe 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 details20:08
highvoltagestgraber: I always remember it when I'm driving and when I'm in the shower :)20:09
highvoltagewe haven't mentioned fat clients yet, that is new in lucid right?20:09
highvoltageor did we have that in karmic already?20:09
highvoltageiirc LTSP 5.2 only came in lucid20:09
stgraberproper fat client support is lucid indeed, though not enabled by default in either ubuntu or edubuntu20:10
stgraberbut probably worth mentionning at the same place as ltsp live20:10
highvoltageI 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 there20:11
* alkisg has been working with fat clients for the past months, had no problems whatsoever20:11
alkisgIt's as much there in the default install as localapps... it's an optional thing of course, but it's there20:11
highvoltagealkisg: that's really good to hear :)20:11
stgraberhighvoltage: 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 feature20:12
stgraberhighvoltage: either that or we can mention ltsp 5.2 in the list of softwares included and mention it there20:12
highvoltage*nod*20:12
stgraberso, 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
bencrisfordsounds good20:13
highvoltage+120:13
* stgraber created edubuntu-lucid-announcement for that20:15
stgraberso, next is topics for UDS, unless we have something else to discuss for tomorrow's release ?20:16
stgraberhighvoltage: what was the name of the gobby document for maverick ?20:16
stgraberhighvoltage: the one I found appears to be empty20:16
highvoltagestgraber: I'm unsure... checking...20:16
highvoltagestgraber: ah right, I emptied it :)20:18
highvoltageI moved it to the wiki page so I removed the contents so that someone wouldn't continue editing it there20:19
stgraberah yes, because it's on the wiki ;)20:19
stgraberso that's fine20:19
stgrabermaybe you should post the URL in the gobby ?20:19
stgraberthat'd make things less confusing ;)20:19
highvoltagehttps://wiki.kubuntu.org/Edubuntu/Specifications/Brainstorming/Maverick20:19
highvoltageok will do20:19
highvoltageor at least, https://wiki.ubuntu.com/Edubuntu/Specifications/Brainstorming/Maverick20:20
stgraberI 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:21
bencrisfordstgraber: think I fixed a typo in your typing, if I was wrong, please correct me!20:25
bencrisfordi didn't know whether to fix it or not :20:26
stgrabersure, feel free to correct my typos ;)20:26
bencrisfordI really feel that we should schedule the sessions ASAP20:26
bencrisfordand decide on times during this meeting20:26
stgraber(and my english as well if the grammar sounds weird ;))20:26
bencrisfordbecause that way we can make it so as many remote participants as possible can participate20:27
stgraberwell, we can't decide times, that's the tricky part20:27
bencrisfordreally..?  there is alot free on the schedule, do you get assigned times rather than choosing?20:27
stgraberwe 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 physically20:27
stgraberso to avoid conflicts with other sessions20:27
bencrisfordoh, ok :/20:27
stgraberso 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 slot20:28
* bencrisford prays to the god of UDS that he can make some of the sessions (remotely, but still)20:28
stgraberthe final schedule is usually the one displayed at 9am in the lobby ;)20:28
highvoltageheh :)20:28
bencrisford:o20:28
bencrisford:(20:28
stgraber(and it may change slightly at lunch time)20:28
bencrisfordlol20:28
mhall119oy, missed another one20:29
highvoltagestgraber: do we need a session for the remote-installer?20:29
bencrisfordits *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 evening20:29
highvoltagestgraber: hah! I was *just* about to start typing that20:30
* bencrisford thinks his little red "t" in the doc looks quite cute20:30
highvoltagestgraber: 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
stgraberhighvoltage: not sure, it's probably not worth a 1 hour session, might merge that into the last one ?20:32
stgraberor with the first one ?20:32
highvoltagestgraber: ok we can add it to installer-improvements20:33
highvoltagestgraber: these are more for sessions rather than specifications right?20:33
stgraberldap/kerberos should be already on the server team's todo list I guess20:33
stgraberwell, the idea is that for each we'll register a spec and get that scheduled (as all sessions need a spec)20:34
highvoltageok, right20:35
stgraberso ideally, each point should last more than 30min or be merged in another20:35
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:36
highvoltageok. 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 implement20:37
highvoltageit'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
highvoltagewe can probably discuss a bunch of stuff outside of 'official' sessions on #edubuntu20:38
highvoltageat least you are there so you could ask the installer/artwork/etc teams if we need quick and good feedback20:39
stgraberyeah, 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
stgrabersmaller edubuntu-specific details can be discussed off-uds20:40
stgraber(as long as it's on some kind of roadmap ;))20:40
highvoltageyep, so I guess we should at least have a session for installer plans20:41
highvoltageI'm not sure how much work adding those screenshots and descriptions would be, but it's glade files at least20:41
highvoltagewould still be nice to get some expert advice though20:42
stgraberyep, UDS should be good for that20:42
bencrisforddo the streams in the meeting rooms get recorded?  or are they just live?  or are they even doing that this time around?20:44
highvoltagebencrisford: audio is live and video recorded for later20:45
bencrisfordvideo?  in every session?20:45
highvoltagebencrisford: yep, there has been before. not sure if they'll do it for this one20:46
bencrisfordhighvoltage: I hope so, that would make things so much easier20:46
stgraberlast time it was only for a few sessions20:46
stgraberthese are marked as videotaped on the schedule20:46
bencrisfordI think I remember there being some at karmic20:46
bencrisfordbut it was mainly like the plenarys and stuff20:46
highvoltagebencrisford: I was at the karmic one and that one was very well videod20:47
bencrisfordhighvoltage: really?  I don't remember that :/20:47
bencrisfordI remember I was free all week20:47
bencrisfordso I was live streaming and IRCing20:47
highvoltagebencrisford: the video wasn't live20:48
bencrisfordhighvoltage: but I don't remember seeing it after20:49
highvoltageit came quite a bit after (like, months).20:50
highvoltageI think having that much video was just too much20:50
bencrisfordhttp://video.ubuntu.com/uds/karmic/20:51
bencrisfordis that it?20:51
bencrisfordthere is quite alot there :/20:51
bencrisfordhow'd I miss that20:51
highvoltageseems like that's just the plenaries though20:52
highvoltageaaaanyway...20:52
highvoltagesomething left for this meeting?20:52
bencrisfordhighvoltage: yes!20:54
bencrisfordI nearly forgot20:54
bencrisfordI was gonna bring up what to do about the teams blueprint and RichEd20:55
bencrisforddo 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 here20:55
highvoltagebencrisford: didn't mdke re-assign it to you?20:55
bencrisfordyes, but mdke suggested contacting him to inform him of the change and inviting him back if he wants in20:56
highvoltagebencrisford: I've tried to contact him for even months before he left canonical and couldn't get in touch with him20:56
bencrisfordwe both agreed however that that isnt that important20:56
bencrisfordok20:56
bencrisfordwell I dont see what else we can do, and it isnt exactly imperative20:57
highvoltageyou're free to try to sms him if you want, but I'm 100% sure it would be a waste of time20:57
bencrisfordok, I don't think its that important20:58
bencrisfordbut it would be decent of us to let him know whats happening with the blueprint he created20:58
bencrisfordI guess he wouldnt expect us to put this much effort into it though20:58
bencrisfordso its more than reasonable to give up I guess20:59
highvoltagebencrisford: I don't think you have to give up, if you want to work on it, please do so21:00
bencrisfordhighvoltage: work on contacting him?21:00
highvoltagebencrisford: richard hasn't been part of the project or cantactable in a very long time21:00
bencrisfordok, I understand that21:01
highvoltagebencrisford: we don't have any responsibility or commitment to find him first before moving on with anything21:01
bencrisfordhighvoltage: I think he does have a right to know, but we shouldnt go out of our way to inform him21:02
bencrisfordif 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 care21:03
highvoltagebencrisford: if it will make you feel better, send an email/sms to all his known contact details21:03
bencrisfordhighvoltage: 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 isnt21:03
bencrisfordI honestly don't feel as strongly about it as it might seem, i'm just following up what I started21:04
highvoltagebencrisford: I know why mdke suggested it, and I don't think mdke knows richard or had much interactions with him21:04
bencrisfordI do understand that, and mdke understood too once I explained21:04
bencrisfordbut I thought I should bring it up here to make sure I have done the right thing by not contacting him21:04
highvoltageyes, you did21:05
highvoltageI can't make that any cleare21:05
highvoltageI can't make that any clearer21:05
highvoltageyou21:05
highvoltage(sorry, on netbook keyboard, can't type as fast as I'd like :) )21:06
bencrisfordregarding the actual blueprint, I would suggest having an IRC "session" post-UDS to work on it21:06
bencrisfordyou guys can discuss community at UDS21:06
highvoltagesounds good21:06
bencrisfordand then I am happy to start working on it with whoever else is21:06
bencrisfordwe just need to seperate the teams into say, 3 groups?21:07
bencrisford1) No/little attention needed, 2) Necessary team (needs attention), 3) Unnecessary team (needs deletion)21:08
highvoltagelet's take it to #edubuntu since we're over our meeting time anyway :)21:08
bencrisfordwoops, so we are21:08
highvoltage(yep that sounds good)21:08
bencrisforddont forget to gong!21:08
highvoltagebencrisford: your turn!21:08
bencrisfordhighvoltage: my turn to what?21:08
highvoltageto hit the gong21:08
* highvoltage hands bencrisford the big sticky thing21:09
bencrisford:O21:09
* bencrisford is honoured21:09
bencrisford*GONGGGGG*21:09
* bencrisford puts all his strength into an almighty swing21:09
highvoltagenice one21:09
bencrisford:D21:09
=== johnc4511 is now known as johnc4510
=== swoody_ is now known as swoody

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!