[15:02] <jamalta> quick question, when i see the calendar at http://fridge.ubuntu.com/calendar it shows events in my timezone, but when i try to add it to my account it goes back to the default calendar timezone (GMT)
[15:02] <jamalta> how can i get it to add it and move the events to my timezone?
[15:53] <jiboumans> o/'s 7 mins early
[15:54] <persia> None of that now.  You'll start a trend of everyone showing up early, and the logs will get all confused :)
[15:55]  * jiboumans hides for a while
[15:56] <persia> No worries.  It's just that MootBot has a feature to list the meeting attendees, tracked by the nicks that sent text between the formal start and end of the meeting.
[15:56] <persia> Some people o/ just to show up in that log, even if they don't say anything else in the meeting.
[15:56] <persia> But doing so prior doesn't provide that benefit.
[15:58]  * marjo waves
[15:59]  * Riddell grabs his canoe and surfs marjo's wave
[16:00] <slangasek> morning all
[16:00] <jiboumans> o/
[16:01] <ttx> \o
[16:01]  * asac waves
[16:02] <slangasek> #startmeeting
[16:02] <slangasek> hmm
[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] <slangasek> ah, there we are :)
[16:03] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-01-15
[16:03] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-01-15
[16:03] <slangasek> [TOPIC] Actions from previous meeting
[16:03] <MootBot> New Topic:  Actions from previous meeting
[16:03] <slangasek>   * fader_ to check with marjo whether lucid-qa-iso-tracker is deferred to alpha-3, and re-target appropriately in LP (n/a, blueprint is completed)
[16:03] <slangasek>   * fader_ to verify whether 494627 == 503700 by re-testing affected hardware
[16:03] <slangasek>   * davidbarth to review cross-team assignments for dx specs and contact right people
[16:03] <slangasek>   * asac to link une-2d-launcher MIRs from blueprint
[16:03] <slangasek>   * asac to link MIR for uboot to spec
[16:03] <slangasek>   * slangasek to claim "adding ARM alternate images to the ISO tracker" (DONE)
[16:03] <slangasek>   * ttx to target "irqbalance - add to the default install" to a3
[16:03] <slangasek>   * ev to retarget foundations-lucid-gfxboot-update greeter to alpha-3
[16:03] <slangasek> fader_, asac, ttx: status there?
[16:03] <asac> both have happened
[16:03] <slangasek>   * slangasek to do some triaging of cron bug reports (DONE)
[16:03] <ttx> sladen: done
[16:03] <ttx> ah
[16:03] <ttx> slangasek: done
[16:04] <slangasek> davidbarth: cross-team workitem assignments> sorted?
[16:04] <fader_> slangasek: As you say, the blueprint is completed.  The bugs were dupes and are marked as such.
[16:04] <slangasek> fader_: and the second one?
[16:04] <davidbarth> slangasek: ah, nope; not all
[16:04] <fader_> slangasek: The bug was a dupe and has been updated in lp.
[16:04] <davidbarth> slangasek: action me again for next week; but i've already sorted the scoping for a3 which was the topic of the week
[16:05] <davidbarth> slangasek: thanks to rickspencer3 and robbiew
[16:05] <slangasek> davidbarth: ok.  do you need any help with trying to identify developers to take these work items for you?
[16:07] <slangasek> davidbarth: (feel free to ping me about it, if so)
[16:07] <slangasek> [TOPIC] QA Team
[16:07] <MootBot> New Topic:  QA Team
[16:07] <davidbarth> slangasek: i'm browsing the blueprints targeted for a2 and a3 right now
[16:07] <davidbarth> slangasek: ok, thanks
[16:07] <marjo> * HW Testing
[16:07] <marjo> http://people.canonical.com/~fader/hw-testing/current.html
[16:07] <marjo> Netbooks:
[16:07] <marjo>         Passed: 8 (62%) Failed: 2 (15%) Untested: 3 (23%)
[16:07] <marjo> Laptops:
[16:07] <marjo>         Passed: 24 (92%) Failed: 0 (0%) Untested: 2 (8%)
[16:07] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:07] <marjo> Servers:
[16:07] <marjo>         Passed: 48 (91%) Failed: 0 (0%) Untested: 5 (9%)
[16:07] <marjo> Desktops:
[16:07] <marjo>         Passed: 12 (100%)     Failed: 0 (0%) Untested: 0 (0%)
[16:07] <marjo> Open bugs:
[16:07] <marjo> LP #504315  Toshiba NB100 failed to resume from hibernate
[16:07] <marjo> LP #497546  Microphones not working on Dell Vostro 320
[16:07] <marjo> all categories look good except for netbooks
[16:07] <slangasek> davidbarth: ok; if you find anything you need to get escalated, don't hesitate to ask
[16:08] <marjo> * alpha-2 test report
[16:08] <marjo> Lucid Alpha 2 Test Report
[16:08] <marjo> 2010-01-15
[16:08] <marjo> = Summary =
[16:08] <marjo> == Test Coverage ==
[16:08] <marjo> Image Test Coverage = 37/39 = 94.8%
[16:09] <marjo> Test Case Coverage = 138/210 = 65.7%
[16:09] <marjo> Upgrade Coverage = 3/10 = 30%
[16:09] <slangasek> marjo, fader_: what does 'investigating' mean for the comment on the untested netbooks?
[16:09] <marjo> [16:09] <marjo> 20 Test Failures
[16:09] <marjo> Failure Rate 20/138 = 14.49
[16:09] <fader_> slangasek: It means I have not yet determined why they were not tested
[16:09] <fader_> slangasek: Basically a placeholder/note to myself to figure out what's wrong and fix it
[16:10] <slangasek> ok
[16:10] <marjo> Alpha 2 image test coverage was quite high; thx to all for testing
[16:10] <slangasek> yes, kudos to all our testers there
[16:11] <marjo> we will continue to push for higher test case coverage and of course, upgrade coverage
[16:11] <asac> marjo: what numbers are you aiming for wrt test coverage?
[16:11] <marjo> asac: 90 - 100%!
[16:12] <marjo> very possible, IMO
[16:12] <slangasek> unless we decide that the extra test coverage means we can do more last-minute ISO respins ;)
[16:13] <asac> haha
[16:13] <cjwatson> let's not, and say we did
[16:13] <marjo> == Bugs summary ==
[16:13] <marjo> [16:13] <marjo> 48 bugs unfixed
[16:13] <marjo> Critical - 2
[16:13] <marjo> High - 7
[16:13] <marjo> Medium - 6
[16:13] <marjo> Low - 2
[16:13] <marjo> Unknown - 1
[16:13] <marjo> Undecided - 30
[16:13] <marjo> Critical Bugs:
[16:13] <marjo> LP: #505772 - system freezes sometimes after X is up for a while - Confirmed - Critical
[16:13] <marjo> LP: #506683 - indicator-applet doesn't show menu choices when selected - Confirmed - Critical
[16:15] <slangasek> both of which seem to be in progress, so that's good
[16:15] <marjo> slangasek: am i not using the right format for mootbot to pick up lp numbers?
[16:15] <slangasek> marjo: I think the IRC bot only responds to 'bug #505772'
[16:15] <marjo> ah, sorry
[16:15] <slangasek> no worries
[16:16] <marjo> [16:16] <marjo> 6 bugs fixed
[16:16] <marjo> High - 2
[16:16] <marjo> Medium - 1
[16:16] <marjo> Unknown - 1
[16:16] <marjo> Undecided - 2
[16:16] <marjo> Specs status and burn-down chart:
[16:16] <marjo> http://piware.de/workitems/qa/lucid-alpha2/report.html
[16:16] <MootBot> LINK received:  http://piware.de/workitems/qa/lucid-alpha2/report.html
[16:16] <marjo> * UbuntuSpec:lucid-qa-iso-tracker
[16:16] <marjo> Implemented as of Alpha-2! Thanks to ara, slangasek and stgraber!
[16:17] <slangasek> do you plan to track the unfixed/fixed status over the next weeks?  (not sure it means much to count the # of issues fixed 1 day after the alpha...)
[16:17] <marjo> slangasek: yes
[16:17] <slangasek> ok
[16:17] <marjo> part of SOP
[16:18] <marjo> * UbuntuSpec:lucid-qa-checkbox-integrate-regression-testing
[16:18] <marjo> One work item missed the Alpha-2 deadline:
[16:18] <marjo> [cr3] Integrate into hardware certification to run on a per milestone basis: INPROGRESS
[16:18] <marjo> Shooting for completion today.
[16:18] <slangasek> ok, cool
[16:18] <marjo> * UbuntuSpec:lucid-qa-kernel-test-automation
[16:18] <marjo> Two work items missed the Alpha-2 deadline:
[16:18] <marjo> [leannogasawara] gcov kernel testing to evaluate kernel coverage (ogasawara to build kernel, talk to fader for testing): TODO
[16:18] <marjo> Shooting for completion next week.
[16:19] <marjo> * UbuntuSpec:qa-lucid-automated-server-testing
[16:19] <marjo> Six work items missed the Alpha-2 deadline:
[16:19] <marjo> Integrate qa-regression-tests clamav tests into checkbox: TODO
[16:19] <marjo>  Integrate qa-regression-tests cups tests into checkbox: TODO
[16:19] <marjo>  Integrate qa-regression-tests cyrus-sasl2 tests into checkbox: TODO
[16:19] <marjo>  Integrate qa-regression-tests fetchmail tests into checkbox: TODO
[16:19] <marjo>  Integrate qa-regression-tests libvirt tests into checkbox: TODO
[16:19] <marjo>  Integrate qa-regression-tests mysql tests into checkbox: TODO
[16:19] <marjo> All retargeted for Alpha-3.
[16:19] <marjo> slangasek: i was too quick to change blueprints per the suggestion
[16:20] <marjo> so, i'll go back and fix so tools don't double up work items
[16:20] <seb128> hi
[16:20] <marjo> slangasek: that's all from QA team
[16:21] <slangasek> marjo: the only thing that doubles is that the count of 'postponed' items increases; the server team wasn't doing this when they ran into the problem
[16:21] <marjo> oh, ok
[16:21] <slangasek> but the suggestion was just a suggestion, as long as the number of open work items is correct I'm ok with whatever teams decide :)
[16:21] <marjo> ack
[16:22] <slangasek> anyone have any questions for QA?
[16:23] <slangasek> marjo: you said 6 items postponed for qa-lucid-automated-server-testing... http://macaroni.ubuntu.com/~pitti/workitems/all-lucid-alpha-2.html shows *44* outstanding items, was that a case of mis-milestoning in the blueprint?
[16:24] <marjo> slangasek: no, the 6 items i refer to missed the alpha-2 deadline
[16:24] <marjo> therefore are now part of the larger 44 outstanding items for post alpha2
[16:25] <slangasek> marjo: the report seems to have thought that all the "Work items for later" were also due by alpha-2, so I guess the report needs tweaked
[16:25] <marjo> slangasek: ack
[16:25] <slangasek> anyway, moving on
[16:25] <slangasek> [TOPIC] Desktop Team
[16:25] <MootBot> New Topic:  Desktop Team
[16:25] <slangasek> marjo: thanks
[16:25] <slangasek> seb128: hi
[16:25] <marjo> thx all!
[16:25] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:25] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:26] <seb128> hey slangasek
[16:26] <slangasek> Riddell: I see you edited that page today, do you know if it's fully up-to-date?
[16:26] <Riddell> I don't think the gnome stuff is
[16:26] <seb128> I've not prepared anything there just replied to the ping some minutes ago
[16:26] <seb128> but I think I can reply to questions
[16:26] <seb128> looking
[16:27] <seb128> no apparently it's not
[16:27] <slangasek> http://macaroni.ubuntu.com/~pitti/workitems/canonical-desktop-team-lucid-alpha-2.html looks good, anyway
[16:27] <MootBot> LINK received:  http://macaroni.ubuntu.com/~pitti/workitems/canonical-desktop-team-lucid-alpha-2.html looks good, anyway
[16:28] <Riddell> but I do have a Kubuntu update :)
[16:28] <seb128> on the Ubuntu side we got an UNE sprint this week
[16:28] <seb128> with good progresses
[16:29] <seb128> we should have public isos to test soon
[16:29] <seb128> the UNE session is working
[16:29] <slangasek> seb128: one spec that I only just noticed had outstanding WIs for alpha-2 was lucid-ubuntu-one-symlinks-and-udfs, which I believes falls under the Desktop umbrella as far as Ubuntu delivery is concerned, but it's not included on the desktop team's report
[16:29] <seb128> kenvandine, ^
[16:29] <seb128> I don't know about online services tasks
[16:29] <slangasek> seb128: do you know how to get that picked up by pitti's scripts?
[16:30] <asac> (the new WI tracker has rough edges still ... for us lots of stuff got dropped etc. -> need to wait for pitti to understand it)
[16:30] <slangasek> so that it's on the radar
[16:30] <seb128> slangasek, no, I guess it needs pitti debugging
[16:30] <kenvandine> seb128, slangasek: it isn't done, we need to get that changed
[16:30] <seb128> I will let him now on monday
[16:30] <slangasek> seb128: ok, let me action you for that?
[16:31] <slangasek> [ACTION] seb128 to follow up with pitti wrt lucid-ubuntu-one-symlinks-and-udfs not tracked on the desktop team report
[16:31] <MootBot> ACTION received:  seb128 to follow up with pitti wrt lucid-ubuntu-one-symlinks-and-udfs not tracked on the desktop team report
[16:31] <seb128> slangasek, ok
[16:31] <slangasek> kenvandine: is the spec in jeopardy for 10.04?
[16:32] <slangasek> asac: if you want to poke me after the meeting about what stuff is dropping off your report, I might be able to make sense of some of it
[16:33] <slangasek> Riddell: go ahead with your Kubuntu report?
[16:33] <Riddell> Alpha 2 out the door and working reasonably
[16:33] <Riddell> MIRs outstanding
[16:33] <Riddell> kubuntu-notification-helper 503906
[16:33] <seb128> on the alpha2 lists, the 	dx-lucid-session-menu "provide missing API to list users and switch sessions" is done now I think
[16:33] <Riddell> virtuoso-opensource 503774
[16:33] <Riddell> KOffice 2 on its way, plenty more MIRs needed there
[16:33] <Riddell> Fixed since alpha 2 is the KDM double login needed issue in consolekit 495100
[16:33] <Riddell> Systray applets now have dbus menu bling, thanks to agateau
[16:33] <Riddell> SIP has a new version out, binary imcompatible, some distruption of Python bits which use it due (mostly Qt/KDE)
[16:33] <seb128> I've seen robert_ancell uploading gdm with a change for that
[16:33] <Riddell> KDM needs plymouth patches investigating (sitting in bug tracker upstream) and Kubuntu needs a Plymouth theme (work started)
[16:33] <Riddell> KDE still needs HAL (udev doesn't offer replacements for all its functions) so please nobody break it
[16:33] <Riddell> https://wiki.ubuntu.com/Kubuntu/Todo
[16:33] <asac> slangasek: ok
[16:33] <kenvandine> slangasek, no, it is real close to being done, last i heard
[16:34] <slangasek> kenvandine: ok.  will you take care of cleaning up the whiteboard to target alpha-3 for the outstanding work?
[16:34] <kenvandine> slangasek, yes
[16:34] <slangasek> thanks
[16:35] <slangasek> Riddell: thanks for the summary
[16:35] <slangasek> anyone have other questions for desktop?
[16:36] <slangasek> [TOPIC] DX Team
[16:36] <MootBot> New Topic:  DX Team
[16:36] <slangasek> seb128, Riddell, kenvandine: thanks
[16:36] <davidbarth> slangasek: hi again
[16:36] <slangasek> davidbarth, njpatel: hi :)
[16:37] <njpatel> hey
[16:37] <davidbarth> The weekly status report is at the usual place: https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[16:37] <davidbarth> In summary:
[16:37] <davidbarth> A2 delivery over now; not all items delivered, but application-indicator considered in good shape.
[16:37] <davidbarth> A2 burn-down chart for reference: http://piware.de/workitems/dx/lucid-alpha2/report.html
[16:37] <davidbarth> Re-scoping for alpha-3 with more limited focus (see blueprints below)
[16:38] <davidbarth> Dropping dx-lucid-notifications for the rest of the release
[16:38] <davidbarth> Limiting work on dx-lucid-xsplash; upcoming call with Scott (after he returns from LCA)
[16:38] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[16:38] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[16:38] <davidbarth> Limiting the scope of dx-lucid-me (new blueprint, to a simple/undifferentiated broadcast of status)
[16:38] <slangasek> [LINK] http://piware.de/workitems/dx/lucid-alpha2/report.html
[16:38] <MootBot> LINK received:  http://piware.de/workitems/dx/lucid-alpha2/report.html
[16:38] <davidbarth> Blueprints tracked for alpha-3:
[16:38] <davidbarth> dx-lucid-application-indicator
[16:38] <davidbarth> of note there:
[16:38] <davidbarth> transparent fallback and menu updates delivered yesterday (Thursday upload window)
[16:39] <davidbarth> SDK guide updated
[16:39] <davidbarth> that's https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationIndicators
[16:39] <davidbarth> FD.o registration still in progress (Gnome & KDE sync)
[16:39] <davidbarth> dx-lucid-me-menu (NEW blueprint)
[16:39] <davidbarth> dx-lucid-gtk-improvements - still re-scoping
[16:39] <davidbarth> dx-lucid-sound-indicator
[16:39] <davidbarth> of note here:
[16:39] <davidbarth> Design analysis on-track: DONE
[16:39] <davidbarth> Initial implementation: started
[16:40] <davidbarth> (that's conor curran's work this week; our new starter; welcome!)
[16:40] <slangasek> hah, that report looks a bit odd, your completed WIs also went away at the end... :)
[16:40] <slangasek> [LINK] http://macaroni.ubuntu.com/~pitti/workitems/canonical-dx-team-lucid-alpha-2.html
[16:40] <MootBot> LINK received:  http://macaroni.ubuntu.com/~pitti/workitems/canonical-dx-team-lucid-alpha-2.html
[16:40] <slangasek> that one looks better
[16:40] <davidbarth> other bp for a3
[16:40] <davidbarth> dx-lucid-power-indicator
[16:40] <davidbarth> dx-lucid-session-menu
[16:41] <davidbarth> we're putting the update of the messaging menu a bit later for now; waiting for some feedback on our ability to deliver the first set of wi during a3
[16:41] <asac> hmm. i am in that report with thumb2 spec ;)
[16:41] <davidbarth> slangasek: thanks for the link; yeah this one's better
[16:41] <davidbarth> questions on DX activities?
[16:42] <davidbarth> asac: what's taht?
[16:42] <cjwatson> davidbarth: the gfxboot-update DX dependency doesn't seem to be in your list?
[16:42] <slangasek> davidbarth: is dx-lucid-netbook-launcher-startup-speed on track for alpha-3?  That was originally a2 and was retargeted
[16:42] <cjwatson> davidbarth: foundations-lucid-gfxboot-update
[16:42] <asac> davidbarth: that clearly has nothing to do with your team ... aka bug in wi-tracker
[16:43] <davidbarth> slangasek: that one is; that's the netbook part of the report; we finished the round of analysis planned for a2; we have an issue currently with the speed that is not on par with our expectations
[16:43] <davidbarth> cjwatson: kept in mind, but don't know where to track it as part of our bp
[16:44] <davidbarth> asac: yes, it seems; we'll follow up with pitti on that
[16:44] <cjwatson> davidbarth: it's Mark-priority, and I'm concerned about it falling off the list; it shows up on http://macaroni.ubuntu.com/~pitti/workitems/canonical-dx-team-lucid-alpha-3.html FWIW
[16:44] <slangasek> [LINK] http://macaroni.ubuntu.com/~pitti/workitems/canonical-dx-team-lucid-alpha-3.html
[16:44] <MootBot> LINK received:  http://macaroni.ubuntu.com/~pitti/workitems/canonical-dx-team-lucid-alpha-3.html
[16:45] <cjwatson> davidbarth: it should be fine to reference it from your wiki page, if that's all that the problem is
[16:45] <davidbarth> cjwatson: ok, noted; adding it to the generic dx-lucid-gtk-improvements one, that bratsche is assigned to
[16:45] <cjwatson> seems a bit mismatched, but ok
[16:45] <cjwatson> I can assign the work items in the foundations spec to bratsche, if that would help?
[16:45] <njpatel> slangasek, the netbook startup speed was being worked on, but this week was the first time we had a clear idea of the times on Lucid (once desktop team did the packaging + session), we've pulled a graph of whats slow this morning and have a plan to fix that
[16:46] <slangasek> njpatel: ok
[16:46]  * cjwatson goes ahead and does that
[16:46] <davidbarth> cjwatson: doing that now
[16:46] <slangasek> anything else on DX?
[16:47] <davidbarth> cjwatson: ok, you first on your bp; also adding it on a dx-lucid one; double accounting should not be an issue, as long as the wi is worked on, quickly
[16:47] <cjwatson> davidbarth: *nod* I don't mind double-accounting here
[16:48] <slangasek> davidbarth: do you not use the canonical-dx-team burndown charts to track your team's outstanding WIs?  The current iteration of the charts specifically includes all WIs assigned to members of the team, to try to help keep these things on the radar
[16:48] <slangasek> (though this is the only one I know of assigned to DX this cycle for another team, so maybe there's no need to generalize?)
[16:49] <davidbarth> slangasek: not sure which burndown you're referring to
[16:49] <slangasek> davidbarth: http://macaroni.ubuntu.com/~pitti/workitems/canonical-dx-team-lucid-alpha-3.html , the one cjwatson pointed at
[16:49] <cjwatson> the ones on macaroni as opposed to piware.de
[16:50] <cjwatson> piware.de is the old set
[16:50] <slangasek> let's keep moving, though
[16:50] <slangasek> [TOPIC] Mobile Team
[16:50] <davidbarth> ok, i hadn't seen this one, ie the team-assigned on; i was using the "old" ones
[16:50] <MootBot> New Topic:  Mobile Team
[16:50] <davidbarth> slangasek:
[16:50] <ogra> thats us !
[16:50] <asac> hi
[16:50] <davidbarth> slangasek: thanks
[16:50] <slangasek> davidbarth: thank you!
[16:50] <slangasek> asac, ogra: hello
[16:50] <asac> [LINK] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:50] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:51] <asac> so ... because of the WI i still listed the old tracker for the overall progress
[16:51] <asac> and for alpha-2
[16:51] <asac> we need to get that sorted, but that was already discussed
[16:51] <asac> == Weekly summary ==
[16:51] <asac>  * uboot investigations: partitioning/fat issues worked around; new issue uncovered (see RC bugs)
[16:51] <asac>  * linux-fsl-imx51 kernel update and verification for a2
[16:51] <asac>  * thumb2 package code review - http://wiki.ubuntu.com/ARM/Thumb2PackageReviewList
[16:52] <asac> [LINK] http://wiki.ubuntu.com/ARM/Thumb2PackageReviewList
[16:52] <MootBot> LINK received:  http://wiki.ubuntu.com/ARM/Thumb2PackageReviewList
[16:52] <asac>  * marvel thumb2 issues investigation - bug 504880 and bug 505772
[16:52] <asac>  * alpha-2 image testing
[16:52] <asac>  * started alpha-3 planning
[16:52] <asac> so lets first go for RC bugs
[16:52] <asac> == RC Bugs ==
[16:53] <asac> not much fixes as we tried to understand uboot and marvell issues
[16:53] <asac> which are most pressing
[16:53] <asac>  * Bug:505772: linux-mvl-dove "system freezes sometimes after X is up for a while"
[16:53] <asac>  * Bug:504880: linux-mvl-dove "[dove] possibility of thumb2 instructions invalidly being handled"
[16:53] <asac> those seem related ... and it might be a silicon issue with thumb2 as it seems
[16:53] <asac> we are trying to get the latest hardware now to verify that thats really the case
[16:54] <ogra> uboot is a swiss cheese ... you fix it on one side and new holes show up on the other ...
[16:54] <asac> for uboot we worked around the issue with loading files from fat file system to find that we have issues with NIC
[16:54] <asac>  * Bug:507887: uboot-imx "NIC not properly initialized in uboot code"
[16:54] <asac> also now we found that anoter file hangs when loading from fat
[16:54] <asac> but we also found that ext2 seems to work
[16:54] <cjwatson> there may be hope for the future; one of the grub2 developers offered to port grub2 to arm if we could lay hands on some hardware for him
[16:55] <ogra> the vendor patches are really tricky, one removes stuff a former added and the third adds it back again ... its a maze
[16:55] <asac> so unless we find the bug in the fat code we can move there (image building will take a bit longer: instead of 2 minutes we get rather 15 minutes i was told)
[16:55] <ogra> cjwatson, we dont have enough HW ourselves atm is our prob
[16:55] <asac> right. but in the past we thought it could be fixed by partitioning only, but now i am not that optimistic
[16:55] <asac> and will look at code more seriously
[16:55] <slangasek> asac: is the progress on uboot bad enough that we need to start thinking about a fallback plan for lucid?
[16:55] <cjwatson> ogra: yeah, I know
[16:55] <ogra> slangasek, we have redboot working
[16:56] <asac> slangasek: we have a fallback that seems to work: ext2
[16:56] <slangasek> ok
[16:56] <asac> and in worst case we can use reboot ... but lets not think about that yet
[16:56] <asac> still some time to go. doesnt block our "images" atm
[16:56] <ogra> right, there is still time until A3
[16:56] <asac> so one good news is that
[16:56] <asac>  * Bug:458537: linux-fsl-imx51: hibernate does not work
[16:56] <asac> can be removed from our RC bug list. we got a confirm that that isnt even supported by freescale
[16:56] <asac> hardware
[16:57] <slangasek> asac: ok, will you pleas adjust the bug status accordingly?  (--> wontfix, unmilestoned)
[16:57] <asac> yes, i just got that before the meeting :)
[16:57] <slangasek> ok
[16:58] <asac> ok so much on RC bugs... not great, but we at least things are moving
[16:58] <asac> the marvell thumb2 thing is what bothers us most, but we will have more info on that next week
[16:58] <asac> ok ... so back to specs:
[16:58] <asac> == Blueprint/Activity alpha-2 late comers ==
[16:58] <asac>  * mobile-lucid-arm-gcc-v7-thumb2: code porting needed documented; some work items left for debian import freeze time
[16:58] <slangasek> asac: no need to reproduce the full webpage on IRC, I think
[16:59] <asac> ok
[16:59] <asac> good
[16:59] <asac> i didnt include a summary of alpha-3 blueprints
[16:59] <asac> as we are planning
[16:59] <slangasek> yep, that's fine
[16:59] <asac> but for that i need a good wi-tracker as its hard to estimate the work we can do with half of the items disappearing ;)
[16:59] <asac> lets hope we get that sorted
[17:00] <slangasek> let's /plan/ to get that sorted. :)
[17:01] <asac> yes
[17:01] <asac> so thats it ... see the report yourself and ask questions ;)
[17:01] <slangasek> asac: mobile-lucid-arm-lightweightbrowser> how "pending" is this?  of all the mobile a2 specs, that had the lowest completion rate
[17:02] <asac> slangasek: we want to do a good comparision on performance and need ffox 3.6 for that
[17:02] <asac> anyway, thats done now and arm is doing the benchmarks
[17:02] <asac> so once we have that we decide and just do it.
[17:02] <slangasek> when are you expecting to have the benchmarks back?
[17:03] <asac> definitly early next week
[17:03] <slangasek> ok
[17:03] <slangasek> no other questions from me; anyone else?
[17:04] <slangasek> [TOPIC] Server Team
[17:04] <MootBot> New Topic:  Server Team
[17:04] <ttx> o/
[17:04] <slangasek> asac, ogra: thanks
[17:04] <slangasek> ttx: hi
[17:04] <asac> thanks
[17:04] <ogra> thanks
[17:04] <ttx> https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[17:04] <ttx> ^ Our updated status
[17:04] <slangasek> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[17:04] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[17:04] <ttx> Alpha2 release went relatively well, despite very late respins
[17:04] <cjwatson> sorry about that ...
[17:04] <ttx> that broke my nice 100% test coverage
[17:05] <cjwatson> there was a bit of fallout from partitioner optimisation work
[17:05] <cjwatson> some of which indeed is still ongoing
[17:05] <ttx> the most annoying bit, I think, was bug 506297
[17:05] <ttx> easily workarounded... if you know it's not frozen.
[17:05] <slangasek> in the errata; should be addressable for a3
[17:06] <ttx> On the bugs front...
[17:06] <ttx> All remaining alpha2-milestoned bugs have been moved to alpha3.
[17:06] <ttx> That's the MIR that have not been completed in time
[17:06] <ttx> + the samba nmbd bug
[17:06] <slangasek> working on that one today
[17:06] <ttx> + the most annoying bug revealed in UEC testing so far
[17:07] <ttx> We'll parse the UEC buglist for 1.6.2 reproduction and target other bugs appropriately
[17:07] <ttx> On the list of bugs in oter teams and affecting us...
[17:07] <ttx> apart from the boot confusion described above, we have bug 494565
[17:08] <ttx> that blocked delivery of one of the specs we had for alpha2
[17:08] <ttx> My understanding is that it should be fixed soon, now that alpha2 is out of the door
[17:08] <ttx> ^ kernel team
[17:08] <ttx> On the specs side...
[17:09] <ttx> I included a quick summary of the spilled-over items from alpha2 that were retargeted to alpha3
[17:09] <ttx> The most significant failure is server-lucid-ec2-boothooks
[17:09] <ttx> which blocked another one (server-lucid-ec2-config)
[17:10] <ttx> Both are high-priority on the alpha3 subcycle
[17:10] <ttx> Jos and I spent most of our week working on alpha3 planning
[17:10] <ttx> it's mostly completed, should be published on Monday, though looking at the alpha3 workitems graph should give you a good idea of what's coming up
[17:11] <ttx> http://macaroni.ubuntu.com/~pitti/workitems/canonical-server-lucid-alpha-3.html
[17:11] <MootBot> LINK received:  http://macaroni.ubuntu.com/~pitti/workitems/canonical-server-lucid-alpha-3.html
[17:11] <ttx> Questions ?
[17:12]  * slangasek takes a minute to finish digesting
[17:13]  * ttx will add status lines to all whiteboards to get a saner Status in those reports
[17:13] <jiboumans> slangasek: 89dc3d665b3c4d5188e3ab963c79e4fe
[17:14] <slangasek> server-lucid-eucalyptus-karmic-retrospective - you note the hardware delivery is late (last week, it was expected this Thursday)
[17:14] <slangasek> jiboumans: heh
[17:14] <ttx> jiboumans: if you're going to hash me, please do SHA256
[17:15] <slangasek> ttx, jiboumans: do we have a new delivery date from IS?
[17:15] <ttx> slangasek: we asked them... jiboumans, any answer ?
[17:15] <jiboumans> slangasek: no date. i'm expecting it early next week and elmo didn't say 'no'
[17:15] <slangasek> ok
[17:16] <slangasek> no other questions from me
[17:16] <slangasek> anyone else?
[17:16] <cjwatson> jiboumans,ttx: could you mail that to me with [is-review] in the subject line, and I'll check on it next call
[17:16] <jiboumans> cjwatson: you mean RT #36737?
[17:17] <jiboumans> cjwatson: you appear to be subscribed
[17:17] <cjwatson> jiboumans: ah, never mind, it already has a suitable priority
[17:17] <cjwatson> jiboumans: I'm subscribed to everything in the platform queue ;-)
[17:17] <ttx> heh
[17:17] <jiboumans> cjwatson: i admire your mailreading skills sir
[17:17] <cjwatson> maildeleting
[17:17] <slangasek> read mail real fast
[17:18] <cjwatson> (it's a useful opportunity to prioritise)
[17:18] <slangasek> [TOPIC] Security Team
[17:18] <MootBot> New Topic:  Security Team
[17:18] <slangasek> jiboumans, ttx: thanks
[17:18] <jdstrand> o/
[17:18] <slangasek> (skipping over kernel team for the moment, as I'm just going to be dumping their report in from email)
[17:18] <jdstrand> as always, https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:19] <slangasek> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:19] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:20] <jdstrand> things are still going ok. we haven't had to postpone any more since last week
[17:20] <jdstrand> we are still plugging away at our blueprints
[17:21] <jdstrand> other than the fact that it would be nice to have a png file instead of svg so we can include it in moin and have it display in firefox, I don't have much to report
[17:21]  * cjwatson seconds that
[17:22] <slangasek> :)
[17:22] <slangasek> jdstrand: looks good to me, thanks
[17:22] <slangasek> [TOPIC] Kernel Team
[17:22] <MootBot> New Topic:  Kernel Team
[17:22] <jdstrand> sure, np
[17:22] <slangasek> kernel team is off sprinting, so I have the report by email
[17:22] <slangasek> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[17:22] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[17:23] <slangasek> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20lucid-alpha-2
[17:23] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20lucid-alpha-2
[17:24] <slangasek> "Two Apparmor deliverables while complete were pushed out to immediately after alpha-2 due to unresolved bugs, they are expected to hit next week.  Boot performance has regressed significantly for the kernel with plymouth entering the initramfs.  suspend/resume testing plans are now in place for CELF et al with improved reporting on the cards.  Freescale imx51 hibernate is slated to work with some new patches from Freescale, testing in progress.  
[17:24] <slangasek> ... Freescale update to vendor supplied BSP complete. Marvell dove update to 2.6.32 based BSP should upload shortly."
[17:25] <slangasek> [TOPIC] Foundations Team
[17:25] <MootBot> New Topic:  Foundations Team
[17:25] <slangasek> (no, I won't take questions on the kernel ;)
[17:25] <slangasek> cjwatson: hi
[17:26] <cjwatson> apologies for shabby report this week (in particular I haven't had time to do any bug analysis); I've been off on another project, but I've broken the back of it now
[17:26] <cjwatson> Weekly summary:
[17:26] <cjwatson>  software-center bug-fixing and work on reviews branch
[17:26] <cjwatson>  nearly there on translated keyboard names in installer
[17:26] <cjwatson>  starting on jockey support in ubiquity
[17:26] <cjwatson>  grub2 reliable device ids well in progress, preliminary patch under review
[17:26] <cjwatson>  test rebuild with gcc-4.5, much bug-reporting
[17:26] <cjwatson> alpha-2 specs:
[17:26] <cjwatson>  foundations-lucid-gfxboot-update half-postponed to alpha-3; blocked on DX team work
[17:26] <cjwatson>  foundations-lucid-boot-recovery not quite finished; still needs bug 505887, which I'll unblock today
[17:26] <cjwatson> alpha-3 specs:
[17:27] <cjwatson>  I've just made sure that everything essential/high is milestoned here (hence the massive jump today), except for distributed-development and daily-builds.  As a consequence we may find ourselves deferring a few things.
[17:27] <cjwatson>  I promoted foundations-lucid-oem-dvd-iso to High yesterday at the request of the OEM team, who are concerned about making sure this lands.
[17:27] <cjwatson>  The existing list for alpha-3 looks reasonably safe at this point, but we certainly have a *lot* to do.
[17:27] <cjwatson> In general: we were more or less on-track up to Christmas, but (as expected) the holidays left us well behind track and it's taking a while to catch up, so the charts aren't looking great.  We'll take a look at
[17:27] <cjwatson>  low- and medium-priority blueprints at the sprint, and very likely defer some.
[17:27] <cjwatson> [LINK] http://macaroni.ubuntu.com/~pitti/workitems/canonical-foundations-lucid-alpha-3.html
[17:27] <MootBot> LINK received:  http://macaroni.ubuntu.com/~pitti/workitems/canonical-foundations-lucid-alpha-3.html
[17:27] <cjwatson> [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:27] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:28] <slangasek> foundations-lucid-oem-dvd-iso> hum, where is that expected to live?
[17:29] <slangasek> (seeing as cdimage is already at the limit)
[17:29] <cjwatson> read the spec :-)
[17:29] <slangasek> ok :)
[17:29] <cjwatson> it calls for a script to generate ISOs on request, rather than hosting more on cdimage, for exactly that reason
[17:29] <cjwatson> and OEM Services will deal with generation and testing
[17:30] <slangasek> no questions here
[17:31] <slangasek> anyone else?
[17:31] <slangasek> [TOPIC] MOTU
[17:31] <MootBot> New Topic:  MOTU
[17:31] <slangasek> cjwatson: thanks
[17:31] <slangasek> ScottK: hi
[17:31] <ScottK> Hello
[17:31] <ScottK> No excitement in MOTU.
[17:31] <slangasek> are we ready to rm the unbuildable packages yet? :)
[17:31] <ScottK> We could, as always, use more help on NBS transitions.
[17:31]  * slangasek nods
[17:32] <ScottK> slangasek: No.  I need to hunt the individual down.
[17:33] <slangasek> ScottK: ok.  anything else?
[17:33] <ScottK> boost1.38 transition is almost done
[17:33] <ScottK> That's it.
[17:33] <slangasek> \o/
[17:33] <slangasek> ScottK: ok, thanks
[17:33] <slangasek> #endmeeting
[17:33] <MootBot> Meeting finished at 11:33.
[17:33] <slangasek> and thanks, all!