[02:29] <ccheney> kirkland, looks like the bug showed up due to this change (still need to verify though) http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=cc56f7de7f00d188c7c4da1e9861581853b9e92f
[09:43] <huats> morning
[15:57]  * ara waves
[15:58]  * Ian_corne waves back
[15:58] <rickspencer3> hi ara, Ian_corne
[15:59] <ttx> o/
[15:59] <Riddell> afternoon
[15:59] <rickspencer3> hi ttx, Riddell
[15:59] <seb128> hey rickspencer3, hey everybody!
[15:59] <rickspencer3> hi seb128
[16:00] <rickspencer3> I never ran this meeting before, so hoping folks can help me out if I get off track or do something incorrectly
[16:00] <rickspencer3> #startmeeting
[16:00]  * ttx prepares a long stick
[16:00] <MootBot> Meeting started at 10:00. The chair is rickspencer3.
[16:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:00] <cjwatson> afternoon
[16:00] <rickspencer3> [LINK] http://wiki.ubuntu.com/ReleaseTeam/Meeting/Agenda
[16:00] <MootBot> LINK received:  http://wiki.ubuntu.com/ReleaseTeam/Meeting/Agenda
[16:00] <rickspencer3> hi cjwatson
[16:01] <rickspencer3> so looking at the burndowns
[16:01] <rickspencer3> https://wiki.ubuntu.com/ReleaseTeam/FeatureStatus
[16:01] <rickspencer3> guess I should do ..
[16:01] <rickspencer3> [LINK]https://wiki.ubuntu.com/ReleaseTeam/FeatureStatus
[16:01] <MootBot> LINK received: https://wiki.ubuntu.com/ReleaseTeam/FeatureStatus
[16:01] <rickspencer3> looks like Ubuntu folks are pretty much on track
[16:02] <rickspencer3> ignoring the "All" chart, looks like nothing has changed much wrt trend line
[16:02] <rickspencer3> I guess we are at Freeze for A2 starting yesterday
[16:03] <cjwatson> it's a bit later for alphas
[16:03] <rickspencer3> only bug fixes from here out
[16:03] <cjwatson> I expect we'll freeze end of Monday / start of Tuesday or so
[16:03] <rickspencer3> yeah, I was going to say, I hear this is a bit more of a target than a limit
[16:03] <rickspencer3> to use cjwatson vernacular
[16:03] <cjwatson> well, we only usually have a full-week freeze for the important milestones
[16:03] <Riddell> who's the alpha 2 release manager?
[16:03] <cjwatson> I think my phrase was the other way round :-)
[16:04] <rickspencer3> cjwatson, right, for important milstones, Freezes are limits, not targets
[16:04] <cjwatson> rickspencer3: ah :)
[16:04] <rickspencer3> Riddell, good question
[16:04] <rickspencer3> as robbiew is on vacation next week
[16:04] <cjwatson> I was expecting to be landed with the bulk of CD-building work and such
[16:04] <rickspencer3> cjwatson, are  you release manager?
[16:04] <rickspencer3> for A2, I mean?
[16:04] <cjwatson> call me release engineer perhaps. :)
[16:05] <rickspencer3> cjwatson, if there are related tasks and such that someone else could handle to lighten your load, let me know
[16:05] <rickspencer3> we can find someone, but probably work on that outside the meeting
[16:06] <rickspencer3> so, I guess we rock the agenda now
[16:06] <rickspencer3> [TOPIC] QA
[16:06] <MootBot> New Topic:  QA
[16:06] <rickspencer3> ara?
[16:07] <ara> OK, it is the first time for me as well, so I guess I'll just follow the agenda
[16:07] <ara> Results for HW testing:
[16:07] <ara> http://people.canonical.com/~fader/hw-testing/current.html
[16:07] <ara> Laptops:
[16:07] <ara>     passed:   49 (78%)    failed:    0 ( 0%)    untested: 14 (22%)
[16:07] <ara> Servers:
[16:07] <ara>     passed:   45 (70%)    failed:    0 ( 0%)    untested: 19 (30%)
[16:07] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:08] <ara> The HW cert team have gotten most of the laptops tested now, as cyphermox solved the environmental issue that was preventing them from being tested.
[16:08]  * ara hugs cyphermox 
[16:08] <ara> There are still a number of systems that were not tested this week; This will be a top priority for fader to get fixed next week when he's back from Taipei.
[16:09] <rickspencer3> ara, are the untested numbers expected to be 0% next week?
[16:09] <ara> yes, fader will work on it
[16:09] <rickspencer3> k
[16:09]  * ara hugs fader as well, the hw cert team rocks!
[16:09] <ara> he couldn't work on those from Taipei
[16:09] <rickspencer3> undestood
[16:10] <rickspencer3> ara, the QA work items are well below the trend line
[16:10] <rickspencer3> so, looks like everything is going to adjusted plan on that regard
[16:10] <ara> yes, numbers look like it
[16:10] <ara> qa-maverick-iso-testcases-review - 100% complete
[16:10] <ara> qa-maverick-mentoring-program - 100% complete
[16:10] <ara> qa-maverick-improve-iso-tracker - 100% of targeted alpha-2 workitems finished
[16:10] <ara> server-maverick-uec-testing - 73% of targetef to alpha-2 workitems finished
[16:11] <rickspencer3> is euc testing blocked, or just not finished yet?
[16:11] <ttx> 73% ? was 60% 10 min ago :)
[16:11] <rickspencer3> heh, suggests "just not finished yet"
[16:11] <ttx> Just not finished yet, i'll come back in my part
[16:11] <rickspencer3> ara, anything to add
[16:11] <rickspencer3> any questions for ara?
[16:12] <ara> not from side, at least you have any questions
[16:12] <rickspencer3> moving on
[16:12] <rickspencer3> [TOPIC]security
[16:12] <MootBot> New Topic: security
[16:12] <jdstrand> o/
[16:12] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Maverick
[16:12] <rickspencer3> fire away
[16:12] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Maverick
[16:12] <jdstrand> mdeslaur is continuing to make progress on security-m-tls-renegotiation-updates, our last remaining essential blueprint.
[16:13] <jdstrand> kees got his patches into the Ubuntu kernel for security-m-kernel-hardening a while ago, and is continuing to work on getting his changes accepted upstream. Based on upstream feedback, he has written a new LSM, 'Yama' and submitted it upstream. The ultimate goal is to get Yama upstream and working with AppArmor (and other LSMs).
[16:13] <jdstrand> (and get that all in Ubuntu to reduce the delta)
[16:13] <jdstrand> I've been working primarily with chriscoulson and the mozillateam on the firefox 3.6 transition. It was discovered that the openjdk-6 plugin does not work with Jaunty or Karmic, which has set back publication for those releases. Because firefox 3.6 requires NPAPI, the current plan is to test openjdk-6 from lucid-proposed on Jaunty and Karmic. Once packages are built in the ubuntu-mozilla-security PPA, TCK tests will be run on them. Assuming 
[16:14] <jdstrand> As such, I've decided to publish the update for Hardy and Lucid early next week (hopefully Monday). People interested in following the status of the security publication can read https://wiki.ubuntu.com/Testing/Firefox3.6.4Upgrade/SecurityPublication.
[16:14] <rickspencer3> who specifically is running the TCK tests?
[16:14] <jdstrand> [LINK] https://wiki.ubuntu.com/Testing/Firefox3.6.4Upgrade/SecurityPublication
[16:14] <MootBot> LINK received:  https://wiki.ubuntu.com/Testing/Firefox3.6.4Upgrade/SecurityPublication
[16:14] <jdstrand> sbeattie will be performing the TCK testing on openjdk-6 for Jaunty and Karmic. He is working with doko on this, and utilizing the prior work he did while on the QA team.
[16:15] <jdstrand> sbeattie is also
[16:15] <jdstrand> coordinating the work for the new 2.5.1 stable release of AppArmor (userspace), which should identify areas of opportunity for SRU in lucid.
[16:15] <jdstrand> On a personal note, I'd like to point out how great it has been working with chriscoulson and micahg. They've been doing a thorough job on the transition and have been willing and able to fix any issues that come up.
[16:15] <jdstrand> :)
[16:15] <jdstrand> We have no milestoned bugs, and we followed up on our release-targeted bugs and are either waiting on feedback from reporters/upstream or time to fix them.
[16:16] <rickspencer3> sounds solid
[16:16] <rickspencer3> anything to add? any questions?
[16:16] <jdstrand> (that's it from me)
[16:16] <rickspencer3> thanks jdstrand
[16:16] <rickspencer3> moving on
[16:16] <jdstrand> sure! :)
[16:16] <rickspencer3> [TOPIC]Kernel
[16:16] <MootBot> New Topic: Kernel
[16:17] <ogasawara> Overall Kernel Team status is summarised at the first URL below, including the item(s) called out in the agenda.  Our burndown chart for Alpha2 is at the third URL, and our overall burndown chart is at the fourth:
[16:17] <ogasawara> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[16:17] <ogasawara> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone maverick-alpha-2
[16:17] <ogasawara> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team-maverick-alpha-2.html
[16:17] <ogasawara> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team.svg
[16:17] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[16:17] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone maverick-alpha-2
[16:17] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team-maverick-alpha-2.html
[16:17] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team.svg
[16:17] <ogasawara> On the item noted in the agenda, the status is as follows:
[16:17] <ogasawara> * Bug 588861
[16:17] <ogasawara> Tim is currently assigned to this bug and working with ccheney to build and test bisected kernels.  I believe they may have isolated the offending commit just this morning.  It's not completely understood why the patch is causing the regression as it seems to just implement more rigorous error checking.  Tim is going to contact the patch authors for further discussions.  This appears to be too late to be resolved in the
[16:17] <ogasawara> kernel by Alpha2.  We're in discussion with the server team for alternative Alpha2 solutions.  ttx will bring this up under the Server Team's status during the meeting.
[16:17] <ttx> yes
[16:17] <ogasawara> As a general status, assuming no kitten killers come our way, we uploaded our final Alpha2 kernel yesterday:
[16:17] <ogasawara> [LINK] https://launchpad.net/ubuntu/+source/linux/2.6.35-6.7
[16:17] <MootBot> LINK received:  https://launchpad.net/ubuntu/+source/linux/2.6.35-6.7
[16:18] <ogasawara> This most notably contains a sync with the latest Apparmor patches, upstream evdev buffer patches, and upstream magicmouse scrolling improvements. We are also below our burdown chart overall as well as below our Alpha2 burdown chart with 89% work items complete.  The remaining Alpha2 work items are not release critical.
[16:18] <ogasawara> Questions?
[16:18] <rickspencer3> thanks ogasawara
[16:18] <rickspencer3> moving on
[16:19] <rickspencer3> [TOPIC]Foundations
[16:19] <MootBot> New Topic: Foundations
[16:19] <cjwatson> [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Maverick
[16:19] <cjwatson> We are below our trend line at last, although much of this has been by means of postponements so the next alpha will be interesting.
[16:19] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Maverick
[16:19] <cjwatson>  * UbuntuSpec:arm-m-tool-chain-selection (0%): Test rebuild still likely to happen for alpha-2, although decision will probably be later.
[16:19] <cjwatson>  * UbuntuSpec:desktop-maverick-language-selector-code-changes (100%): Our side of this is done.
[16:19] <cjwatson> * UbuntuSpec:foundations-maverick-btrfs-support (100%): Complete for alpha-2.  First pass at technical work on grub2 for alpha-3 has been completed, but may stall on licensing issues beyond our control; we've tried to initiate discussion on this.
[16:19] <cjwatson> * UbuntuSpec:foundations-maverick-buy-something (25%): Work items no longer reflecting reality due to server-side changes.  Michael will get these updated today.
[16:19] <cjwatson>  * UbuntuSpec:foundations-m-uefi-support (83%): Essentially complete for alpha-2.  Ran into a few problems at the UEFI Plugfest which should now be fixed.  Open work item for kernel team to investigate status of Intel graphics drivers on EFI.  Deferred investigation of multi-catalog images; this has been started but will probably not be completed in time for alpha-2.
[16:19] <cjwatson>  * UbuntuSpec:server-maverick-uec-liveusb (100%): Merged live-uec seed.  We have a work item for alpha-3 to start building CD images of this.
[16:19] <cjwatson> We've got a jump on a few of our alpha-3 specs as well.  See our release status page for details.
[16:19] <cjwatson> No major bugs, but:
[16:19] <cjwatson>  * Bug:588677 - slideshow show 10.04 LTS in maverick alpha1: had been waiting for a complete slideshow drop, but it might be worth fixing this before that if only to cut down on duplicates from ISO testing
[16:19] <cjwatson>  * Bug:596136 - package binutils-multiarch 2.20.1-3ubuntu6 failed to install/upgrade: this has been reassigned to hardening-wrapper, so can it have the security team's attention?
[16:19] <cjwatson> Fixed:
[16:20] <cjwatson>  * Bug:588633 - textual splash says 10.04 for maverick
[16:20] <cjwatson> My main concern for alpha-2 at the moment is that the archive is in a somewhat wonky state regarding installability and such (e.g. we haven't had working alternate or server CD builds for a few days), and we'll need to pay special attention to that over the next few days.
[16:20] <cjwatson> --
[16:20] <cjwatson> (PS the most immediate cause of alternate/server build breakage is fixed, but we'll see what's next)
[16:21] <rickspencer3> ara ...
[16:21] <rickspencer3>   * Bug:596136 - package binutils-multiarch 2.20.1-3ubuntu6 failed to install/upgrade: this has been reassigned to hardening-wrapper, so can it have the security team's attention?
[16:21] <rickspencer3> ?
[16:21] <jdstrand> cjwatson: re hardening-wrapper, I'll point kees at it
[16:21] <rickspencer3> oops
[16:21] <cjwatson> jdstrand: thanks
[16:21] <rickspencer3> sorry ara, wrong person
[16:21] <rickspencer3> thanks jdstrand
[16:21] <rickspencer3> :/
[16:22] <jdstrand> :)
[16:22] <rickspencer3> thanks cjwatson
[16:22] <ara> :)
[16:22] <rickspencer3> cjwatson, in terms of A3 ...
[16:22] <rickspencer3> (and this is relevant for everyone)
[16:22] <rickspencer3> please use the # of WI that were done in A2 as an initial target for A3
[16:23] <rickspencer3> I'd rather if we commit to the targeted items in A3, and we have more capacity, we just do more work items
[16:23] <rickspencer3> this will help us be a bit more predictable, but shouldn't make us less productive
[16:23] <cjwatson> that's fair, I'll talk about it with Robbie when he gets back
[16:23] <rickspencer3> thanks cjwatson
[16:23] <cjwatson> although I do hope that we'll be able to be significantly more productive for a3
[16:23] <cjwatson> particularly with e.g. the platform sprint in theree
[16:24] <rickspencer3> cjwatson, ack
[16:24] <rickspencer3> also, I wouldn't say Foundations was not productive
[16:24] <cjwatson> I generally feel we've been under where we should be
[16:24] <cjwatson> obviously other factors etc.
[16:24] <rickspencer3> well, work items is only one of the things the team works on
[16:24] <ttx> rickspencer3: the work-item-tracker could seed the trends line to the previous iteration completed wi number
[16:24] <rickspencer3> so I don't think I would say the team was not productive
[16:24] <rickspencer3> ttx sure, good idea
[16:25] <ttx> that wouldn't be worse than the current "whatever is the number at the start of cycle" current situation
[16:25] <cjwatson> agreed
[16:25] <rickspencer3> sure
[16:25] <rickspencer3> let's move on, though
[16:25] <rickspencer3> thanks again cjwatson
[16:26] <rickspencer3> [TOPIC]Server
[16:26] <MootBot> New Topic: Server
[16:26] <ttx> o/
[16:26] <ttx> Updated status is at: https://wiki.ubuntu.com/ServerTeam/MaverickReleaseStatus
[16:26] <ttx> Our good-looking burndown chart can be visited at: http://people.canonical.com/~pitti/workitems/maverick/canonical-server-maverick-alpha-2.html
[16:26] <ttx> Alpha2-milestoned bugs:
[16:26] <ttx> Bug 588861 (davewalker/rtg) -- will come back to this one in just a few
[16:26] <ttx> Bug 595421 (davewalker) -- Fixed, pending upload
[16:26] <ttx> Bug 588410 (davewalker) -- Fixed, pending upload
[16:26] <ttx> Bug 594372 (ccheney/mterry) -- Pending MIR team review
[16:26] <ttx> Bug 574554 (ccheney/zul) -- Needs a review from Foundations' upstart review team
[16:27] <ttx> (hint hint)
[16:27] <ttx> On the specs side...
[16:27] <ttx> Alpha2-milestoned specs status
[16:27] <ttx> server-maverick-new-stacks (60%): One potential package to upload to universe, will be done by next week
[16:27] <ttx> server-maverick-sru-process (67%): On track, setup of new process will be finalized early next week
[16:27] <ttx> server-maverick-cloud-datastores (86%): Only one communication/documentation work item left
[16:27] <ttx> server-maverick-cloud-init (93%): Only one communication/documentation work item left
[16:27] <rickspencer3> ttx, is bug #574554 blocking A2?
[16:28] <ttx> no, it was a target, but can be postponed
[16:28] <ttx> its part of the MIR
[16:28] <ttx> Specs with remaining work items affected by Alpha2 freeze:
[16:28] <ttx> server-maverick-uec-eucalyptus-next (80%): Needs to land a eucalyptus package fixing the already-mentioned alpha2-critical issues
[16:28] <ttx> Other Critical/High Specs < 85% completion:
[16:28] <ttx> server-maverick-hypervisor (82%): Only triage tasks left
[16:28] <ttx> server-maverick-hadoop-pig (67%): Remaining tasks will be completed at Hadoop Summit next week
[16:28] <ttx> server-maverick-uec-testing (60%): Work in progress, still on track for Alpha2 milestone release
[16:29] <ttx> Other Medium/Low Specs < 70% completion:
[16:29] <ttx> server-maverick-uds-web20-workloads (67%): Two packages to upload to universe
[16:29] <ttx> server-maverick-cloud-kernel-upgrades (57%): Tech investigation tasks, will be completed by next week
[16:29] <ttx> server-maverick-uds-seed-review (50%): package set contents review, should be completed by next week
[16:29] <ttx> server-maverick-uds-cloud-loadbalancing (50%): Tech investigation task left, will be completed by next week
[16:29] <ttx> So it's all looking good, we don't expect spillover to A3
[16:29] <ttx> Questions on that, before I switch to bug 588861 ?
[16:30] <ttx> ok, moving on...
[16:30] <ttx> So I wanted to talk about bug 588861 as there is a decision for the release team to take for Alpha2 on that
[16:30] <ttx> This bug is a java file decryption error in Eucalyptus, only when run on a recent (2.6.33+) kernel
[16:30] <ttx> The net effect being it prevents to register any image in Eucalyptus, so you just can't use it.
[16:31] <ttx> tgardner and ccheney bisected the regression up to a precise commit early in 2.6.33.
[16:31] <rickspencer3> that sounds like a blocker
[16:31] <ttx> We don't understand yet why it's causing that decryption error in Javaland.
[16:31] <ttx> The options for A2 are:
[16:31] <ttx> (1) ship with a kernel which reverts that commit (but we are late for that, as ogasawara mentioned)
[16:31] <ttx> (2) ship Ubuntu Server Maverick Alpha2 with a Lucid kernel (is that even possible ?)
[16:31] <cjwatson> (2) is not possible
[16:31] <ttx> (3) releasenote, for UEC installs, the process to revert to a Lucid kernel to workaround the issue
[16:31] <ttx> cjwatson: right
[16:32] <ttx> (4) .... anything else ?
[16:32] <cjwatson> (well, not without changing a vast amount of stuff)
[16:32]  * ogasawara would vote for #3
[16:32] <rickspencer3> cjwatson, could folks who want to test uec install the lucid kernel themselves, in a manual way? as work around?
[16:32] <rickspencer3> ook
[16:32] <rickspencer3> that's option #3
[16:32] <rickspencer3> n,
[16:32] <rickspencer3> nm, even
[16:32]  * rickspencer3 votes for option #3 too
[16:32] <Daviey> ttx: Could we not have a PPA of the kernel with the commit redacted, for A2?
[16:32] <ttx> if we can come up with a simple way of doing #3, maybe that's the best option
[16:33] <Daviey> Then that is *closer* to Maverick A2 vanilla
[16:33] <tgardner> Daviey, we could
[16:33] <ttx> Daviey: yes, that could be how we present the #3 option
[16:33] <rickspencer3> well, presumably, if the bug is not fixed in A2, it will be fixed quite soon
[16:33] <rickspencer3> so it seems the effort of creating the PPA may be better channeled to working on the bug
[16:33] <tgardner> rickspencer3, I've got the full court press going on it
[16:33] <rickspencer3> thoughts?
[16:34] <rickspencer3> so perhaps you install A2, apt-get dist-upgrade, and you're good to go?
[16:34] <rickspencer3> tgardner ^ what are the chances of that?
[16:34] <jdstrand> if 3 is not done right/relatively easily, then you will lose testers
[16:34] <tgardner> pretty good.
[16:35] <rickspencer3> jdstrand, but if #3 is "dist-upgrade" what could be easier?
[16:35] <rickspencer3> ttx, how many testers do you expect to have who will be blocked by this bug?
[16:35] <jdstrand> sure. that is as easy as it gets :) (I typed that before I saw that option :)
[16:35] <ttx> rickspencer3: I'd like to keep a workaround in the milestone, so that the UEC actually gets tested at milestone
[16:36] <ttx> but if PPA is costly...
[16:36] <rickspencer3> ttx, but if there is a new kernel with the bug fix in place by next Thursday, then your testers are in fine shape, right?
[16:36] <ttx> I prefer to releasenote "this is how you get past the bug" rather than "we'll probably be fixing it soon". But if soon < release
[16:36] <ttx> rickspencer3: yes
[16:36] <rickspencer3> ttx, ack
[16:37] <tgardner> ttx, the PPA thing will take ogasawara10 minutes to prep and upload
[16:37] <ttx> tgardner: so we can make a call on the releasenote text at the last minute, ack
[16:37] <Daviey> I believe it was only one person that had issues with the bug during A1... and that same person found the work around, so i'm not sure it's a *big* concern going from iso to $whatever to get testing in A2.
[16:37] <rickspencer3> so we can defer this decision to next Wednesday?
[16:37] <rickspencer3> depending on what are the fact at the time?
[16:37] <rickspencer3> I'll take that as a "yes"
[16:38] <cjwatson> rickspencer3: certainly one can downgrade, although it would be fiddly
[16:38] <rickspencer3> cjwatson, ack
[16:38] <ttx> +1 from me
[16:38] <rickspencer3> I think it's best to keep resources focused on fixing bugs in the kernel
[16:38] <ogasawara> works for me
[16:38] <ttx> thanks everyone, I'm done
[16:38] <rickspencer3> if on Wednesday, it's not fixed, then can ogasawara prepare the PPA and then ttx can release note that?
[16:39] <rickspencer3> I think there is a bot macro for this?
[16:39] <ogasawara> rickspencer3: sounds good
[16:39] <ttx> otherwise I'll releasenote: "dist-upgrade before registering your first image"
[16:39] <ttx> I'll write that down in the bug
[16:40] <rickspencer3> [AGREED]if on Wednesday bug #588861 is not fixed in kernel, then can ogasawara prepare the PPA and then ttx can release note the PPA, otherwise ttx to release note to dist-upgrade
[16:40] <MootBot> AGREED received: if on Wednesday bug #588861 is not fixed in kernel, then can ogasawara prepare the PPA and then ttx can release note the PPA, otherwise ttx to release note to dist-upgrade
[16:40] <rickspencer3> sweet!
[16:40]  * rickspencer3 rocks the irc bot
[16:40] <rickspencer3> moving on
[16:40] <ttx> rickspencer3: beware, you're starting to enjoy it
[16:40] <rickspencer3> [TOPIC]Desktop
[16:40] <MootBot> New Topic: Desktop
[16:40] <seb128> hey
[16:40] <seb128> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:40] <seb128> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-maverick-alpha-2.html
[16:40] <seb128>  
[16:40] <seb128> We are on track for alpha2, got most of our workitems done and postponed a few to the next iteration
[16:40] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:40] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-maverick-alpha-2.html
[16:40] <seb128> .
[16:40] <seb128> * specs completed: desktop-maverick-xorg-in-mm dx-m-unity-une-integration vfat-noexec
[16:40] <seb128> * specs still requiring work on the a2 list: desktop-maverick-easy-wayland-testing desktop-maverick-video-bugs-in-the-kms-world
[16:40] <seb128> * the previous specs are ppa testing and bug triage work so not blocking alpha2 in any way and we can postpone some items if required
[16:40] <seb128> .
[16:41] <seb128> maverick bugs:
[16:41] <seb128> * bug:594214: "Preferences" and "Setup new device..." options are broken in bluetooth-applet": not investigated yet not a blocker issue either
[16:41] <seb128> lucid sru bugs:
[16:41] <seb128> * bug:525807 [upstream] [3.2.1] OOo Slide Show and Fullscreen modes - not full screen under compiz: should be worked next week
[16:41] <seb128> * bug:578281 Add search plugin for Baidu: not worked yet, our firefox maintainer has been busy with security updates
[16:41] <seb128>  
[16:41] <seb128> question: when is the upload line for updates that will go to lucid .1?
[16:41] <seb128>  
[16:41] <rickspencer3> seb128, I promised that we would get bug #578281 into 10.04.1!
[16:41] <seb128> (that's it from me, questions next, then Riddell for Kubuntu)
[16:42] <seb128> rickspencer3, give me an extra webbrowser maintainer and I will get it fixed for .1! ;-)
[16:42] <rickspencer3> *sigh*
[16:42] <seb128> rickspencer3, joke aside, see the question for the upload target for .1
[16:42] <rickspencer3> I would have to defer to cjwatson
[16:42] <rickspencer3> can we take this offline?
[16:42] <seb128> new firefox is available so the security work will be over in the next days
[16:42] <rickspencer3> ok
[16:42] <seb128> I think chrisccoulson will be able to work on this issue on time for lucid .1
[16:42] <rickspencer3> let's figure it out next week, I don't this it's A2 specific
[16:43] <seb128> right
[16:43] <Riddell> it's an interesting question to all though, should probably be announced on ubuntu-devel-announce
[16:43] <ogra> ++
[16:43] <rickspencer3> [ACTION]rickspencer3 to get someone to announce 10.04.1 timelines
[16:43] <MootBot> ACTION received: rickspencer3 to get someone to announce 10.04.1 timelines
[16:43] <rickspencer3> Riddell, is that what you were looking for?
[16:43] <Riddell> yes
[16:43] <ogra> freezes rather i guess :)
[16:43] <rickspencer3> ogra, ack
[16:43] <rickspencer3> Riddell, Kubuntu?
[16:44] <Riddell>  * I promoted a load of packages to main so koffice, rekonq, kdevelop, kdeedu and kdenetwork are now in main fully featured, MIRs still needing done
[16:44] <Riddell>  * plasma-netbook and plasma-desktop are now on the same CD, chosen at load based on screen size, so kubuntu netbook images should be going away soon and kubuntu normal images will want arm builds
[16:44] <Riddell>  * images are oversized as a result of above, but there's bits we can get rid of
[16:44] <Riddell>  * arm builds going "slowly, and painfully" or "All good except bindings and edu" depending on your point of view
[16:44] <Riddell>  * Kubuntu Ninjas are putting their moves on KDE SC 4.5 release candidate tars which are due for release by upstream later today
[16:44] <ogra> Riddell, with arm do you refer to images or to packages ?
[16:45] <Riddell> ogra: arm builds refers to packages
[16:45] <ogra> NCommander will take massive care of the KDE stuff after A2
[16:45] <Riddell> he's a star
[16:45] <Riddell> actually he'll be with me at Akademy after alpha 2
[16:45] <ogra> we're currently all focused on getting our A2 images working, after that there is manpower available for the rest of the world :)
[16:46] <ogra> yes
[16:46] <ogra> but he can work remotely :)
[16:46] <rickspencer3> Riddell, all done?
[16:46] <cjwatson> upload line: good question, to be honest I am not up to date on the .1 schedule
[16:46] <rickspencer3> move on?
[16:46] <ogra> i know he is already looking into it with half an eye
[16:46] <cjwatson> it should be pretty soon
[16:46] <Riddell> rickspencer3: move on
[16:47] <rickspencer3> [TOPIC}Dx
[16:47] <MootBot> New Topic: [TOPIC}Dx
[16:47] <davidbarth> hi
[16:47] <davidbarth> https://wiki.ubuntu.com/DesktopExperienceTeam/MaverickReleaseStatus
[16:47] <cjwatson> upload line> I think it should probably be this time next week
[16:47] <davidbarth> http://people.canonical.com/~pitti/workitems/maverick/canonical-dx-team-maverick-alpha-2.html (not up to date though, i just moved the last w.i. this afternoon)
[16:47] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-dx-team-maverick-alpha-2.html (not up to date though, i just moved the last w.i. this afternoon)
[16:48] <davidbarth> new this week, we're also putting some fancy release notes for a2: https://wiki.ubuntu.com/DesktopExperienceTeam/MaverickAlpha2ReleaseNotes
[16:48] <davidbarth> now back to the serious stuff
[16:48] <davidbarth>  * [[https://blueprints.edge.launchpad.net/ubuntu/+spec/dx-m-app-menubar|dx-m-app-menubar]]
[16:48] <davidbarth>   * delivered release for a2, including GTK & QT menus support, app. switching, transient windows, shortcuts and dynamic menu items support; lots of those came together in the last 4 days
[16:48] <davidbarth>   * bug reports piling up though, we're going through that to 1. clean old reports, 2. identify remaining critical issues
[16:48] <davidbarth>   * landed in universe
[16:48] <davidbarth>   * agreement to turn the feature on by default on UNE, only if we demonstrate that most reported bugs are fixed by Monday
[16:48] <davidbarth>   * see https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationMenu for how you can help
[16:48] <davidbarth>  * [[https://blueprints.edge.launchpad.net/ubuntu/+spec/dx-m-gtk-enhancements|dx-m-gtk-enhancements]]
[16:48] <davidbarth>   * csd out for  maverick
[16:48] <davidbarth>   * argb out for a2; will be retested for a3
[16:48] <davidbarth>  * [[https://blueprints.edge.launchpad.net/ubuntu/+spec/dx-m-sound-menu-v2|dx-m-sound-menu-v2]]
[16:48] <davidbarth>   * new release for a2; delivers the app registration and remote control features that were planned
[16:48] <davidbarth>   * RB, VLC & Amarok enabled to support the latest menu features
[16:49] <davidbarth>   * generally on track for Maverick
[16:49] <davidbarth> that's the desktop part
[16:49] <seb128> "only if we demonstrate that most reported bugs are fixed by Monday" is a "bugs are triaged" rather
[16:49] <seb128> or "somebody is showing interest for those"
[16:49] <davidbarth> a human readable summary would say: menubar on the edge, sound is all good, and csd is out
[16:49] <davidbarth> seb128: right
[16:50] <davidbarth> now on for the unity part, unity rocks ;)
[16:50] <davidbarth>  * [[https://blueprints.edge.launchpad.net/ubuntu/+spec/dx-m-unity-une-integration|dx-m-unity-une-integration]]
[16:50] <davidbarth>   * New weekly release (now on time), featuring the new files and apps place
[16:50] <davidbarth>   * Lucid PPA also available at: http://launchpad.net/~canonical-dx-team/+archive/une
[16:50] <davidbarth> and sadly, the connman menu is still behind:
[16:50] <davidbarth>  * [[https://blueprints.edge.launchpad.net/ubuntu/+spec/dx-m-indicator-network|dx-m-indicator-network]]
[16:50] <davidbarth>   * Prototype Settings UI + some minor changes to the panel indicator released
[16:50] <davidbarth>   * Weekly batch of backend bugfixes submitted to connman/ofono
[16:50] <davidbarth>   * *Not* on track for A2 for the UI part, not on track for data gathering / testing; not on track for packaging / integration in Maverick
[16:51] <davidbarth> for unity: the new places and search feature are on track; the launcher refresh too; the network menu is not
[16:51] <davidbarth> on the network menu, we're continuing our efforts nonetheless, knowing we have a good fallback plan
[16:52] <davidbarth> questions?
[16:52] <rickspencer3> thanks davidbarth
[16:52] <rickspencer3> moving on
[16:52] <rickspencer3> [TOPIC]RM
[16:52] <MootBot> New Topic: RM
[16:52] <rickspencer3> [TOPIC]ARM
[16:52] <MootBot> New Topic: ARM
[16:52] <ogra> thats me !
[16:53]  * ogra waves
[16:53] <ogra> Detailed status at: https://wiki.ubuntu.com/ARMTeam/ReleaseStatus/Maverick
[16:53] <ogra> ..
[16:53] <ogra> Short Summary:
[16:53] <ogra> - omap kernel and preinstalled image enablement: omap4 kernel package available, omap3 kernel 594382 was fixed but 597904 broke display output now.
[16:53] <ogra> - ongoing work on main ftbfs: gobject-introspection was fixed
[16:53] <ogra>  - KDE/Kubuntu stack still broken due to kdebindings, work ongoing
[16:53] <ogra> - work towards A2 for preinstalled omap (oem like) netbook images
[16:53] <ogra> - MIR for jasper-initramfs (595947) is a **critical blocker** grinding us to a full halt wrt image builds
[16:53] <ogra> ..
[16:53] <ogra> A2 status:
[16:53] <ogra> http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-maverick-alpha-2.html
[16:53] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-maverick-alpha-2.html
[16:53] <ogra> ..
[16:53] <ogra> A2 targeted specs:
[16:53] <ogra> still only https://blueprints.launchpad.net/ubuntu/+spec/preinstalled-sd-card-images-for-omap
[16:53] <ogra> ..
[16:53] <ogra> Blocking bugs:
[16:53] <ogra> bug 595947
[16:53] <ogra> bug 589624
[16:53] <ogra> bug 594382
[16:53] <ogra> ..
[16:53] <ogra> General:
[16:53] <ogra> - ARM team would like to propose to rethink the way of MIR handling and to have a discussion about this at the sprint, currently the backlog grows constantly while the MIR team shrinks.
[16:54] <rickspencer3> ogra, I think the MIR situation is under discussion, on a @u-devel thread, is it not?
[16:54] <asac> didnt send the mail yet
[16:54] <ogra> oh, i missed that if it is
[16:54] <asac> but ogra knows that we are working on that :)
[16:54] <ogra> i just promised the team to bring it up here :)
[16:54] <seb128> there was an email about it?
[16:54] <rickspencer3> in other words, this is a BIG topic, and I think we probably don't want to try to resolve in the 6 minutes left for this meeting ;)
[16:55] <rickspencer3> ogra, we hear you though
[16:55] <ogra> rickspencer3, "rethink the way of MIR handling and to have a discussion about this at the sprint"
[16:55] <asac> ogra: your team suffered the least so far i tell you :)
[16:55] <ogra> i didnt talk about this meeting ;)
[16:55] <rickspencer3> ogra, ack
[16:55] <ogra> asac, well, we wont make A2 due to it
[16:55] <rickspencer3> I was really just trying to head of discussion ;)
[16:55] <asac> ogra: lets talk offline. there is _no_ reason to not make A2 because of that
[16:56] <rickspencer3> [ACTION]asac to seed MRI disussion on @u-devel, all to discuss at sprint
[16:56] <MootBot> ACTION received: asac to seed MRI disussion on @u-devel, all to discuss at sprint
[16:56] <asac> thx
[16:56] <ogra> thanks
[16:56] <rickspencer3> ogra, awesome, seems ARM is quite on track
[16:56] <rickspencer3> ready to move on?
[16:56] <ogra> any non MIR questions ?
[16:56] <ogra> if not, i'm done :)
[16:56] <rickspencer3> k
[16:56] <asac> ogra: do you have capacity to do the une-launcher spec?
[16:56] <rickspencer3> moving on
[16:56] <rickspencer3> oops
[16:56] <ogra> asac, i can tell you after A2
[16:57] <asac> ok
[16:57] <ogra> we might though :)
[16:57] <asac> move on
[16:57] <rickspencer3> ok
[16:57] <rickspencer3> [TOPIC]MOTU
[16:57] <MootBot> New Topic: MOTU
[16:58] <rickspencer3> is this normally ScottK ?
[16:58] <asac> yes
[16:58] <rickspencer3> moving on
[16:58] <rickspencer3> [TOPIC]Downstream Deriviatives
[16:58] <MootBot> New Topic: Downstream Deriviatives
[16:59] <asac> thats me ;) (helping out why jamie is on vac)
[16:59] <rickspencer3> arm-m-tool-chain-selection (Linaro) - 0% complete
[16:59] <ScottK> Yes.
[16:59] <ScottK> Nothing exciting to report.
[16:59] <ScottK> Now that DIF is passed, we can work on banging things into shape.
[16:59] <rickspencer3> asac, robbiew had ^ on the agenda
[16:59] <asac> rickspencer3: that spec (according to robbiew) is doko material
[16:59] <rickspencer3> I see
[16:59] <asac> besides from that we have
[16:59] <asac> [LINK] https://wiki.ubuntu.com/LinaroTeam/ReleaseStatus/Maverick
[16:59] <MootBot> LINK received:  https://wiki.ubuntu.com/LinaroTeam/ReleaseStatus/Maverick
[17:00] <asac> and a bunch of burndowns:
[17:00] <asac> [LINK] http://people.canonical.com/~pitti/workitems/maverick/arm-foundations.html
[17:00] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/arm-foundations.html
[17:00] <asac> [LINK] http://people.canonical.com/~pitti/workitems/maverick/arm-foundations-maverick-alpha-2.html
[17:00] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/arm-foundations-maverick-alpha-2.html
[17:00] <asac> [LINK] http://people.canonical.com/~pitti/workitems/maverick/arm-infrastructure.html
[17:00] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/arm-infrastructure.html
[17:00] <asac> [LINK] http://people.canonical.com/~pitti/workitems/maverick/arm-infrastructure-maverick-alpha-2.html
[17:00] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/arm-infrastructure-maverick-alpha-2.html
[17:00] <asac> [LINK] http://people.canonical.com/~pitti/workitems/maverick/arm-user-platforms.html
[17:00] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/arm-user-platforms.html
[17:00] <asac> [LINK] http://people.canonical.com/~pitti/workitems/maverick/arm-user-platforms-maverick-alpha-2.html
[17:00] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/arm-user-platforms-maverick-alpha-2.html
[17:00] <asac> so to give a summary:
[17:00] <asac>  * Overall: behind on alpha-2 work items, but catching up now that planning is finished. * Foundations: good progress on cross compiling base system spec * Infrastructure: approved specs; image builder spec stalled due to LexBuilder open sourcing; archive specs working with Launchpad guys
[17:00] <asac>  * User Platforms: maverick hadless image set-up; qt-qws packaging finished and call for testing; clutk porting sgtalled - looking for opengl ES 2. shader expert; worked on getting a X11 driver cookbook up for ARM drivers; telepony packaging started
[17:00] <asac> ouch
[17:00] <asac> * Overall: behind on alpha-2 work items, but catching up now that planning is finished.
[17:01] <asac>  * Foundations: good progress on cross compiling base system spec
[17:01] <asac>  * Infrastructure: approved specs; image builder spec stalled due to LexBuilder open sourcing; archive specs working with Launchpad guys
[17:01] <asac>  * User Platforms: maverick headless image set-up; qt-qws packaging finished and call for testing; clutk porting stalled - looking for opengl ES 2. shader expert; worked on getting a X11 driver cookbook up for ARM drivers; telepony packaging started
[17:01] <asac> and as already rasied a request for help on:
[17:01] <asac> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/arm-m-une-launcher-on-arm
[17:01] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/arm-m-une-launcher-on-arm
[17:02] <asac> that spec isnt that critical for linaro, while its probably critical for ubuntu on arm
[17:02] <asac> so i feel bad about it maybe getting not done because we own it ... at best we would move that to a shared ubuntu desktop/arm place
[17:03] <rickspencer3> asac, in any case, there is no point in having the work items targeted for A2 if there is no hope of them getting done
[17:03] <rickspencer3> in general, perhaps you should postpone work items across the board to get at least near the trend lines?
[17:03] <asac> yes ... we will do that
[17:04] <rickspencer3> asac, I guess jamie will drive that?
[17:04] <asac> the postponing? no. each team would drive that. i will carry that forward
[17:04] <asac> of course jamie is supposed to ensure its happening ... but he is gone for another week or two
[17:05] <rickspencer3> [ACTION]asac to work with teams to postpone Linaro work items to get teams to trend lines
[17:05] <MootBot> ACTION received: asac to work with teams to postpone Linaro work items to get teams to trend lines
[17:05] <asac> thx
[17:05] <asac> any other questions besids some more whipping?
[17:05] <asac> ;)
[17:05] <rickspencer3> asac, who should own figuring out if we are going to do this:
[17:05] <rickspencer3> https://blueprints.edge.launchpad.net/ubuntu/+spec/arm-m-une-launcher-on-arm
[17:06] <rickspencer3> ?
[17:06] <asac> rickspencer3: ogra said he would decided at a3 ... so maybe he?
[17:06] <rickspencer3> well, if ogra says they can't do it ... then what?
[17:06] <ogra> we're getting a new team member in 10 days or so
[17:07] <ogra> so there is a possibility that we have the manpower
[17:07] <asac> rickspencer3: i dont know. for linaro it could be dropped. but i think for ubuntu its high or essential
[17:07] <rickspencer3> asac, in that case that ARM can't do it, I think you need to make the call whether we postpone to maverick+1 or if you can find someone else to do it
[17:07] <asac> at least a lightweight variant for that spec needs to happen to have a good experience
[17:07] <rickspencer3> but I don't think we should let it dangle
[17:08] <ogra> rickspencer3, its only dangling for a week
[17:08] <ogra> i can respond next meeting to the request
[17:08] <rickspencer3> fine then
[17:08] <asac> rickspencer3: if nothing is getting done on this spec for maverick, then the default ARM image will fail to the default X session
[17:08] <rickspencer3> [ACTION]ogra to accept https://blueprints.edge.launchpad.net/ubuntu/+spec/arm-m-une-launcher-on-arm for ARM team, or to postpone to maverick+1
[17:08] <MootBot> ACTION received: ogra to accept https://blueprints.edge.launchpad.net/ubuntu/+spec/arm-m-une-launcher-on-arm for ARM team, or to postpone to maverick+1
[17:08] <asac> we need at least a lightweight solution
[17:08] <ogra> its just that we dont have a single working arm kernel yet so cant buiuld images and i want to have spare cycles in the team once we build them
[17:09] <ogra> since i expect a good bunch of bugs
[17:09] <asac> so ... i think it definitly should be move to another team. even if it gets dropped from maverick
[17:10] <ogra> we're kind of blocked on all fronts in arm atm and once we are released we'll drown in bugs i fear
[17:10] <asac> so can i set assignee to ubuntu-arm team and then you decide what to do?
[17:10] <ogra> asac, your spec is about the automatic detection though
[17:10] <ogra> the lightweight session will be there
[17:11] <ogra> thats covered in https://blueprints.launchpad.net/ubuntu/+spec/mobile-m-lightweight-panel-for-efl
[17:11] <asac> ogra: it has automatic detection work items, but the general spirit is: get to a state where you can log in after boot and get at least some desktop (defaulting to efl would be the light weight variant)
[17:12]  * ogra doesnt think *that* needs a spec since it is ubuntus default session on arm
[17:12] <rickspencer3> this seems like it needs to be sorted for A3 planning
[17:12] <ogra> yes
[17:12] <ogra> offline likely
[17:12] <rickspencer3> asac, ogra, can you guys get this sorted by next meeting?
[17:12] <asac> ogra: ltes take that offline. its not the default. lucid default did the fallback. so now it just fails iirc
[17:12] <ogra> yes
[17:13] <asac> ack
[17:13] <asac> give us an action
[17:13] <asac> thanks
[17:13] <ogra> asac, i dont have working images to verify :)
[17:13] <rickspencer3> ok, moving on
[17:13] <ogra> so i wouldnt even know it fails
[17:13] <rickspencer3> next is ...
[17:13] <rickspencer3> 10.04.1 LTS Agenda
[17:13] <rickspencer3> I think we already covered this by saying that we need to get our act together ASAP
[17:14] <cjwatson> https://wiki.ubuntu.com/PointReleaseProcess is the rubric for this
[17:14] <rickspencer3> seb128, cjwatson, desktop and foundations each have Critical/High bugs
[17:15] <rickspencer3> 10.04.1 is on July 29th
[17:15] <seb128> right
[17:15] <rickspencer3> that puts us at the end of this timeframe:
[17:15] <rickspencer3> Release minus 2 months:
[17:15] <rickspencer3> Process stable release updates as normal. For hardware-enabling fixes, the package should be tested on the affected hardware prior to submitting to sign-off for -proposed.
[17:15] <rickspencer3> Discuss the possibility of a Canonical press release for the point release with Gerry Carr.
[17:15] <rickspencer3> Liaise with IS, QA, and certification to arrange for testing resources.
[17:15] <rickspencer3>  
[17:15] <rickspencer3> and hair-raisingly close to this one
[17:16] <rickspencer3> Release minus 1 month:
[17:16] <rickspencer3> In coordination with QA, verify that all candidate bugs are fixed.
[17:16] <rickspencer3> Upload a new base-files package to -proposed to bump the lsb_release description (example for 6.06.2). Do not change the DISTRIB_RELEASE value, which is used programmatically by third-party software.
[17:16] <rickspencer3> If the kernel or associated modules have been changed, upload debian-installer after all the binaries are in place. If the ABI changed, make sure to take account of this throughout debian-installer/build/config/ and in the installer seed for all flavours being built.
[17:16] <rickspencer3> Notify Evan Dandrea to update umenu and wubi for the point release.
[17:16] <rickspencer3> Change cdimage/bin/make-web-indices, cdimage/bin/publish-release, and debian-cd/CONF.sh to use the new release version number.
[17:16] <rickspencer3> Change cdimage/bin/run-germinate and debian-cd/CONF.sh to build from -proposed temporarily.
[17:16] <rickspencer3> Build CD images (which will be published on cdimage.ubuntu.com) and smoke-test in some convenient environment to check for obvious failures.
[17:16] <rickspencer3> "
[17:16] <rickspencer3>  In coordination with QA, verify that all candidate bugs are fixed."
[17:16] <cjwatson> the upload/change items there are all very easy, BTW
[17:16] <rickspencer3> I am skeptical that all candidate bugs are fixed
[17:16] <cjwatson> kind of five minutes each
[17:17] <rickspencer3> cjwatson, can you please spare 1 hour on Monday to help me reason this out?
[17:17] <rickspencer3> then I can do my best to get everyone on the train
[17:17] <cjwatson> absolutely
[17:17] <rickspencer3> looking over this list, I feel that the current 10.0.4.1 date is achievable
[17:17] <rickspencer3> any specific comments, questions, concerns, discussion regarding 10.04.1 atm?
[17:18] <rickspencer3> going ...
[17:18] <rickspencer3> going ...
[17:18] <rickspencer3> #endmeeting
[17:18] <MootBot> Meeting finished at 11:18.
[17:18] <rickspencer3> thanks everyone!
[17:18] <seb128> thanks ;-)
[17:18] <rickspencer3> sorry the meeting ran over :/
[17:18] <rickspencer3> lesson here is, don't let rickspencer3 run the release meeting!
[17:19] <seb128> rickspencer3, nice try to avoid getting that task again but I'm not sure that's going to work ;-)
[17:19] <ara> it is schedule to run for one hour and a half, isn't it?
[17:19] <rickspencer3> am I that transparent?
[17:19] <rickspencer3> ara are you saying I have another 12 minutes to harangue  you?
[17:20] <rickspencer3> in that case, I have pet bugs you could look at
[17:20] <ara> thanks, but no, thanks
[17:20] <rickspencer3> :)
[17:20] <ara> :)