[15:57]  * marjo waves
[15:59]  * bladernr_ waves back
[15:59]  * ameetp waves
[16:00]  * ttx waves
[16:00] <robbiew> \o/
[16:00]  * apw looks acout blearily
[16:00] <cjwatson> hi
[16:01]  * slangasek waves
[16:01] <slangasek> #startmeeting
[16:01] <MootBot> Meeting started at 10:01. The chair is slangasek.
[16:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:01] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-02-26
[16:01] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-02-26
[16:01] <slangasek> [TOPIC] QA Team
[16:01] <MootBot> New Topic:  QA Team
[16:02] <slangasek> marjo: you're on :)
[16:02] <marjo> * Lucid Alpha 3 Test Report
[16:02] <marjo> 2010-02-26
[16:02] <marjo> = Summary =
[16:02] <marjo> == Test Coverage ==
[16:02] <marjo> Mandatory Testcase Coverage: 138/180 = 76.67%
[16:02] <marjo> Optional Testcase Coverage: 3/19 = 15.79%
[16:02] <marjo> Image Coverage: 32/32 = 100%
[16:02] <marjo> [16:02] <marjo> 19 Test Failures
[16:02] <marjo> Failure Rate 19/141 = 13.48%
[16:03] <marjo> please note image coverage of 100% thx to everyone who helped out!
[16:03] <seb128> hi
[16:03] <marjo> even with late respins of images
[16:03] <marjo> == Bugs summary ==
[16:03] <marjo> [16:03] <marjo> 59 bugs unfixed
[16:03] <marjo> High - 7
[16:03] <marjo> Medium - 6
[16:03] <marjo> Low - 2
[16:03] <marjo> Undecided - 44
[16:04] <marjo> [16:04] <marjo> 9 bugs fixed
[16:04] <marjo> High - 1
[16:04] <marjo> Medium - 4
[16:04] <marjo> Low - 1
[16:04] <marjo> Undecided - 3
[16:04] <slangasek> next time, we'll have DVDs working to make it more of a challenge ;)
[16:04] <marjo> Here's the list of bugs that were marked as "serious" by testers
[16:05] <marjo> == Serious bugs found during testing ==
[16:05] <marjo> Sorted by status from New to Fix Released
[16:05] <marjo> #527828 | kubuntu oem-config 'No valid steps.'
[16:05] <marjo> ubiquity (Ubuntu)                      | Undecided | New
[16:05] <marjo> #528331 | [Lucid Kubuntu] Ubiquity crashes in PartMan.py when choosing manual partitioning and creating new partition - NameError: global name 'partman' is not defined
[16:05] <marjo> ubiquity (Ubuntu)                      | Undecided | New
[16:05] <marjo> #528346 | Impossible to select in wich disk install to (resize)
[16:05] <marjo> ubiquity (Ubuntu)                      | Undecided | New
[16:05] <marjo> #526626 | [Alpha 3 Testing] Ubuntu Logo on UNE doesn't minimize applications and show Launcher anymore
[16:05] <marjo> go-home-applet (Ubuntu)                | Undecided | New
[16:05] <marjo> #527447 | [Lucid Netbook Alpha 3] env crashed with SIGSEGV in setlocale()
[16:05] <marjo> coreutils (Ubuntu)                     | Medium    | New
[16:05] <marjo> #527972 | [Lucid Alpha 3] usb-creator.exe does not accept ISO selection on Windows XP system
[16:05] <marjo> usb-creator (Ubuntu)                   | Undecided | New
[16:05] <marjo> #527148 | dove fails to shutdown
[16:05] <marjo> linux-mvl-dove (Ubuntu)                | Undecided | New
[16:05] <marjo> #527870 | karmic -> lucid CDROM only upgrade fails
[16:05] <marjo> libsdl1.2 (Ubuntu)                     | Undecided | New
[16:05] <marjo> update-manager (Ubuntu)                | Undecided | New
[16:05] <marjo> libsdl1.2 (Ubuntu Lucid)               | Undecided | New
[16:05] <marjo> update-manager (Ubuntu Lucid)          | Undecided | New
[16:06] <marjo> #527848 | [Lucid] ubi-partman failed with exit code 141 during manual partitioning
[16:06] <marjo> ubiquity (Ubuntu)                      | Undecided | New
[16:06] <marjo> #527115 | [Lucid Xubuntu] Can not perform an upgrade using "update-manager -d"
[16:06] <marjo> update-manager (Ubuntu)                | Undecided | New
[16:06] <marjo> #524439 | 20100219 Server ISO fails to set up console keyboard correctly
[16:06] <marjo> console-setup (Ubuntu)                 | High      | Triaged
[16:06] <marjo> console-setup (Ubuntu Lucid)           | High      | Triaged
[16:06] <marjo> #528034 | Ubiquity crash on Lucid alpha 3 20100225 Kubuntu
[16:06] <marjo> ubiquity (Ubuntu)                      | Undecided | Incomplete
[16:06] <marjo> #527377 | on resize mode i can't choose in which disk install to
[16:06] <marjo> gparted (Ubuntu)                       | Undecided | Incomplete
[16:06] <marjo> #527377 | on resize mode i can't choose in which disk install to
[16:06] <marjo> gparted (Ubuntu)                       | Undecided | Incomplete
[16:06] <marjo> #458482 | usb drives imaged with usb-creator fail to boot on some systems
[16:06] <marjo> usb-creator (Ubuntu)                   | High      | Confirmed
[16:06] <marjo> #510524 | Multiple freeze during boot
[16:06] <marjo> plymouth (Ubuntu)                      | High      | Confirmed
[16:06] <marjo> #510524 | Multiple freeze during boot
[16:06] <marjo> plymouth (Ubuntu)                      | High      | Confirmed
[16:06] <marjo> #527832 | [Lucid] Ubiquity shuts off my monitor during the startup to live environment
[16:06] <marjo> ubiquity (Ubuntu)                      | Undecided | Confirmed
[16:06] <marjo> #527932 | [Lucid Kubuntu] Ubiquity crashes in PartMan.py when choosing manual partitioning - AttributeError: 'PartMan' object has no attribute 'allow_change_step'
[16:06] <marjo> ubiquity (Ubuntu)                      | High      | Fix Committed
[16:06] <marjo> #527722 | pre depends loop
[16:06] <marjo> upstart (Ubuntu)                       | Medium    | Fix Committed
[16:06] <marjo> sorry about very long listing!
[16:07] <marjo> * Hardware testing
[16:07] <marjo> http://people.canonical.com/~fader/hw-testing/current.html
[16:07] <marjo> Netbook:
[16:07] <marjo>   	passed:   9 (70%) failed:   1 (15%)	untested: 3 (15%)
[16:07] <marjo> Laptop:
[16:07] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:07] <marjo> 	passed:   26 (100%) failed:    0 (  0%) untested:  0 (  0%)
[16:07] <marjo> Server:
[16:07] <marjo>   	passed:   52 (96%) failed:    0 ( 0%) untested:  2 ( 4%)
[16:07] <marjo> Desktop:
[16:07] <marjo> 	passed:   11 (92%) failed:    0 ( 0%) untested:  1 ( 8%)
[16:07] <marjo> the untested netbooks will be tested next week
[16:07]  * mvo will look at the update-anager problems
[16:07] <slangasek> I'm puzzled by some of those new Kubuntu partman bugs, I thought those were fixed in ubiquity before our respin
[16:08] <marjo> so, will be closer to 100%
[16:08] <cjwatson> the plugin migration in ubiquity had a fair bit of fallout, and I think we have a lot of tidying up to do there
[16:09] <marjo> cjwatson: thx for that info; will keep an eye on developments
[16:09] <marjo> for beta-1
[16:09] <mvo> http://people.ubuntu.com/~mvo/automatic-upgrade-testing/current/ <- also does not look great
[16:09] <MootBot> LINK received:  http://people.ubuntu.com/~mvo/automatic-upgrade-testing/current/ <- also does not look great
[16:10] <marjo> mvo: would like to follow up w/ you and ara on upgrades topic
[16:10] <mvo> marjo: sure, stepmaker opens up a vastly cool new test area, I'm very excited
[16:10] <slangasek> cjwatson: is that mostly affecting Kubuntu because of difference in how much testing it's gotten?  Does it make sense to have people doing tests of desktop dailies as these bugs get fixed?
[16:11] <marjo> mvo: +1
[16:11] <cjwatson> slangasek: more because of differences in code layout, but yes, if it's not entirely ridiculous I think desktop daily testing would be valuable
[16:12] <slangasek> cjwatson: for both Ubuntu and Kubuntu, or is it primarily Kubuntu we need to worry about?
[16:12] <cjwatson> I'm more worried about Kubuntu
[16:13] <slangasek> marjo: is it possible for you guys to commit some resources to doing daily install tests of Kubuntu desktop over the next few weeks?
[16:13] <slangasek> (generally only needed after there's been an ubiquity upload...)
[16:14] <marjo> slangasek: yes, we are also working w/ rickspencer3 on desktop bug finding anyway
[16:14] <marjo> slangasek: agree
[16:14] <slangasek> ok
[16:14] <slangasek> [ACTION] QA Team to retest Kubuntu desktop after ubiquity uploads
[16:14] <MootBot> ACTION received:  QA Team to retest Kubuntu desktop after ubiquity uploads
[16:14] <marjo> Specs Status
[16:14] <marjo> http://people.canonical.com/~pitti/workitems/canonical-platform-qa-lucid-alpha-3.html
[16:14] <marjo> http://people.canonical.com/~pitti/workitems/canonical-platform-qa-ubuntu-10.04-beta-1.html
[16:14] <marjo> * Checkbox Desktop Experience Tests
[16:14] <marjo>    Remaining work items moved to Beta 1
[16:14] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-platform-qa-lucid-alpha-3.html
[16:14] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-platform-qa-ubuntu-10.04-beta-1.html
[16:14] <marjo>    - Extract CPU- and I/O-data provided by bootchart
[16:14] <marjo>    - Improve test reporting for boot times
[16:14] <marjo> * Identify and implement kernel test cases to automate
[16:15] <marjo> 	Last work item moved to Beta 1
[16:15] <marjo>    - Evaluate EC2/UEC integration
[16:15] <marjo> * lucid-qa-bugs-hwdb-querying
[16:15] <marjo> 	Medium priority blueprint – work items moved to Beta 1
[16:15] <marjo> that's all folks!
[16:16] <slangasek> ok, thanks!
[16:16] <slangasek> [TOPIC] Server Team
[16:16] <MootBot> New Topic:  Server Team
[16:16] <slangasek> ttx: hi
[16:16] <ttx> slangasek: o/
[16:16] <ttx> Our updated status at : https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:16] <slangasek> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:16] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:17] <ttx> Alpha3 end status, a few work items have been deferred to beta1, a few others simply postponed to lucid+1 or never
[16:17] <ttx> Nothing left in alpha3
[16:17]  * slangasek nods
[16:17] <ttx> Beta1 planning is believed to be complete
[16:17] <ttx> http://people.canonical.com/~pitti/workitems/canonical-server-ubuntu-10.04-beta-1.html
[16:17] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-server-ubuntu-10.04-beta-1.html
[16:18] <ttx> should show what we are aiming at for beta1
[16:18] <ttx> The most impacting thing in there is probably "EBS root"
[16:18] <slangasek> hmm, when did pitti say he was resetting those lines? :)
[16:19] <ttx> slangasek: something like, today :)
[16:19] <slangasek> ah, but he's off today, oops :)
[16:19] <ttx> EBS root will probably impact EC2 deliverables
[16:20] <ttx> The rest is mostly QA/Doc/Bugfixing
[16:20] <ttx> Beta1-targeted bugs:
[16:20] <ttx> I listed those in the report, they don't all have assignees yet
[16:20] <ttx> That will be fixed by next week, obviously
[16:20] <slangasek> ttx: impact EC2 deliverables how?
[16:21] <ttx> slangasek: IIUC we would also publish a EBS root system
[16:21] <ttx> (rather than just an AMI)
[16:21] <ttx> smoser: around ?
[16:21] <smoser> here
[16:22] <ttx> could you explain impact of EBS root deliverables, if any ?
[16:22] <smoser> the end result is more ami-XXXXXXXX numbers
[16:22] <ttx> (on the release process)
[16:22] <slangasek> ah :/
[16:22] <smoser> and, then, ISO testing on those.
[16:22] <slangasek> doubles the current number?
[16:22] <smoser> yeah.
[16:23] <ttx> slangasek: other questions on that part ?
[16:24] <slangasek> are we sure that supporting both types of images as first-class Ubuntu images is the right thing to do?
[16:24] <ttx> slangasek: we expect most people to use those instead of the regular ones in a few
[16:24] <slangasek> ok
[16:24] <ttx> since they basically allow persistence for a reasonable cost
[16:25] <ttx> smoser: correct me if I'm wrong here
[16:25] <ttx> Ok, moving on to bugs affecting server, in other teams:
[16:25] <smoser> there is extremely little reason to prefer instance-store images.
[16:25] <slangasek> [ACTION] slangasek to record server-lucid-ec2-ebsroot work items related to ISO testing integration
[16:25] <MootBot> ACTION received:  slangasek to record server-lucid-ec2-ebsroot work items related to ISO testing integration
[16:25] <smoser> so, yes, we expect high usage of ebs root ami
[16:26] <ttx> bug 506297
[16:26] <ttx> That one was already revealed in alpha2 ISO testing
[16:26] <ttx> bug 524439
[16:26] <ttx> That one is more recent.
[16:27] <ttx> Both are linked to plymouthization if my understanding is correct.
[16:27] <ttx> That's about all for me. Questions ?
[16:27] <slangasek> yes; the former is covered by Keybuk's work this week (and next) to Fix Plymouth
[16:28] <slangasek> the latter will take a back seat to this for the moment, AIUI, since it has the same assignee
[16:28] <cjwatson> oh, I took over the latter
[16:28] <slangasek> oh, ok
[16:28] <cjwatson> I'll take over the bug too
[16:28] <ttx> slangasek: cool, we need those cosmetic issues fixed for beta1, since we want to call for testing quite widely
[16:28] <slangasek> wasn't sure if you had taken it and assigned it back again
[16:29] <slangasek> ttx: the plymouth stuff is so very much more than cosmetic :-)
[16:29] <slangasek> fortunately, your cosmetic issue will get fixed in the process :)
[16:29] <ttx> slangasek: the bugs are, though :)
[16:29] <slangasek> only on server; for everyone else they're crasher bugs
[16:29] <ttx> I mean, their symptoms are easily workaroundable
[16:29] <ttx> right :)
[16:29] <cjwatson> the console-setup one is chiefly complicated by the kernel sucking
[16:29] <cjwatson> I've been trying to see if I can make the kernel not suck
[16:30] <ttx> cjwatson: interestingly enough, I can't reproduce it if I have a crypted LVM
[16:30] <ttx> cjwatson: looks like the keyboard setup for password prompt kinda sticks to console
[16:30] <ttx> (not sure if that helps in any way)
[16:30] <Keybuk> that's an interesting issue
[16:31] <Keybuk> setting the keyboard layout so you can type your plymouth passphrase, but while plymouth is running
[16:31] <Keybuk> eep
[16:31] <cjwatson> ttx: that's because then the console is set up in the initramfs
[16:31] <ttx> cjwatson: ack, makes sense
[16:33] <slangasek> ok - anything further on server?
[16:33] <slangasek> [TOPIC] Mobile Team
[16:33] <MootBot> New Topic:  Mobile Team
[16:33] <slangasek> ttx: thanks
[16:33] <slangasek> asac: hi
[16:33] <asac> hey
[16:33] <asac> https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:34] <asac> [LINK] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:34] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:34] <asac> summary:
[16:34] <asac> * rootstock/qemu stabilization ... this is what occupied ogra for quite some time ;)
[16:35] <ogra> still doing
[16:35] <asac> it works, but seems qemu goes up and down a bit ... (nothing i would be worried about)
[16:35] <ogra> qemu is messy
[16:35] <asac> * thumb2 porting sprint and porting  -> we had another mini sprint this week, where we managed to scratch a few more packages from our thumb2 list
[16:36] <asac> * obviously we had alpha3 testing ... which didnt reveal really bad regressions, yay!
[16:36] <ogra> no, it rather improved :)
[16:36] <ogra> apart from the openoffice issue :)
[16:36] <asac> * openoffice "uno" investigation - round 2 - started (417009)  -> this about a bug we carry since karmic and we try to put resources in now that we are past FF
[16:36] <ogra> but that was fixed in time
[16:37] <asac> webservice specs - implementation started --- not much to implement, but we are getting pulled into other projects these weeks so we are not yet ready to upload
[16:37] <ogra> seems NCommander is on something there ... not sur its the actual issue but seems to be narrowed down a bit more
[16:37] <asac> howver, the office glue code seems to work quite well so i hope this will happen once we come back next week from a mini summit
[16:38] <asac> e.g. just a matter to package .desktop files up together with it and ensuring we dont claim too many mime-types etc.
[16:38] <asac> Image Status:
[16:38] <asac> * imx51 and dove in usable shape
[16:38] <asac> ok on Specs:
[16:38] <asac> [LINK] http://people.canonical.com/~pitti/workitems/canonical-mobile.html
[16:38] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-mobile.html
[16:38] <asac> [LINK] http://people.canonical.com/~pitti/workitems/canonical-mobile-ubuntu-10.04-beta-1.html
[16:38] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-mobile-ubuntu-10.04-beta-1.html
[16:39] <slangasek> asac: what about these specs that still have outstanding workitems for alpha-3?
[16:39] <asac> i thought i cleaned them up ... most likely some have still a bad label next to the Work items (...) and hence show up there
[16:40] <ogra> yeah, the powermanagement spec should be sorted
[16:40] <slangasek> https://blueprints.launchpad.net/ubuntu/+spec/mobile-lucid-arm-lightweightbrowser still shows as outstanding
[16:40] <asac> slangasek: that has one TODO left ... which is to complete the feature comparison (that isnt really relevant anymore)
[16:41] <slangasek> the "bad labels" are precisely what gets tracked on work item status, so please clean these up :)
[16:41] <asac> i can mark that as posponed
[16:41] <slangasek> is there a final decision there to ship firefox, then?
[16:41] <asac> slangasek: yes.
[16:41] <slangasek> ok
[16:41] <asac> slangasek: unless someone jumps in and forces us ;)
[16:42] <asac> (not expected atm)
[16:42]  * slangasek nods
[16:42] <asac> so RC Bugs:
[16:42] <asac> list grew a bit this week and we have a few more candidates which wait for verification
[16:42] <asac> we got from a3 testing
[16:43] <asac> porting list is not moving as fast as we would like to, but the list is small enough to not to be considered a risk
[16:43] <asac> main point i wanted to rais is the thumb2 rebuild we will now do
[16:43] <asac> thats not RC Bugs anymore ;)
[16:44] <asac> i will coordinate the final package list with doko who wanted to include libs in that rebuild ... then we will split it up in chunks
[16:44] <slangasek> how soon do you think the rebuilds will start, and how long is it expected to take to finish?
[16:44] <asac> and send out an announce to ubuntu-devel before starting ... also i will keep you updated before each batch
[16:44] <asac> slangasek: start on monday.
[16:44] <ogra> ... universe looks bad wrt FTBFS and thumb porting ... would be nice if there would be a MOTU team somehow that would be intrested in arm help
[16:45] <slangasek> what's the reason for splitting the rebuild into chunks?
[16:45] <asac> slangasek: time it will take: thats difficult to estimate. i hope 2- 3 month
[16:45] <asac> slangasek: in case we underestimate how long it will take i thought it might be beneficial to not pump everything in one batch
[16:46] <slangasek> oh, well, we don't have 3 months before release, even
[16:46] <slangasek> so yeah, we wouldn't want to leave a bunch of stuff in the queue still at release time
[16:46] <asac> right. thats the idea ... do it in chunks ... so we dont have stuff building when release happens ;)
[16:46] <slangasek> is this 2-3 months whole-archive, or just main?
[16:46] <asac> or even at milestones (which proabably would hit us hardest)
[16:46] <asac> slangasek: sorry 2-3 weeks ;)
[16:46] <slangasek> oh
[16:46] <seb128> you need to rebuild everything?
[16:46] <ogra> heh
[16:47] <slangasek> that's saner
[16:47] <asac> thats an optimistic estimate
[16:47] <seb128> or just thing which didn't get uploaded in lucid?
[16:47] <asac> but it shouldnt take much longer
[16:47] <ogra> seb128, only stuff that wasnt built yet
[16:47] <slangasek> and I guess that's definitely just main, then
[16:47] <seb128> ok
[16:47] <asac> seb128: just things that were not uploaded
[16:47] <asac> slangasek: right. just main
[16:47] <asac> we wont do that for universe this cycle
[16:47] <ogra> seb128, nothing from your desk for sure :)
[16:47] <asac> unless things go really quick and we see that we can push more chunks
[16:48] <slangasek> asac: will you cross-check against the list of out-of-date packages, to make sure we're not getting unnecessary reuploads of packages that already FTBFS? http://people.canonical.com/~ubuntu-archive/testing/lucid_outdate.html
[16:48] <asac> seb128: also libs that were build before some date that doko has to give me (there was a toolchain bug we need to wipe)
[16:48]  * asac checks
[16:49] <asac> slangasek: yeah we should take that into account
[16:49] <slangasek> in the meantime, we should move on, unless there's anything else to cover for Mobile?
[16:49] <asac> i will try to get those removed from the list
[16:49] <asac> not from us
[16:49] <slangasek> [TOPIC] Kernel Team
[16:49] <MootBot> New Topic:  Kernel Team
[16:49] <slangasek> asac: thanks
[16:49] <slangasek> apw: hi
[16:49] <apw> hi
[16:49] <asac> thanks
[16:50] <apw> Overall Kernel Team status is summarised at the first URL below, including the items called out in the agenda.  Alpha-3 activity shows 100% complete, I have pushed out a number of items which are highlighted in the release status.  Beta-1 activity is summarised at the second URL below, with those item pushed out shown as At Risk.  Out burndown chart is at the third URL:
[16:50] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:50] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20ubuntu-10.04-beta-1
[16:50] <apw> [LINK] http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
[16:50] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:50] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20ubuntu-10.04-beta-1
[16:50] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
[16:50] <apw> Of the pushed out items most are not critical to the release.  The main issues are well progressed, patches for the readahead scanning are in testing, discussions on builtin modules are in progress, and we hope to have the majority closed out soon.
[16:50] <apw> The bugs picked out in the agenda are progressing well.  The first we have fixes for and they should be uploaded today.  The second is likely fixed by upsteam DRM which are testing at the moment, another stong indicator that we need a drm update in lucid.  Discussion on that should be concluded by early next week.
[16:50] <apw> ..
[16:51] <slangasek> is '..' and EOF marker I'm unfamiliar with? :)
[16:52] <slangasek> (I guess so!)
[16:52] <slangasek> any questions for kernel?
[16:52] <apw> heh yeah .. is an EOF  we use that in our meetings sorry!
[16:52] <apw> i've updated the first one to fix the pushed items formatting
[16:53] <slangasek> [TOPIC] Desktop Team
[16:53] <MootBot> New Topic:  Desktop Team
[16:53] <slangasek> apw: thanks
[16:53] <slangasek> seb128: hi
[16:53]  * ScottK is here for Kubuntu
[16:54] <seb128> slangasek, hey
[16:54] <seb128> status is on https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:54] <seb128> the weekly summary for the team:
[16:54] <seb128> desktop-lucid-startup-speed considered done now (pitti still tracking one udisks item)
[16:54] <seb128> DX integration: integrated new releases, gnome-power-manager ported to the application-indicator system
[16:54] <seb128> OLS integration: rhythmbox music store in main and on by default (but server side not activated yet)
[16:54] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:54] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:54] <seb128> Desktop changes: GNOME 2.29.91, gtk client side decoration, new gnome-keyring, gwibber installed by default now (but not autostarted yet)
[16:54] <seb128>  
[16:55] <seb128> the alpha3 work items are on http://people.canonical.com/~pitti/workitems/canonical-desktop-team-lucid-alpha-3.html
[16:55] <seb128> Overall status: all alpha3 work items done excepted one desktop-lucid-social-from-the-start documentation item which can be delayed to beta;
[16:55] <seb128>  
[16:56] <seb128> the beta1 list is on http://people.canonical.com/~pitti/workitems/canonical-desktop-team-ubuntu-10.04-beta-1.html
[16:56] <slangasek> seb128: there was also an outstanding workitem for #
[16:56] <slangasek> desktop-lucid-new-firefox-support-model
[16:57] <seb128> (sorry got wireless disconnected and reconnected)
[16:57] <seb128> slangasek, the desktop-lucid-new-firefox-support-model items got done I think
[16:57] <slangasek> seb128: well, it's not marked as done
[16:57] <seb128> (from what pitti told me, checking)
[16:58] <slangasek> identify extensions to be kept in archive - binary components or importance can qualify an extension: TODO
[16:58] <seb128> hum, it's not on http://people.canonical.com/~pitti/workitems/canonical-desktop-team-lucid-alpha-3.html for some reason
[16:59] <slangasek> oops :)
[16:59] <seb128> asac, ^ do you know about that one?
[16:59] <seb128> slangasek, I don't have an answer about this one right now, will check and come back to you later
[16:59] <slangasek> seb128: sounds good
[17:00] <slangasek> [ACTION] seb128 to check on status of outstanding a3 wi for desktop-lucid-new-firefox-support-model
[17:00] <MootBot> ACTION received:  seb128 to check on status of outstanding a3 wi for desktop-lucid-new-firefox-support-model
[17:00] <seb128> otherwise for beta1
[17:00] <seb128>     * desktop applications are being ported to the new appindicator systemn around 6 of those changes are waiting for review now or will be soon and should go in lucid before beta-1
[17:00] <seb128> we should get those done next week
[17:01] <seb128> + we will need extra testing on gtk client side decoration
[17:01] <seb128> that's still new technology and could create issues
[17:01] <seb128>  
[17:01] <seb128> otherwise kubuntu summary is on the wiki too
[17:01] <seb128> not sure if somebody from the kubuntu team usually speak for those ;-)
[17:02] <slangasek> ScottK: anything you want to add regarding Kubuntu?
[17:02] <ScottK> For Kubuntu the main thing is getting kdebindings fixed on armel
[17:02] <ScottK> That's planned for next week.
[17:02] <ScottK> We're also still looking to get the KDE Firefox patches in.
[17:02] <slangasek> that should help clean up http://people.canonical.com/~ubuntu-archive/testing/lucid_outdate.html :)
[17:02] <ScottK> I know asac and Riddell` were working on that, but don't know exactly where se stand.
[17:02] <ScottK> Yes
[17:02] <ScottK> We're dead on armel at the moment
[17:03] <ScottK> koffice is updated to koffice2 in Universe
[17:03] <ScottK> We won't have a koffice in Main this cycle (upstream isn't confident enough)
[17:03] <ScottK> Riddell removed kdevelop since it's KDE4 release doesn't happen until May
[17:04] <ScottK> We are very, very close to moving kdelibs (the KDE3 one) to Universe
[17:04] <ScottK> That's it.
[17:04] <slangasek> ok, thanks
[17:05] <slangasek> anyone with questions on desktop?
[17:06] <slangasek> [TOPIC] DX Team
[17:06] <MootBot> New Topic:  DX Team
[17:06] <slangasek> seb128, ScottK: thanks
[17:06] <slangasek> davidbarth, njpatel: hi
[17:06] <davidbarth> hi slangasek
[17:06] <davidbarth> so not much to say this week
[17:06] <davidbarth> report at: https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus as usual
[17:07] <njpatel> slangasek, hey
[17:07] <davidbarth> mostly work on bug fixing system indicators further
[17:07] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[17:07] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[17:08] <davidbarth> of note, is the actual landing of cs-deco, after some last minute performance issues were solved by seb128 and bratsche
[17:08] <davidbarth> oops, the content of the report should be good now; i forgot to save
[17:08] <davidbarth> be sure to relead in a few secoinds
[17:08] <davidbarth> dx-lucid-gtk-improvements
[17:09] <davidbarth> further bug fixes
[17:09] <davidbarth> reminder: use the 'gtk-csd' tag for bugs related to that change
[17:09] <davidbarth> dx-lucid-xsplash - further work on that is being postponed to L+1
[17:09] <davidbarth> dx-lucid-session-menu: #506683 is fixed and released
[17:10] <davidbarth> dx-lucid-notifications: we have a patch for the closenotification api in testing right now; should land next week before b1
[17:11] <davidbarth> we had not planned to do major releases this week, still tedg made tarballs for 6 of our projects to release more bug fixes
[17:11] <davidbarth> questions?
[17:12] <cjwatson> dx-lucid-netbook-launcher-startup-speed is marked as todo in foundations-lucid-boot-performance - are you tracking that as well?
[17:12] <davidbarth> cjwatson: that part is done as far as we're concerned
[17:13] <davidbarth> cjwatson: i should mark it so, unless some stakeholder has a different feedback
[17:14] <slangasek> davidbarth: I gather from emails that foundations-lucid-gfxboot-update is still blocked on having the new graphics, can we talk about this?
[17:14] <davidbarth> cjwatson: hmm, actually, let me check that again, as i haven't seen recent charts with the results of netbook-launcher
[17:14] <cjwatson> davidbarth: it's only supposed to be marked done once it's been confirmed as hitting its budget
[17:14] <davidbarth> cjwatson: as a reminder for next week, ie there should be no regressions
[17:14] <cjwatson> slangasek,davidbarth: I'll cover that in our section - we revisited that with the design team today
[17:14] <slangasek> ok
[17:14] <cjwatson> and we're going to take a different approach
[17:14] <davidbarth> cjwatson: right, so let's put that as an action item for me for next week
[17:15] <davidbarth> slangasek: yes, the new graphics are blocked
[17:15] <davidbarth> cjwatson: ah ok fine
[17:16] <cjwatson> (no disrespect intended etc., new plan just seems more viable)
[17:16] <slangasek> anything else on DX?
[17:17] <slangasek> [ACTION] davidbarth to check on budget status of dx-lucid-netbook-launcher-startup-speed
[17:17] <MootBot> ACTION received:  davidbarth to check on budget status of dx-lucid-netbook-launcher-startup-speed
[17:18] <slangasek> [TOPIC] Foundations Team
[17:18] <MootBot> New Topic:  Foundations Team
[17:18] <slangasek> davidbarth: thanks
[17:18] <cjwatson> [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:18] <cjwatson> [LINK] http://people.canonical.com/~pitti/workitems/canonical-foundations-ubuntu-10.04-beta-1.html
[17:18] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:18] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-foundations-ubuntu-10.04-beta-1.html
[17:18] <cjwatson> Beta-1 work items are mostly composed of deferrals from alpha-3 (the alpha-3 list should be at zero after the next refresh), so there are several specs there with one or two tail-end work items to tidy up.
[17:18] <cjwatson> (and sorry I hadn't cleaned up the alpha-3 list before now)
[17:18] <cjwatson> Boot speed doing well, with kernel+plumbing+X down to 6 seconds on reference hardware.
[17:18] <cjwatson> parted 2.1 migration in progress, following FFe.  With a little bit of partman work on top, this will give us non-512-byte sector support and better alignment, so should hopefully clear up a lot of "doesn't wor
[17:18] <cjwatson> k with Windows 7" bugs.
[17:18] <cjwatson> Plymouth still a hot button; lots of bugs related to that.
[17:18] <cjwatson> The plugin migration in ubiquity has been a bit rough, and we're knocking off bugs related to that as fast as possible.  They're mostly small.
[17:18] <cjwatson> We need a volunteer to clear up the rest of foundations-lucid-supportable-binaries.
[17:19] <cjwatson> Java and X versions still need to be confirmed for foundations-lucid-release-collaboration-with-debian.
[17:19] <cjwatson> foundations-lucid-gfxboot-update discussed with design team today.  Backing off from previous pre-greeter approach, which was going to take too long to polish up UI-wise, and planning to use ubiquity's language selector instead; this will involve a lot less new code.
[17:19] <cjwatson> Still a number of software-center tasks open, but the list is beginning to look under control.
[17:19] <cjwatson> --
[17:19] <slangasek> I had volunteered to follow through on foundations-lucid-supportable-binaries, it's just been getting pushed down the stack by other fires
[17:20] <cjwatson> ok, shall I assign the remaining work items to you?
[17:20] <slangasek> sure
[17:20] <slangasek> gfxboot-update> doesn't that mean we have the problem of the UI not being translated in the live env?
[17:21] <cjwatson> no, it shouldn't do - standalone ubiquity language selector -> try/install choice -> if you select try, starts live env
[17:21] <cjwatson> if you select install, continues
[17:21] <slangasek> oh, ok
[17:22] <slangasek> neat, then :)
[17:22] <cjwatson> this is all from discussion today, but I'm feeling a lot happier about it after that
[17:23] <slangasek> all looks sane to me - anything else on Foundations?
[17:24] <cjwatson> we're mostly hunkering down for bugfixing now, I think.
[17:24] <slangasek> indeed
[17:24] <slangasek> [TOPIC] Security Team
[17:24] <MootBot> New Topic:  Security Team
[17:24] <slangasek> cjwatson: thanks
[17:24] <slangasek> jdstrand: hi
[17:24] <jdstrand> hi
[17:25] <jdstrand> you can see our status here: https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:25] <slangasek> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:25] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:25] <jdstrand> as far as dev work is concerned, we were done with alpha-3 stuff last week. that did not change this week :)
[17:26] <jdstrand> and the team as a whole worked on security stuff in stable releases this past week, so nothing new to report
[17:26] <slangasek> phew :)
[17:26] <jdstrand> that's pretty much it
[17:27] <slangasek> anything of concern for beta1?
[17:27] <jdstrand> no
[17:27] <slangasek> ok, cool
[17:27] <jdstrand> we are in bug fixing mode
[17:27] <slangasek> [TOPIC] MOTU
[17:27] <MootBot> New Topic:  MOTU
[17:27] <slangasek> jdstrand: thanks
[17:27] <jdstrand> the bps that are left are either not dependent on a milestone or are bug fixes
[17:27]  * sistpoty|work waves
[17:27] <ScottK> sistpoty|work: You around?
[17:27] <jdstrand> np
[17:27] <slangasek> ScottK, sistpoty|work: hi
[17:27] <ScottK> sistpoty|work: You go first
[17:28] <sistpoty|work> we got a haskell and an ocaml transition waiting to be finished
[17:28] <sistpoty|work> Laney tracks haskell, and makes good progress afaict
[17:28] <ScottK> ocaml is making progress too (I see the bug reports)
[17:28] <sistpoty|work> ocaml is also tracked, could need some more people uploading rebuilds
[17:29] <slangasek> ocaml I've been seeing bug reports for; haskell I have not - perhaps because there are no FFes needed there?
[17:29] <sistpoty|work> others than that, FFe handling started quite smooth
[17:29] <slangasek> I could take some ocaml rebuilds, where's the list?
[17:29]  * sistpoty|work looks
[17:30] <ScottK> Watching the Debian Python 2.6 tranisition work, I'm a little nervous about our status, but don't have specifics.
[17:31] <sistpoty|work> bug #526073
[17:32] <slangasek> sistpoty|work: thanks
[17:32] <sistpoty|work> others than that, thanks for driving motu-release <-> ubuntu-release merge, slangasek
[17:32] <slangasek> ScottK: python> you're concerned about latent bugs in Ubuntu's python 2.6 that aren't getting picked up?
[17:32] <ScottK> slangasek: Yes.
[17:32] <antihacker> anyone know what axel.dav is.
[17:33] <slangasek> ScottK: what are the chances those bugs were marked release-critical in Debian?
[17:33] <ScottK> slangasek: Once we get a little further along we should have another look at sync/merge candidates
[17:33]  * slangasek nods
[17:33] <ScottK> slangasek: Some, but many are just getting fixed without bugs being filed
[17:33] <slangasek> ScottK: yep, figured
[17:34] <ScottK> I'm sure once python2.6 is default in Debian we'll get more
[17:34] <slangasek> ScottK: at what point further along should we review the sync/merges for python?
[17:34] <antihacker> anyone know what axel.dav is?   low level format access violation  DAV
[17:34] <ScottK> antihacker: You're in the wrong channel
[17:34] <antihacker> k, sorry
[17:34] <ScottK> slangasek: Let's say two weeks.  Not sure really.
[17:34] <slangasek> ok
[17:35] <slangasek> [ACTION] ScottK, slangasek to review python sync/merge candidates ~Mar 12
[17:35] <MootBot> ACTION received:  ScottK, slangasek to review python sync/merge candidates ~Mar 12
[17:35] <slangasek> noted :)
[17:35] <slangasek> anything else to discuss?
[17:36] <ScottK> Not from me
[17:36] <slangasek> [TOPIC] AOB
[17:36] <sistpoty|work> don't think so
[17:36] <MootBot> New Topic:  AOB
[17:36] <slangasek> sistpoty|work, ScottK: thanks, as always
[17:36] <slangasek> anything else someone wants to cover here today?
[17:37] <slangasek> #endmeeting
[17:37] <MootBot> Meeting finished at 11:37.
[17:37] <slangasek> thanks, folks!
[17:39] <marjo> slangasek: thx