[15:57]  * slangasek waves
[15:57]  * marjo waves
[15:57] <ScottK> o/
[15:58]  * apw fades in
[15:58] <kane_> \\o o// \o/
[15:59]  * pgraner 0/
[15:59]  * asac waves
[15:59] <pitti> o/
[15:59] <mdz> \o
[16:00]  * ogra lurks
[16:02] <slangasek> #startmeeting
[16:02] <MootBot> Meeting started at 10:02. The chair is slangasek.
[16:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:02] <pitti> hey slangasek
[16:03] <slangasek> so as I mentioned in the email w/ the agenda, this meeting should be fairly focused on 1) specs that need to be discussed with the team as a whole for any reason, and 2) making sure we're on track for alpha-1, which is sneaking up on us next week
[16:03] <slangasek> [TOPIC] QA Team
[16:03] <MootBot> New Topic:  QA Team
[16:04] <marjo> * Reminder: If you change the name or URL of your daily builds and you don't
[16:04] <marjo> file a bug against the ubuntu-qa-website to fix the ISO tracker, your build
[16:04] <marjo> won't appear properly in the ISO tracker.
[16:04] <marjo> * Hardware testing
[16:04] <marjo> http://people.canonical.com/~fader/hw-testing/current.html
[16:04] <marjo> Netbooks:
[16:04] <marjo>     passed:   8 (62%)	failed:   1 ( 7%)	untested: 4 (31%)
[16:04] <marjo> Laptops:
[16:04] <marjo>     passed:   21 (78%)	failed:   2  ( 7%)	untested: 4  (15%)
[16:04] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:04] <marjo> Servers:
[16:04] <marjo>     passed:   22 (42%)	failed:   0  ( 0%)	untested: 31 (58%)
[16:04] <marjo> Desktops:
[16:04] <marjo>     passed:   12 (100%)	failed:   0  (  0%)	untested: 0  (  0%)
[16:04] <marjo> Failures under investigation.
[16:05] <mdz> wow, lots of testing has happened since the last report I saw, that's great
[16:05] <mdz> I guess we got better ISOs
[16:05] <marjo> mdz: yes, last minute results from fader
[16:05] <marjo> fader: thx
[16:05] <fader_> mdz: Yes, a lot more is testable now :)
[16:06] <slangasek> marjo: have there been changes to daily build urls this cycle?  only the CD image team has access to change these...
[16:06] <mdz> it's also fantastic to see test results flowing so early in the cycle, well done
[16:06] <marjo> mdz: thx
[16:07] <marjo> slangasek: we just want to make sure that the iso tracker has the right info in prep for next week
[16:07] <marjo> testing
[16:07]  * slangasek nods
[16:07] <cjwatson> from the testing, there seems to be a slight problem with the bug-filing methodology
[16:07] <mdz> are there any updates to the release manifest for lucid vs. karmic?
[16:08] <cjwatson> the only bug filed is bug 491999, which is filed against an upstream product in such a way that no Ubuntu developer is subscribed
[16:08] <mdz> (has a release manifest been created?)
[16:08] <cjwatson> I'll give it an appropriate Ubuntu task, but you might want to watch out for this in future
[16:09] <slangasek> mdz: has not been created yet; I can make sure that gets done today.  We have at least one manifest change this cycle, unr -> une, but I'm not sure where we are in that process currently
[16:09] <slangasek> [ACTION] slangasek to create lucid release manifest
[16:09] <MootBot> ACTION received:  slangasek to create lucid release manifest
[16:09] <fader_> cjwatson: Sorry, I missed the product it was filed against; I'll try to look out for that going forward
[16:09]  * cjwatson wonders if he offended moustafa somehow ...
[16:10] <slangasek> [ACTION] slangasek to check whether unr->une rename is ready to happen for alpha-1
[16:10] <MootBot> ACTION received:  slangasek to check whether unr->une rename is ready to happen for alpha-1
[16:10] <cjwatson> fader_: that's ok, just wanted to point it out
[16:10] <fader_> cjwatson: Thanks!
[16:10] <mdz> fader_, if you always use ubuntu-bug to file the bugs (which is best practice anyway), it avoids this problem
[16:10] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-12-04
[16:10] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-12-04
[16:11] <slangasek> (oops, shoulda had that at the beginning of the meeting)
[16:11] <fader_> mdz: Unfortunately the firewall in the lab does not currently allow this; I'll see if I can get that changed
[16:11] <slangasek> marjo: is #
[16:11] <slangasek> marjo: is lucid-qa-checkbox-desktop-experience-tests something we should still expect to land for alpha-1?
[16:11] <marjo> * UbuntuSpec:lucid-qa-checkbox-desktop-experience-tests
[16:11] <marjo> https://blueprints.edge.launchpad.net/ubuntu/+spec/lucid-qa-checkbox-desktop-experience-tests
[16:11] <marjo> Status: cr3 is working on integrating the dx team ppa and lifeless is
[16:11] <marjo> progressing with the reporting piece
[16:12] <marjo> slangasek: yes
[16:12] <slangasek> ok; that will be in by Tuesday, so it's not going on during ISO prep?
[16:13] <marjo> slangasek: pls explain
[16:13] <mdz> marjo, he asked if it was landing for alpha 1; to do that it needs to be in by Tuesday
[16:13] <mdz> it sounds like it's probably not ready
[16:14] <marjo> AFAIK, it's independent of ISO prep
[16:14] <slangasek> marjo: there's a milestone freeze in place from Tuesday until the milestone release.  checkbox is on the ISOs, so any checkbox uploads related to this should be happening before Tuesday
[16:15] <cr3> if this refers to the blueprints scheduled for alpha-1, they only affect internal packages which don't need to be pushed to main
[16:15] <slangasek> ok
[16:15] <slangasek> marjo: anything else on QA?
[16:15] <cr3> slangasek: thanks for the heads up though, much appreciated!
[16:15] <marjo> * UbuntuSpec:lucid-qa-checkbox-integrate-regression-testing
[16:15] <marjo> https://blueprints.edge.launchpad.net/ubuntu/+spec/lucid-qa-checkbox-integrate-regression-testing
[16:15] <marjo> Good progress
[16:15] <marjo> * Write script to branch qa-regression-testing: DONE
[16:15] <marjo> * Write script to parse QRT strings from regression suite: DONE
[16:15] <marjo> * Write script to output checkbox test definitions: DONE
[16:16] <marjo> * Add support for running suite scripts as root: DONE
[16:16] <marjo> * Write script so that it can modify the sudoers file to run regression tests with sudo: DONE
[16:16] <marjo> nice progress, so i thot i'd share it
[16:16] <marjo> that's it for QA team
[16:16] <slangasek> ok, thanks
[16:16] <cr3> maybe I could push some of those changes to main for completeness purposes, but the dx testing will not depend on it though
[16:16] <slangasek> [TOPIC] Desktop Team
[16:16] <MootBot> New Topic:  Desktop Team
[16:16] <slangasek> pitti: hi
[16:17] <pitti> This week we got spec drafting and review and work item creation to some 95%. Our release status page (https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus) has an overview about the changes we plan for lucid, as well as the
[16:17] <pitti> usual bug status
[16:17] <pitti> We did a lot of investigation and discussion around desktop startup speed and landed the first set of fixes.
[16:17] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:17] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:17] <pitti> We also prepared the X.org halsectomy, hoping that we can drop hal from the default installation in alpha-1. This should give us maximum testing for the udevification, as well as decrease boot time.
[16:17] <pitti> One release radar bug which is in jeopardy for alpha-1 is bug 491162, but it doesn't affect a lot of people, so I don't consider it an alpha-1 breaker (moved to a2)
[16:18] <pitti> also of note is bug 491136 which breaks jockey completely (but no other pk consumers for some reason)
[16:18] <pitti> but I hope to get that nailed today or Monday
[16:18]  * slangasek nods
[16:19] <slangasek> looks good
[16:19]  * pitti adds the jockey bug to the page, sorry
[16:20] <slangasek> pitti: btw, have you seen my comments regarding seed pulling in 50MB of -dev packages (and making gnome-games uninstallable)?
[16:20] <pitti> slangasek: uh, still? shouldn't happen for the CD any more
[16:20] <slangasek> I followed up on the MIR bug, haven't noticed any further activity in getting that resolved
[16:20] <pitti> I saw it for the dvd
[16:20] <slangasek> oh, how was it fixed?
[16:20] <pitti> those games were unseeded
[16:20] <pitti> we don't want them in the default install anyway
[16:20] <slangasek> ok
[16:20] <slangasek> agreed :)
[16:20] <pitti> I'll double-check
[16:21] <pitti> still needs resolution for the DVD, of course
[16:21] <pitti> seed was fixed today
[16:21] <pitti> (as in the package "seed", for the clutter stuff)
[16:21] <slangasek> ok, so I'm just behind a day
[16:21] <slangasek> anything else for desktop?
[16:21] <pitti> -dev dependencies still need to be addressed; there was something weird about them shipping gir data, which should probably move to the lib themselves
[16:21] <ogra> isnt "seed" also used by some webkit stuff ?
[16:21] <pitti> not from me; any qeustions?
[16:22] <pitti> ogra: correct, like epiphany
[16:22] <slangasek> ogra: not anything that we have in main, though
[16:22] <pitti> it's JS bindings for webkit
[16:22] <ogra> ubiquity-slideshow ?
[16:22] <pitti> that's in main, and seed wasn't in karmic
[16:22] <ogra> k
[16:23] <slangasek> (I still think the lot of seed should be kept out of main as long as possible, and that games written natively in JS can stay far away from the supported set, but.)
[16:23] <ogra> i just thought i saw some deps there during armel researches
[16:23] <slangasek> [TOPIC] DX
[16:23] <MootBot> New Topic:  DX
[16:23] <pitti> slangasek: WFM
[16:23] <slangasek> anyone from DX team here?
[16:24] <slangasek> [TOPIC] Mobile
[16:24] <MootBot> New Topic:  Mobile
[16:24] <asac> hi
[16:24] <slangasek> asac: hi
[16:24] <asac> https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:24] <slangasek> [LINK] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:24] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:24] <asac> so on specs we have work items everywhere
[16:24] <asac> and almost all are finished drafting/approval
[16:24] <ogra> masses :)
[16:24] <asac> hehe
[16:24] <asac> another topic brought up is: imx51 buildlivefs commands in the crontab on antimony arent respected (ogra)
[16:25] <ogra> right, i dont know why and would appreciate help of someone from ubuntu-cdimage here
[16:25] <cjwatson> remind me after the meeting and I'll help
[16:25] <ogra> as you know we separated the armel buildlive calls in the crontab entries in karmic
[16:25] <ogra> thanks
[16:26] <asac> action required?
[16:26] <slangasek> [ACTION] ogra and cjwatson to debug imx51 buildlivefs problem on antimony
[16:26] <MootBot> ACTION received:  ogra and cjwatson to debug imx51 buildlivefs problem on antimony
[16:26] <ogra> ++
[16:26] <asac> Reminder: armel/thumb2 build failure procedure: https://wiki.ubuntu.com/ARM/Thumb2#How%20to%20deal%20with%20build%20failures
[16:27] <asac> we will triage them and go through build failures on our own, but if you see stuff break after upload it would be great to use that tagging/subscription model
[16:27] <slangasek> asac: I note that the RC bugs list on https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid includes bugs that aren't targeted to lucid at all; please make sure that any bugs your team considers RC are targeted to release for tracking
[16:27] <asac> slangasek: ack.
[16:27] <asac> will ensure that in future
[16:27] <asac> on bug front:
[16:28] <asac> 319240: linux-fsl-imx51: kexec broken on imx51
[16:28] <ogra> https://wiki.ubuntu.com/ARM/Thumb2 helps if you want to fix your packages yourself
[16:28] <asac> this is currently being worked on
[16:28] <asac> it doesnt have an impact on alpha-1
[16:28] <slangasek> ogra: is that something that warrants a brief announcement on ubuntu-devel or u-d-a?
[16:28] <asac> 456659: linux-fsl-imx51: suspend/resume failure on imx51
[16:28] <asac> same here
[16:28] <ogra> slangasek, yeah
[16:28] <asac> slangasek: it was announced to mobile. we should forward it
[16:28] <slangasek> who can take an action for that?
[16:29] <asac> me
[16:29] <slangasek> [ACTION] asac to announce https://wiki.ubuntu.com/ARM/Thumb2 to the broader developer community
[16:29] <MootBot> ACTION received:  asac to announce https://wiki.ubuntu.com/ARM/Thumb2 to the broader developer community
[16:29] <asac> thx
[16:29] <asac> i think thats it for this week
[16:29] <asac> ogra: ?
[16:30] <cjwatson> qt4-x11 fails to build on armel. ScottK brought this up in the foundations meeting as it blocks further work on KDE on armel. I took an action there to do some basic checking, and verified that -Wa,-mimplicit-it=thumb makes no difference (which was one theory)
[16:30] <ogra> yup
[16:30] <cjwatson> can I make this the mobile team's problem at this point?
[16:30] <cjwatson> it's reproducible on jocote
[16:30] <asac> cjwatson: is there a bug opened? we have it on our lists to address for sure.
[16:30] <cjwatson> I didn't see a bug
[16:31] <ScottK> There was one.  Let me find it.
[16:31] <cjwatson> I started trying to get a stripped-down test case for a gcc bug, but ran out of time
[16:31] <cjwatson> (the preprocessed source started out at 20000 lines or so)
[16:31] <slangasek> [ACTION] ScottK to target qt4-x11/armel FTBFS bug
[16:31] <MootBot> ACTION received:  ScottK to target qt4-x11/armel FTBFS bug
[16:31] <ogra> NCommander usually cares for qt ... i was hoping it could wait until he's back from vacation ... if thats not the case i guess someone else in mobile has to take it
[16:32] <cjwatson> somebody said ncommander had already thrown up his hands in horror. :)
[16:32] <cjwatson> (iirc)
[16:32] <ogra> heh
[16:32] <slangasek> -
[16:32] <slangasek> because it was an ICE, yes
[16:32] <asac> its not blocking our images afaik. so i think it snot blocking alpha-1
[16:32] <ogra> right
[16:32] <ogra> but the KDE community
[16:32] <cjwatson> you can construct a stripped-down compiler test case without significant gcc experience
[16:32] <slangasek> so is there an action there for the mobile team this week?
[16:33] <asac> i think not for this week. scott ensures its targetted
[16:33] <asac> we will triage it etc.
[16:33] <slangasek> ok
[16:33] <slangasek> anything else on mobile?
[16:34] <asac> no
[16:34] <slangasek> [TOPIC] Server Team
[16:34] <MootBot> New Topic:  Server Team
[16:34] <slangasek> ttx: hi
[16:34] <slangasek> asac, ogra: thanks
[16:34] <ttx> slangasek: yo
[16:34] <ttx> OK, so our very empty release status report is up at https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:35] <ttx> We mostly concentrated on meeting FeatureDefinitionFreeze deadline
[16:35] <ttx> and sorting out which specs should be alpha2 milestoned
[16:35] <slangasek> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:35] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:35] <ttx> Specs targeted to alpha2 are now all approved, I think... jib ?
[16:35] <kane_> ttx: correct
[16:35] <ttx> jib and kane are the same person.
[16:36] <slangasek> oh :)
[16:36] <ttx> The server daily started to be produced this morning
[16:36] <kane_> work items all in place, and everything looks managable. Some external deps on IS/eucalyptus for UEC automated testing.
[16:36] <ogra> schizophrenia !
[16:36] <mdz> when does the test tracker get updated?
[16:36] <slangasek> test tracker as in iso.qa.u.c?
[16:36] <ttx> when an alpha1 candidate is nominated, I suppose
[16:36] <slangasek> yes
[16:37] <ttx> slangasek: planned for Tuesday ?
[16:37] <mdz> (welcome kane[jib], this is his first release meeting)
[16:37] <mdz> slangasek, yes
[16:37] <slangasek> ttx: correct
[16:37] <ttx> Not so much testing so far, nothing nominated or reported against lucid dailies
[16:37] <hfhgfg> ne diyorsun
[16:37] <mdz> ttx, has anyone tried the dailies yet?
[16:38] <mdz> (I've got one in progress right now, but about all I can say is that it is able to start installing the base system)
[16:38] <ttx> mdz: I didn't. I thought they would start to be generated next week
[16:38] <ttx> and just discovered they were already up
[16:38] <cjwatson> I have
[16:38] <ttx> Colin to the rescue :)
[16:38] <cjwatson> although I was testing with a modified eucalyptus
[16:39] <cjwatson> initial smoke-test was fine apart from a glitch in kernel installation (bootloader installed too early), which I think I've fixed now
[16:39] <mdz> cjwatson, for lucid+1, the server team will need to learn the art of crafting ISOs with a modified eucalyptus
[16:39] <cjwatson> *I* don't bother crafting ISOs with a modified eucalyptus
[16:40] <cjwatson> I inject it on the fly :)
[16:40] <ttx> cjwatson: I could use that art for lucid+0
[16:40] <mdz> cjwatson, whatever you do, they need to know how to do it also ;-)
[16:40] <cjwatson> but I'm only working on eucalyptus-udeb, which is a lot easier
[16:40] <mdz> the server installer prompts for a linux command line when installing grub
[16:40] <cjwatson> mdz: yes, that's what I fixed
[16:40] <cjwatson> TBH, just pointing you guys at https://help.ubuntu.com/community/InstallCDCustomization is probably all you need
[16:41] <mdz> ah, lovely
[16:41] <cjwatson> it will be more than you need but it's probably not efficient for me to reiterate the necessary bits
[16:41] <ttx> cool
[16:41] <mdz> I'd like to script the lot of it sometime
[16:41] <cjwatson> I've been meaning to do that since warty
[16:42] <mdz> dwim.sh lucid-server-i386.iso eucalyptus_blar.changes
[16:42] <cjwatson> (which means, realistically, that I'm never going to get round to it ...)
[16:42] <mdz> I started on it once upon a time but never finished
[16:43] <cjwatson> I think it's easier now that we (I think) don't worry about the Release.gpg signature on CDs
[16:43] <ttx> mdz: would that task fit your new position ? :)
[16:43] <cjwatson> it's in the image but I think you can just delete it and it will work
[16:43] <mdz> ttx, only in that I might have free time once in a while ;-)
[16:43] <cjwatson> used to be you had to sneak in a new key as well
[16:43]  * mdz stops wandering on this tangent
[16:44] <mdz> cjwatson, so apart from the kernel bit, the server daily didn't emit any smoke?
[16:44] <slangasek> anything else on server?
[16:44] <ttx> so obviously we'll do wider testing early next week, and formalize it as soon as we have a candidate on the test tracker
[16:44]  * slangasek nods
[16:44] <cjwatson> mdz: no, not that I tested it very hard
[16:45] <ttx> I need to validate that eucalyptus is not too broken from 1.6.1 + java libraries upgrades
[16:46] <ttx> sladen: nothing from my side
[16:46] <cjwatson> I got past the first reboot then threw away the vm
[16:46] <mdz> yes, iirc it wasn't tested substantially prior to upload
[16:46] <mdz> (euca 1.6.1)
[16:46] <slangasek> ttx: do we expect eucalyptus to be working for alpha-1, or is it a target of opportunity?
[16:46] <mdz> slangasek, it is expected to work
[16:46] <ttx> slangasek: if we are lucky, it might
[16:46] <slangasek> ("target of opportunity" would seem to be consistent with our normal alpha milestone handling)
[16:47] <ttx> slangasek: if it doesn't work, then it's a bug.
[16:47] <slangasek> certainly
[16:47] <mdz> it may be at 1.6.1 (current stable) if the latest snapshot isn't working yet
[16:47] <slangasek> I'm asking whether I should expect people to be in panic mode next week if it doesn't :)
[16:47] <mdz> that's the version which was uploaded this week
[16:47] <mdz> (FWIW my server install completed and boots)
[16:48] <mdz> update-motd seems to be busted
[16:48] <mdz> nothing more from me
[16:48] <slangasek> [TOPIC] Kernel Team
[16:48] <MootBot> New Topic:  Kernel Team
[16:48] <slangasek> mdz, ttx, kane[jib]: thanks
[16:48] <slangasek> apw: hi
[16:48] <apw> ..
[16:49] <apw> Overall Kernel Team status is summarised at the URL below, including the items called out in the agenda.  AppArmor is currently not ready for Alpha-1, I am hoping to get updated bit before monday and get it uploaded.
[16:49] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:49] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:49] <apw> Blueprints: the majority of our blueprints are now approved and in most cases started.  Four are still waiting on approval, but we expect to have those complete shortly.   The first is basically complete, just waiting on actual approval.  The second needs buy-in from other teams.  The last two are investigative efforts and not likely to be producing any release items.
[16:49] <apw> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-lucid-kms
[16:49] <apw> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-lucid-new-kernel-on-lts
[16:49] <apw> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-lucid-suspend-resume
[16:49] <apw> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-devicetree-quirks
[16:49] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-lucid-kms
[16:49] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-lucid-new-kernel-on-lts
[16:49] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-lucid-suspend-resume
[16:49] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-devicetree-quirks
[16:49] <apw> The mainline 2.6.32 kernel has just released and we have just uploaded the Ubuntu kernel, so we should have that for Alpha-1.
[16:49] <apw> ..
[16:52] <slangasek> apw: who are you awaiting buy-in from on kernel-lucid-new-kernel-on-lts ?
[16:53] <apw> pgraner, there was tie in with other teams ... who was that
[16:53] <apw> slangasek, i don't think there are any release dependancies right nwo for it
[16:53] <apw> this cycle is policy only, and 'not doing things to break it', we won't have them till next cycle
[16:53] <slangasek> fair enough
[16:54] <apw> i'll add a section to the release status for these four and put something more formal down about them
[16:54] <pgraner> slangasek: tie ins are with support, release mgt etc...
[16:54] <slangasek> 355232, "unlikely to make alpha-1" - change the milestone then, if it shouldn't be a blocker?  (I guess it's importance: low anyway, hadn't caught that when preparing the agenda)
[16:55] <apw> yep, if its not going to hit, i'll push it out, should know in a few hours
[16:55] <slangasek> ok
[16:55] <slangasek> anything else for kernel?
[16:55] <apw> nothing from me
[16:55] <slangasek> [TOPIC] Security Team
[16:55] <MootBot> New Topic:  Security Team
[16:56] <slangasek> apw, pgraner: thanks
[16:56] <pgraner> slangasek: np
[16:56] <jdstrand> https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus
[16:56] <jdstrand> not that much to report
[16:56] <jdstrand> we've started a few things, and don't have any blockers
[16:56] <slangasek> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus
[16:56] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus
[16:56] <pitti> distro-wise security threat level: GREEN
[16:56] <pitti> ?
[16:57] <jdstrand> not from me
[16:57] <slangasek> [TOPIC] Foundations Team
[16:57] <MootBot> New Topic:  Foundations Team
[16:58] <slangasek> jdstrand: thanks
[16:58] <cjwatson> So far we've mostly concentrated on getting blueprints finished, and to my knowledge we now have a more or less complete set of work items:
[16:58] <slangasek> cjwatson: hello
[16:58] <jdstrand> sure :)
[16:58] <cjwatson> [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[16:58] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[16:58] <cjwatson> The next thing to do here is to address the pile of unassigned work items (the bulk of these are just down to inadequate bookkeeping) and do some balancing across the team.
[16:58] <cjwatson> For Alpha 1 we hope to have:
[16:58] <cjwatson>  * working installers across the board (we've had more time than usual to prepare this time round, and it's looking reasonable)
[16:58] <cjwatson>  * a decent start on the boot experience work (foundations-lucid-boot-experience; some ordering issues with the splash screen, but we have a plausible design)
[16:58] <cjwatson>  * as much as possible of foundations-lucid-uec-installer-enhancement, which the server team will otherwise be blocked on
[16:58] <cjwatson> We've also been making some progress on the underpinnings of forthcoming software-center work.
[16:58] <cjwatson> I haven't caught up on bugs at all yet. If there's anything milestone-urgent, please shout ...
[16:58] <cjwatson> (thanks to apw for wiki-status scripting)
[16:59] <cjwatson> oh, and by my comment on bugs I mean that most of the alpha-1 bugs at this point seem to be opportunistic milestoning by developers, so I'm not worrying about them too much
[16:59] <slangasek> there are a number of targeted bugs for foundations, but I suspect they need some gardening; nothing that looks to me like it would block the milestone prep
[17:00] <cjwatson> right, bug gardening has been low on my list so far
[17:01] <slangasek> 462169> probably gets re-milestoned, I can make the intended change for lucid but the SRU validation failed so I apparently still don't understand the real issue
[17:01] <slangasek> anything else on foundations, then?
[17:02] <slangasek> (houses, shops...)
[17:02] <cjwatson> I had a question for DX but they don't seem to be here
[17:02] <cjwatson> so nothing else from me at least
[17:02]  * slangasek nods
[17:02] <slangasek> [TOPIC] MOTU
[17:02] <MootBot> New Topic:  MOTU
[17:02] <ScottK> The bug for the qt4-x11 related ICE on armel is Bug 490391
[17:02] <ScottK> I was on a work telcon during desktop, so I also have a little Kubuntu news to report
[17:03] <ScottK> For Kubuntu KDE SC 4.4 beta 1 was released today.
[17:03] <cjwatson> ah, good, Dave Martin is way ahead of the request I made earlier
[17:03] <ScottK> We are currently blocked on a needed patch for qt4-x11 (unrelated to armel).
[17:03] <ScottK> The patch is being developed, but the developer is unfortunately priorizing exams over FOSS development
[17:04] <ScottK> So it may be a bit before we have it.
[17:04] <ScottK> I still expect to have the beta in for alpha 1, but it's getting a bit sporting.
[17:04] <ScottK> For MOTU our only significant item right now is the spec to remove unbuildable binaries.
[17:05] <ScottK> We have the rebuild results on ubuntuwire.com now and we just need to work through them to get a list of what to kill.
[17:05] <ScottK> That's all I have
[17:06] <slangasek> unbuildable binaries> ah, great!
[17:06] <slangasek> anything else for MOTU?
[17:06] <ScottK> Not unless there are questions.
[17:07] <slangasek> (... what does that agenda item need to change to under archive reorg?)
[17:07] <ScottK> cjwatson and I have some archive reorg stuff to do, but it doesn't affect the release
[17:07] <ScottK> Let me look
[17:07] <slangasek> ScottK: I just meant, if we're not going to have "MOTU" anymore, what do I put in the agenda :)
[17:07] <cjwatson> slangasek: "MOTU", as agreed at UDS
[17:07] <slangasek> oh, ok
[17:08] <cjwatson> (or "Community development" if we really want I suppose but it's a bit wordy)
[17:08] <ScottK> The work cjwatson and I have to do is to document this.
[17:08] <slangasek> [TOPIC] AOB
[17:08] <MootBot> New Topic:  AOB
[17:08] <slangasek> anything else we need to get out before alpha-1?
[17:08] <cjwatson> does anyone know how well-gardened the DX specs are?
[17:08] <ogra> working images :)
[17:08] <cjwatson> I was a bit confused by some items in the dx-lucid-xsplash spec, and their timings
[17:08] <ScottK> I know work is ongoing on at least some of them.
[17:09] <slangasek> no idea here
[17:09] <slangasek> robbiew: ^^ ?
[17:09] <pitti> I still seem them being written, but I didn't really follow up on them yet, sorry
[17:09] <ScottK> There was a binary incompatible kdelibs change needed for one of them and it hit KDE svn today
[17:09] <pitti> "seen"
[17:09] <cjwatson> specifically the requirement for a MIR of xsplash, which is already in main; and a MIR of plymouth *after* it's supposed to go into the default install
[17:09] <robbiew> slangasek: dbarth is your best bet on that stuff
[17:09] <robbiew> I know the specs are being attended to
[17:09] <cjwatson> and the fact that it's milestoned for well after a foundations spec that depends on it
[17:10] <slangasek> heh
[17:10] <slangasek> is there an action there, then?  Someone to follow up with dbarth about these timeline mismatches?
[17:11] <pitti> will ask him
[17:11] <cjwatson> thanks
[17:11] <slangasek> [ACTION] pitti to check with dbarth about spec delivery timeline mismatches
[17:11] <MootBot> ACTION received:  pitti to check with dbarth about spec delivery timeline mismatches
[17:11] <slangasek> pitti: thank you
[17:11] <slangasek> anything else?
[17:11] <slangasek> #endmeeting
[17:11] <MootBot> Meeting finished at 11:11.
[17:11] <slangasek> thanks, all
[17:12] <ogra> thanks slangasek
[17:12] <pitti> thanks all