[14:02] <lag> o/
[14:06] <mpoirier> o/
[14:07] <lag> No meeting today then
[14:08] <rsalveti> well, we should have it, waiting NCommander
[14:08] <GrueMaster> give NCommandera few minutes to shake off the cob webs.
[14:09] <davidm> G'day
[14:10] <GrueMaster> NCommander has been successfully poked.
[14:11] <NCommander> #startmeeting
[14:11] <MootBot> Meeting started at 08:11. The chair is NCommander.
[14:11] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[14:11] <ogra_ac> question is if he stays awake :)
[14:11]  * NCommander had a time zone adjustment failure
[14:11] <GrueMaster> Does he ever?
[14:11] <ogra_ac> heh
[14:12] <NCommander> [link] https://wiki.ubuntu.com/MobileTeam/Meeting/2010/20101005
[14:12] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2010/20101005
[14:12] <NCommander> No Action items or special items from last week
[14:12] <NCommander> [topic] Burndown chart
[14:12] <MootBot> New Topic:  Burndown chart
[14:12] <NCommander> [link] http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html
[14:12] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html
[14:13] <NCommander> [link] http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-ubuntu-10.10.html
[14:13] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-ubuntu-10.10.html
[14:13] <ogra_ac> OMG !
[14:14] <ogra_ac> we're deep red
[14:14] <NCommander> so there's one last action item left open, persia, can you close it? :-)
[14:14] <ogra_ac> persia, !!!
[14:14] <ogra_ac> NCommander, there are three
[14:14] <ogra_ac> (see the overall chart)
[14:16] <NCommander> [action] persia to close and/or postpone his remaining action items for 10.10
[14:16] <MootBot> ACTION received:  persia to close and/or postpone his remaining action items for 10.10
[14:16] <NCommander> anything else on the charts?
[14:16] <ogra_ac> what about the buglist ?
[14:16] <NCommander> [link] http://qa.ubuntu.com/reports/team-assigned/canonical-mobile-assigned-bug-tasks.html
[14:16] <MootBot> LINK received:  http://qa.ubuntu.com/reports/team-assigned/canonical-mobile-assigned-bug-tasks.html
[14:16] <NCommander> ogra_ac: that's separate from the burndown charts no?
[14:17] <ogra_ac> k
[14:17]  * ogra_ac vaguely remembers an action item for NCommander that doesnt seem to have been transferred ;)
[14:17] <ogra_ac> regarding the bugs :)
[14:18]  * NCommander doesn't :-)
[14:18] <NCommander> [action] NCommander to unassign himself from bugs (c/o)
[14:18] <MootBot> ACTION received:  NCommander to unassign himself from bugs (c/o)
[14:18] <NCommander> anything else on the bug list?
[14:19] <NCommander> I guess not
[14:19] <NCommander> [topic] Kernel Status (cooloney, mpoirier, lag)
[14:19] <MootBot> New Topic:  Kernel Status (cooloney, mpoirier, lag)
[14:19] <mpoirier> been working on b637947 all week - nothing else to report.
[14:19] <mpoirier> ..
[14:19] <ogra_ac> NCommander, dont you run so fast !
[14:19] <ogra_ac> 7me was just typing :P
[14:19] <ogra_ac> anyway
[14:19] <GrueMaster> bug 637947, maybe?
[14:20] <lag> o/
[14:20] <ogra_ac> we're working on it
[14:20] <ogra_ac> trying to get patches in today
[14:20] <ogra_ac> since thats the last chance to make the release
[14:21] <ogra_ac> can you guys make sure the kernel team is available for us to make uploads etc ?
[14:21] <NCommander> anything else from the kernel side?
[14:21] <lag> * Texas Instruments (ti-omap)
[14:21] <lag>    * PATCH    : IGEPv2's 6 patches are being worked into the SRU process (OMAP3)
[14:21] <lag>    * PATCH    : A new set of ftrace patches have been released - will integrate in Natty (OMAP3)
[14:21] <lag>    * PATCH    : Received patch from TI that enables passing the MAC address to the kernel from u-boot
[14:21] <lag>    * ON GOING : B637947 Latest sound patches are available from TI - configuration problem still exists
[14:21] <lag>    * ON GOING : B653002 Currently under investigation - TI suspects a silicone problem
[14:21] <lag>    * ON GOING : B637947 Still working on the userspace ALSA or PulseAudio configuration
[14:21] <lag>    * FIXED    : B647890 Fixed the building error
[14:21] <lag>    * WORKROUND: B633227 Applied patches from Nicolas to set memory 2G:2G - enabled the errata for PL310 lx20 cache controller
[14:21] <lag>    * MISC     : "fakeroot debian/rules binary-omap" seems to be broken on Natty - investigation is required
[14:22] <lag>    * MISC     : Some members of the Arm team received ES2.1 boards - so far it's as good as ES2.0
[14:22] <lag> ..
[14:22] <NCommander> ah, there's lag
[14:22] <lag> :D
[14:22] <lag> Hi ya
[14:22] <ogra_ac> yeah, we have slow network NCommander :)
[14:22] <ogra_ac> lots of lag :)
[14:22] <ogra_ac> lag, Natty ?!?!
[14:23] <ogra_ac> lag, please stop building omap3 in natty
[14:23] <ogra_ac> that either needs to go into a feature branch again or we need to swithc to linaro
[14:23] <lag> Speak to mpoirier
[14:23]  * ogra_ac will add a spec for that
[14:23] <mpoirier> ogra_ac: that's a company decision...
[14:23] <NCommander> ogra_ac: yes well, its not my fault you forgot to pack a high-speed interneet connection from Germany ogra_ac !
[14:23] <ogra_ac> mpoirier, no
[14:24] <ogra_ac> mpoirier, we cant work that way, omap3 needs fixes at times where the mainline kernel cant be uploaded anymore ...
[14:24] <ogra_ac> mpoirier, building omap3 delays the mainline kernel builds a lot
[14:24] <ogra_ac> both teams suffer from it being in the core tree
[14:25] <mpoirier> who's idea was it to put it in the core tree ?
[14:25] <ogra_ac> thats an unbearable situation, we either need to change it back or completely switch to linaro kernels
[14:25] <ogra_ac> mpoirier, lool's with agreement from the kernel team
[14:25] <mpoirier> I suppose it was put there for a reason...
[14:25] <ogra_ac> we tried it one release, its not workable
[14:25] <ogra_ac> yes, "because we can"
[14:26] <ogra_ac> its a test that failed badly
[14:26] <mpoirier> then let's get the concerned parties together and settle on the issue.
[14:26] <ogra_ac> we would have IGEP2 support properly working if we had a feature branch with separate policies
[14:26] <ogra_ac> mpoirier, thats what i said above
[14:26] <ogra_ac> i'll create a spec for discussion at UDS
[14:26] <NCommander> ogra_ac: mpoirier I think UDS would be the proper venue for this discussion TBH
[14:27] <NCommander> ah
[14:27] <ogra_ac> just dont waste time on natty branches now
[14:27] <NCommander> :-)
[14:27] <NCommander> anyway, can I move on?
[14:27] <ogra_ac> yep
[14:27] <ogra_ac> just again
[14:28] <NCommander> [topic] QA Status (GrueMaster)
[14:28] <MootBot> New Topic:  QA Status (GrueMaster)
[14:28] <ogra_ac> we need exceptoions and uploads
[14:28] <ogra_ac> *today*
[14:28] <GrueMaster> RC Testing went well.  No major issues found, except the missing installer icon on dove images, which is now fixed.
[14:28] <ogra_ac> please someone be available from the kernel team to do that
[14:28] <GrueMaster> Netboot image for omap was missing modules for usb.  No keyboard, no networking.  Colin has worked to fix this for release.
[14:29] <ogra_ac> \o/
[14:29] <mpoirier> GrueMaster: omap3 or 4 ? when was that discovered ?
[14:29] <ogra_ac> ast week
[14:29] <ogra_ac> *last
[14:29] <GrueMaster> omap/omap3/beagle.
[14:30] <ogra_ac> we dont build netboot for omap4
[14:30] <ogra_ac> and omap3 are just a nice to have goodie
[14:30] <ogra_ac> leftover from luicd
[14:30] <GrueMaster> This is not a kernel issue.  This was an issue with debian installer.
[14:30] <ogra_ac> right, that too
[14:30] <GrueMaster> The modules were not included in the netboot image.
[14:31] <ogra_ac> NCommander, move if there are no other questions
[14:32] <NCommander> [topic] ARM Porting/FTBFS status (NCommander, dyfet)
[14:32] <MootBot> New Topic:  ARM Porting/FTBFS status (NCommander, dyfet)
[14:32] <dyfet> We (ncommander and I) discussed plt-scheme yesterday
[14:32] <NCommander> FTBFS looks relatively happy on all architectures, not just ARM excluding openjjfk
[14:32] <ogra_ac> below 100 pkgs !!!
[14:32] <ogra_ac> thanks to doko !!!
[14:33] <ogra_ac> we owe him a lot, he's the only one really working actively on that list atm
[14:33] <NCommander> +1 beer to doko
[14:33] <ogra_ac> +3 from me :)
[14:34] <NCommander> :-)
[14:34] <NCommander> [topic] ARM Image Status (ogra, NCommander)
[14:34] <MootBot> New Topic:  ARM Image Status (ogra, NCommander)
[14:34] <ogra_ac> omap4 runs on panda ES2.1 !!!
[14:34]  * NCommander heard
[14:34] <GrueMaster> WOOT!
[14:34] <ogra_ac> all open RC bugs were fixed apart from sound
[14:34] <NCommander> Its great when hardware is properly designed to be relatively compatible and sane
[14:35] <NCommander> Dove is currently looking good, sound issue aside
[14:35] <ogra_ac> not sure about omap3 (i didnt test since a while) or dove
[14:35] <ogra_ac> GrueMaster, how did omap3 look last time you tested ?
[14:35] <NCommander> Installer icon shows up where it should be, and its relatively fast and responsive
[14:35] <GrueMaster> Looked good, other than the missing modules in the netboot image.
[14:35] <NCommander> cool
[14:36] <GrueMaster> Audio has the same issues across the board, though.
[14:36] <GrueMaster> omap, omap4, dove.
[14:36] <ogra_ac> omap and dove can have SRUs for that
[14:36] <ogra_ac> omap4 will get fixes today
[14:36] <NCommander> I think we're in very good shape at this point and I think armel+dove and possibly armel+omap can go out the door on 10.10.10
[14:36] <ogra_ac> (or workarounds)
[14:36] <ogra_ac> omap4 too
[14:36] <rsalveti> hopefully
[14:37] <ogra_ac> we only need the xloader patch
[14:37] <ogra_ac> that should be enough, workst case all other fixes can be SRUs
[14:37] <NCommander> ogra_ac: check thatwith davidm since thats contray to what I heard yesterday
[14:37] <ogra_ac> xloader and uboot are the things we cant update
[14:37] <NCommander> otherwise, WOO
[14:37] <ogra_ac> if they are in shape omap4 is ready for 10.10.10
[14:38] <ogra_ac> davidm, ^^^^
[14:38] <ogra_ac> please agree
[14:38] <NCommander> ogra_ac: why can't you update XLO or u-boot
[14:38] <ogra_ac> NCommander, because they are not handled by packages in the image
[14:38] <ogra_ac> we treat them like BIOS
[14:38] <NCommander> ogra_ac: ah. fair enough.We could fix it, but it would be fugly
[14:38] <ogra_ac> a way we inherit through using flash-kernel from debian
[14:38] <ogra_ac> NCommander, lets fix it in a non ugly way
[14:39] <ogra_ac> SPEC !!!
[14:39] <NCommander> ogra_ac: right
[14:39] <ogra_ac> will need good thinking through
[14:39] <NCommander> [action] ogra + davidm to determine armel+omap4 releasability and notify the release team with the result
[14:39] <MootBot> ACTION received:  ogra + davidm to determine armel+omap4 releasability and notify the release team with the result
[14:39] <ogra_ac> ++
[14:39] <ogra_ac> thanks
[14:39] <ogra_ac> i'll be able to tell tonight
[14:40] <NCommander> [topic] Any Other Business
[14:40] <MootBot> New Topic:  Any Other Business
[14:40] <ogra_ac> really depends on the kernel team
[14:40] <davidm> ogra_ac, theree were NO kernel changes for OMAP 4?
[14:40] <ogra_ac> we need an uploader for the sound fix
[14:40] <ogra_ac> davidm, apart from sound ? no
[14:40] <ogra_ac> davidm, es2.1 should work out of the box with the xloader changes
[14:40] <davidm> ogra_ac, lets have a talk later
[14:40] <ogra_ac> yep
[14:40] <ogra_ac> lets wait how today at TI turns out
[14:41] <ogra_ac> we can say for sure by end of day
[14:41] <rsalveti> robclark is just testing the instabilities issues we saw yesterday
[14:41] <rsalveti> so soon we should know better if it works or not
[14:41] <rsalveti> but I'd say that we just need x-loader fixes
[14:41] <ogra_ac> ++
[14:42] <NCommander> anything else left for this meeting?
[14:42] <NCommander> Or can I close it out?
[14:42] <rsalveti> nops, hopefully we'll be on-line sooner today
[14:42] <ogra_ac> activity reports !!
[14:42] <ogra_ac> dont foget them :)
[14:42] <rsalveti> I did mine ;-)
[14:42] <ogra_ac> rsalveti rocks
[14:42] <NCommander> rsalveti: maybe one of you should buy a prepaid broadband solutoin and make a hotspot
[14:42] <ogra_ac> (and he's the only one here)
[14:42] <ogra_ac> NCommander, THATS WHAT WE USE
[14:43] <ogra_ac> OOPS
[14:43] <rsalveti> yup :-)
[14:43] <ogra_ac> damned caps
[14:43] <NCommander> ogra_ac: so when you run out of bandwidth on AT&T they make you use all caps?< i didn't know that!
[14:43]  * NCommander runs.
[14:43] <NCommander> anyway, about to close the meeting
[14:43] <NCommander> going once
[14:44]  * ogra_ac slaps NCommander with a holiday inn pancake
[14:44] <NCommander> mmmmm, tasty
[14:44] <GrueMaster> So ogra_ac, does thisw mean you will do a status report too?
[14:44]  * ogra_ac slaps GrueMaster  with a holiday inn pancake
[14:44]  * GrueMaster has bacon and will slap back.
[14:45] <ogra_ac> greasy meeting !
[14:45]  * NCommander notes that ogra_ac and GrueMaster should get a room to save all our visions.
[14:45] <NCommander> anyway
[14:45] <ogra_ac> NCommander, quick close the meeting
[14:45] <NCommander> going once
[14:45] <NCommander> twice
[14:45] <NCommander> three times
[14:45] <NCommander> #endmeeting
[14:45] <MootBot> Meeting finished at 08:45.
[14:45]  * NCommander resets his alarm to respect the local time
[14:51] <lool> mpoirier, ogra_ac: Sorry, I didn't follow; what was my decision wiht the kernel team agreement?
[14:52] <mpoirier> lool, at one point or another omap3 became part of mainstream.
[14:53] <mpoirier> since this it the time I got hired, I *think* lucide was a topic branch and was wrapped in mainstream for maverick.
[14:54] <kees> \o
[14:55] <ogra_ac> lool, having omap built from the main tree is a pain for everyone
[14:56] <ogra_ac> lool, so i want either a topic branch for natty again or directly switch to linaro
[14:56]  * ogra_ac takes further discussion to #ubuntu-arm
[14:56] <lool> I think this is a large topic
[14:57] <ogra_ac> yep
[15:02] <mdz> pitti: hi
[15:02] <cjwatson> hello
[15:03] <cjwatson> gosh, am I chair
[15:03] <cjwatson> kees: around?
[15:03] <cjwatson> ah yes
[15:03] <mdz> ah, so you are
[15:03] <mdz> I thought it was pitti, but that's the meeting I missed
[15:03] <cjwatson> no obvious sign of Keybuk; pinged sabdfl
[15:04] <pitti> hello
[15:04] <pitti> cjwatson: sabdfl is on a conference
[15:04] <pitti> he asked to be skipped on the chair rotation
[15:04] <cjwatson> aha
[15:04] <pitti> so he might lag or not be present at all
[15:04] <cjwatson> #startmeeting
[15:04] <MootBot> Meeting started at 09:04. The chair is cjwatson.
[15:04] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:04] <cjwatson> [TOPIC] Action review
[15:04] <MootBot> New Topic:  Action review
[15:04] <cjwatson> Martin Pitt to ask Martin Pool about bzr self test instructions on installed system
[15:05] <cjwatson> pitti: ?
[15:05] <kees> cjwatson: yup
[15:05] <kees> cjwatson: he asked, but I didn't see a reply
[15:06] <pitti> cjwatson: done
[15:06] <pitti> he replied
[15:06] <cjwatson> Kees to add bzr self test to qa-regression-testing project
[15:06] <pitti> and even better, they seemed to have made a lot of fixes
[15:06] <pitti> bzr 2.0.3 should have a fully working test suite
[15:06] <kees> cjwatson: did that
[15:06] <pitti> or .2 even
[15:06] <cjwatson> Martin to add bzr microrelease exception to StableReleasePolicy
[15:07] <pitti> done
[15:07] <cjwatson> excellent
[15:07] <cjwatson> [TOPIC] Decide/document ubuntu-archive interaction with ARB packages
[15:07] <MootBot> New Topic:  Decide/document ubuntu-archive interaction with ARB packages
[15:07] <cjwatson> [LINK] https://lists.ubuntu.com/archives/technical-board/2010-September/000516.html
[15:07] <MootBot> LINK received:  https://lists.ubuntu.com/archives/technical-board/2010-September/000516.html
[15:08] <cjwatson> I don't remember whether we discussed this, or if so what the outcome was
[15:08] <cjwatson> normally, one function of the archive admins is to at least ensure legality of distribution
[15:08] <mdz> it's new to me, though I missed the previous meeting
[15:08] <cjwatson> which is more or less the bare minimum
[15:09] <cjwatson> this wasn't in the previous meeting; ScottK asked about it on our list, although he apologised that he wouldn't be able to make it to this meeting
[15:10] <mdz> so the question is whether archive admins will have responsibility for reviewing ARB packages as well as other kinds of packages?
[15:10] <cjwatson> my memory is that extras.ubuntu.com is actually a mirror of a PPA owned by the ARB
[15:10] <mdz> is there anyone else in a position to do it?
[15:11] <cjwatson> which would mean that ubuntu-archive wouldn't actually naturally have access to it, only the ARB
[15:11] <mdz> the ARB themselves?
[15:11] <cjwatson> (ScottK may or may not be aware of this)
[15:11] <cjwatson> https://wiki.ubuntu.com/PostReleaseApps/Process is not terribly clear on the matter
[15:12] <cjwatson> if it's an ARB-owned PPA, then I think the answer is simple, but the process documentation needs to be expanded to mention that
[15:12] <mdz> sounds straightforward enough
[15:12] <cjwatson> does anyone know the answer to that authoritatively?
[15:12] <mdz> presumably there's an existing archive admin checklist which could be reused?
[15:12] <cjwatson> I knew a couple of months ago ...
[15:12] <mdz> I don't know about the PPA implementation
[15:13] <cjwatson> https://wiki.ubuntu.com/ArchiveAdministration#NEW%20handling has various things we do
[15:13] <mdz> rickspencer3 is here; I could ask him if he's likely to know
[15:13] <cjwatson> I think he would
[15:13] <cjwatson> please do
[15:13] <mdz> ok, I'll run over
[15:14] <mdz> cjwatson: he doesn't quite know
[15:14] <mdz> he redirected to mvo
[15:15] <mdz> mvo: around?
[15:16] <cjwatson> [ACTION] cjwatson to ensure that documentation on nature of extras.ubuntu.com archive makes it into process docs
[15:16] <MootBot> ACTION received:  cjwatson to ensure that documentation on nature of extras.ubuntu.com archive makes it into process docs
[15:16] <mdz> cjwatson: maybe we need to chase this offline
[15:16] <cjwatson> I think it's clear that that's needed no matter what
[15:16] <cjwatson> OK, I'll take an action and chase it up tomorrow probably
[15:16] <cjwatson> [ACTION] cjwatson to chase up archive processing details for extras.ubuntu.com
[15:16] <MootBot> ACTION received:  cjwatson to chase up archive processing details for extras.ubuntu.com
[15:16] <cjwatson> [TOPIC] Decide on permission changes documented in LP: 174375 - Matt Zimmerman
[15:16] <MootBot> New Topic:  Decide on permission changes documented in LP: 174375 - Matt Zimmerman
[15:17] <cjwatson> I already acked that bug both in person and in LP
[15:17] <mdz> bdmurray sent email to the mailing list and didn't get enough of a response to feel comfortable moving forward
[15:17] <mdz> I'm +1 on it
[15:17] <mdz> maybe we can just do a quick vote assuming folks have read it?
[15:17] <cjwatson> there seems to be slight pushback from LP over the split in responsibilities between spec management and release management, but I think that's the essence of the change we need and so we can't give ground there
[15:18] <cjwatson> anyone feel they need a few minutes to read over bug 174375?
[15:18] <kees> I've read it a few times now :)
[15:18] <mdz> https://lists.ubuntu.com/archives/technical-board/2010-August/000426.html
[15:18]  * pitti reads to refresh memory
[15:19] <mdz> is brian's proposal
[15:19] <mdz> which is also in the bug at https://bugs.edge.launchpad.net/launchpad-registry/+bug/174375/comments/4
[15:20] <mvo> mdz: yes, I'm around
[15:21] <mdz> mvo: the question earlier was whether extras.ubuntu.com is a mirror of a PPA owned by the ARB
[15:21] <mvo> mdz: yes, that is the case
[15:21] <mdz> mvo: thanks
[15:21] <mvo> yw
[15:22] <cjwatson> mvo: thank you, looks like that answers the question; I'll follow up with ScottK et al
[15:22] <mvo> thanks cjwatson
[15:22] <mdz> pitti: refreshed?
[15:22] <pitti> mdz: yes
[15:23] <cjwatson> [VOTE] Approve Brian's proposal for redesign of distribution driver permissions
[15:23] <MootBot> Please vote on:  Approve Brian's proposal for redesign of distribution driver permissions.
[15:23] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[15:23] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[15:23] <cjwatson> +1
[15:23] <MootBot> +1 received from cjwatson. 1 for, 0 against. 0 have abstained. Count is now 1
[15:23] <kees> +1
[15:23] <MootBot> +1 received from kees. 2 for, 0 against. 0 have abstained. Count is now 2
[15:23] <pitti> I think bug targetting needs to be more open than just release-managers; the rest looks fairly okay
[15:23] <pitti> if we understand "ubuntu drivers" as "team leads, tech leads, etc"
[15:24] <mdz> +1
[15:24] <MootBot> +1 received from mdz. 3 for, 0 against. 0 have abstained. Count is now 3
[15:24] <pitti> under that assumption,
[15:24] <pitti> +1
[15:24] <MootBot> +1 received from pitti. 4 for, 0 against. 0 have abstained. Count is now 4
[15:24] <cjwatson> pitti: I'm not too concerned about bug targeting, as long as we can control it independently from spec handling
[15:24] <cjwatson> (FAOD that doesn't affect my vote either way)
[15:24] <pitti> cjwatson: *nod*
[15:24] <mdz> yeah, the real change is making it a separate slot
[15:24] <cjwatson> [ENDVOTE]
[15:24] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
[15:24] <mdz> I'll go back to Brian and let him know we acked it, thanks
[15:24] <pitti> separating blueprints and bugs is the main goal here indeed
[15:24] <cjwatson> targeting: Brian says "should be fixed as long as it doesn't exclude uploaders" which is OK by me
[15:25] <pitti> right
[15:25] <cjwatson> [TOPIC] Scan the mailing list archive for anything we missed
[15:25] <MootBot> New Topic:  Scan the mailing list archive for anything we missed
[15:25] <cjwatson> the only thing I see is: is the security team still awaiting confirmation on what to do with chromium, or is that settled?
[15:25] <cjwatson> (sorry, I appear to be a stateless machine today)
[15:26] <kees> cjwatson: I think it's understood; we're just waiting for a final proposal from fta
[15:26] <pitti> I think there is a consensus there
[15:26] <kees> right
[15:26] <cjwatson> September's thread from https://lists.ubuntu.com/archives/technical-board/2010-September/000501.html is sort of ambiguous as to what to do with the waiting period
[15:26] <pitti> basically, throw out the upstream updates pretty much blindly
[15:26] <pitti> but it's not mature enough yet for main
[15:27] <cjwatson> absolutely agreed
[15:27] <kees> I think the waiting period needs to be dropped, but at the same time, debian/ changes should be limited
[15:27] <pitti> kees: well, perhaps dropped -> shortened
[15:27]  * kees nods
[15:27] <pitti> it should at least build and get a coarse upgrade/install test
[15:28] <kees> right, but I call that "testing" :)
[15:28] <pitti> we can drop the 7 days maturing period, but please let's not drop -proposed and at least quick verification
[15:28] <kees> yup
[15:28] <mdz> +2
[15:29] <jdstrand> is -proposed required?
[15:30] <jdstrand> as kees said, we require testing
[15:30] <pitti> uploading the stuff straight to -updates is way too risky IMHO
[15:30] <jdstrand> it won't ever blindly be uploaded
[15:30] <pitti> if it buids on amd64 and fails on i386, we create uninstallability, etc.
[15:30] <jdstrand> eg, I'd run it through qrt
[15:30] <jdstrand> pitti: sure, we test both i386 and amd64. it is part of the testing procedures
[15:31] <jdstrand> (that is part of the security team's checklist)
[15:31] <pitti> sounds good
[15:31] <jdstrand> I guess what I am getting at is this
[15:32] <jdstrand> I noticed yesterday that we are showing chromium as a supported browser in the maverick livecd slideshow
[15:32] <pitti> !?
[15:32] <jdstrand> yes, I was surprised too...
[15:32] <pitti> well, we'll keep it up to date either way
[15:33] <jdstrand> but the security team will just need to treat it like flashplugin-nonfree-- it is universe, but we know a ton of people use it
[15:33] <cjwatson> that seems realistic, yes
[15:33] <jdstrand> so we test it ourselves in a similar manner
[15:33] <jdstrand> ie, with all our checklists, etc, etc
[15:33] <pitti> i. e. it's not an OMGincident if it suddenly breaks with a particular web page
[15:34] <jdstrand> correct
[15:34] <jdstrand> and no USN
[15:34] <pitti> (chromiums seems to do that a lot, at least on our arm systems)
[15:34] <jdstrand> like I mentioned, we have a qrt script which should catch any really huge issues
[15:35] <jdstrand> (js, ssl, redirects, images, flash, java, etc, etc...)
[15:35] <pitti> jdstrand: wow, so you call it on different web page types and check that it doesn't "Aw, snap!"? nice
[15:35] <jdstrand> I'm happy to do all the pocket copying if it is required, but if we have the standing exception, and we treat it this way, I'm not sure it is
[15:36] <jdstrand> pitti: yes
[15:36] <jdstrand> it is semi-automatic
[15:36] <pitti> it seems to have worked pretty well with the last handful of updates
[15:36] <pitti> at least from my POV
[15:36] <jdstrand> ie, it requires you to be looking at the test as it runs and close the browser, but it leads you through repeatable tests
[15:36] <jdstrand> yes
[15:37] <cjwatson> ok, anything further on this?
[15:37] <pitti> so what's remaining on this?
[15:37] <pitti> standing SRU exception?
[15:38] <pitti> it seems to be pretty much without alternative
[15:38] <kees> yeah; should we vote on it?
[15:38] <cjwatson> I haven't heard any disagreement
[15:38] <jdstrand> yes. iirc fta is supposed to write something up formally. he isn't sure why that is required since it has been discussed at length, but I can try to prod him
[15:38] <pitti> without requiring the 7 days testing period, too
[15:38] <cjwatson> but why don't we vote on fta's proposal
[15:38] <cjwatson> when it arrives
[15:38] <pitti> *nod*
[15:39] <cjwatson> let's move on for now, then
[15:39] <jdstrand> (if he hasn't done so already,-- I am not up to date)
[15:39] <cjwatson> I haven't seen it
[15:39] <cjwatson> [TOPIC] Check up on community bugs (standing item)
[15:39] <MootBot> New Topic:  Check up on community bugs (standing item)
[15:39] <cjwatson> nothing except what we just discussed
[15:39] <cjwatson> [TOPIC] Select a chair for the next meeting
[15:39] <MootBot> New Topic:  Select a chair for the next meeting
[15:39] <cjwatson> I make it kees
[15:39] <kees> sounds good
[15:39] <cjwatson> [TOPIC] AOB
[15:39] <MootBot> New Topic:  AOB
[15:40] <cjwatson> going once
[15:40] <cjwatson> going twice
[15:40] <mdz> nothing from me
[15:40] <cjwatson> sold to the gentleman with the purple IRC client
[15:41] <cjwatson> #endmeeting
[15:41] <MootBot> Meeting finished at 09:41.
[15:41] <mdz> thanks, cjwatson
[15:41] <pitti> thanks everyone
[15:41] <kees> thanks!
[15:41]  * pitti hops to the next meeting
[17:59] <JFo> o/
[18:00] <apw> o/
[18:00] <cking_> \o
[18:00]  * ogasawara waves
[18:00] <mpoirier> o/
[18:00] <bjf> #startmeeting
[18:00] <MootBot> Meeting started at 12:00. The chair is bjf.
[18:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[18:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[18:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[18:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[18:00] <bjf> #
[18:00] <bjf> # NOTE: '..' indicates that you are finished with your input.
[18:00] <bjf> #
[18:01] <bjf> [TOPIC] ARM Status (lag)
[18:01] <MootBot> New Topic:  ARM Status (lag)
[18:01] <lag> * Texas Instruments (ti-omap)
[18:01] <lag>    * PATCH    : IGEPv2's 6 patches are being worked into the SRU process (OMAP3)
[18:01] <lag>    * PATCH    : A new set of ftrace patches have been released - will integrate in Natty (OMAP3)
[18:01] <lag>    * PATCH    : Received patch from TI that enables passing the MAC address to the kernel from u-boot
[18:01] <lag>    * ON GOING : B637947 Latest sound patches are available from TI - configuration problem still exists
[18:01] <lag>    * ON GOING : B653002 Currently under investigation - TI suspects a silicone problem
[18:01] <lag>    * ON GOING : B637947 Still working on the userspace ALSA or PulseAudio configuration
[18:01] <lag>    * FIXED    : B647890 Fixed the building error
[18:01] <lag>    * WORKROUND: B633227 Applied patches from Nicolas to set memory 2G:2G - enabled the errata for PL310 lx20 cache controller
[18:01] <lag>    * MISC     : "fakeroot debian/rules binary-omap" seems to be broken on Natty - investigation is required
[18:01] <lag>    * MISC     : Some members of the Arm team received ES2.1 boards - so far it's as good as ES2.0
[18:01] <lag> ..
[18:02] <bjf> [TOPIC] Release Metrics: (JFo)
[18:02] <MootBot> New Topic:  Release Metrics: (JFo)
[18:02] <JFo> Release Meeting Bugs (4 bugs, 9 Blueprints)
[18:02] <JFo> [18:02] <JFo>  * 2 linux kernel bugs (up 1)
[18:02] <JFo>  * 0 linux-fsl-imx51 bugs (no change)
[18:02] <JFo>  * 0 linux-ec2 bugs (no change)
[18:02] <JFo>  * 0 linux-mvl-dove bugs (no change)
[18:02] <JFo>  * 0 linux-ti-omap bugs (no change)
[18:02] <JFo>  * 0 linux-meta-ti-omap bug (no change)
[18:02] <JFo> [18:02] <JFo>  * 16 linux kernel bugs (up 3)
[18:02] <JFo>  * 0 linux-fsl-imx51 bugs (no change)
[18:02] <JFo>  * 0 linux-ec2 bugs (no change)
[18:02] <JFo>  * 2 linux-mvl-dove bugs (no change)
[18:02] <JFo>  * 0 linux-ti-omap bugs (no change)
[18:02] <JFo>  * 0 linux-meta-ti-omap bug (no change)
[18:02] <JFo> [18:02] <JFo>  * 14 blueprints (Including HWE Blueprints)
[18:02] <JFo> [18:03] <JFo>  * [[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on | Bugs with Patches]]
[18:03] <JFo>  * [[http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/ | Breakdown by status]]
[18:03] <JFo> ..
[18:03] <bjf> [TOPIC] Status: Maverick (ogasawara)
[18:03] <MootBot> New Topic:  Status: Maverick (ogasawara)
[18:03] <ogasawara> As mentioned last week, we've been queuing patches for Maverick SRU which includes the latest 2.6.35.5, 2.6.35.6, and 2.6.35.7 stable updates.  We are also planning a 0-day kernel upload which has been documented at bug 647071 .  I'm not aware of any kitten killer bugs for Maverick which would cause a last minute upload.  Obviously let us know if we've overlooked/missed anything.
[18:03] <ogasawara> ..
[18:04] <bjf> [TOPIC] Security & bugfix kernels - Lucid/Karmic/Jaunty/Hardy/Others (smb)
[18:04] <MootBot> New Topic:  Security & bugfix kernels - Lucid/Karmic/Jaunty/Hardy/Others (smb)
[18:04] <smb> ||                   || Upd./Sec.     || Proposed      || TiP || Verified    ||
[18:04] <smb> || Dapper: Kernel    || 2.6.15-55.88  ||               ||     ||             ||
[18:04] <smb> || Hardy:  Kernel    || 2.6.24-28.79  ||               ||     ||             ||
[18:04] <smb> || =       LRM       || 2.6.24.18-28.7||               ||     ||             ||
[18:04] <smb> || Jaunty: Kernel    || 2.6.28-19.65  ||               ||     ||             ||
[18:04] <smb> || Karmic: Kernel    || 2.6.31-22.65  || 2.6.31-22.66  ||  12 ||  1/ 4       ||
[18:04] <smb> || =       mvl-dove  || 2.6.31-214.30 || 2.6.31-214.32 ||  12 ||  1/ 4       ||
[18:04] <smb> || =       ec2       || 2.6.31-307.17 || 2.6.32-307.18 ||  12 ||  1/ 4       ||
[18:04] <smb> || Lucid:  Kernel    || 2.6.32-25.44  ||               ||     ||             ||
[18:04] <smb> || =       LBM       || 2.6.32-25.24  ||               ||     ||             ||
[18:04] <smb> || =       mvl-dove  || 2.6.32-211.27 ||               ||     ||             ||
[18:04] <smb> || =       fsl-imx51 || 2.6.31-608.20 ||               ||     ||             ||
[18:04] <smb> || =       ti-omap   || 2.6.33-502.10 || (in progress) ||     ||             ||
[18:04] <smb> || =       ec2       || 2.6.32-308.16 || 2.6.32-309.17 ||   0 ||  7/28       ||
[18:04] <smb> ..
[18:04] <bjf> [TOPIC] Incoming Bugs: Regressions (JFo)
[18:04] <MootBot> New Topic:  Incoming Bugs: Regressions (JFo)
[18:04] <JFo> 721 Maverick Bugs (up 92)
[18:05] <JFo> 1014 Lucid Bugs (up 36)
[18:05] <JFo> Current regression stats (broken down by release):
[18:05] <JFo> [18:05] <JFo>   * 364 maverick bugs (up 44)
[18:05] <JFo>   * 163 lucid bugs (up 3: to be converted to regression-release)
[18:05] <JFo> [18:05] <JFo>   * 64 lucid bugs (up 9)
[18:05] <JFo>   * 6 karmic bugs (down 1)
[18:05] <JFo>   * 4 jaunty bugs (no change)
[18:05] <JFo>   * 0 hardy bugs (no change)
[18:05] <JFo> [18:05] <JFo>   * 177 lucid bugs (up 7)
[18:05] <JFo>   * 37 karmic bugs (up 1)
[18:05] <JFo>   * 17 jaunty bugs (no change)
[18:05] <JFo>   * 2 hardy bugs (no change)
[18:05] <JFo> [18:05] <JFo>   * 6 lucid bugs (no change)
[18:05] <JFo>   * 1 karmic bug (no change)
[18:05] <JFo> ..
[18:05] <bjf> [TOPIC] Incoming Bugs: Bug day report (JFo)
[18:05] <MootBot> New Topic:  Incoming Bugs: Bug day report (JFo)
[18:05] <JFo> The Bug Day is today, so I don't have much information other than that. The next Bug Day will be Tuesday 19 October.
[18:05] <JFo> The focus will be on bugs with patches. We will be working to identify those bugs that have actual, relevant patches.
[18:05] <JFo> More details to follow on the wiki.
[18:05] <JFo> We will continue to have the Team Bug Day to address the Top 50 list as half days on Friday and Monday.
[18:05] <JFo> Reviewers, please take a look at your needs-review lists and help us keep the process moving. There are several lists that are not getting a look.
[18:05] <JFo> Please also take ownership of your bugs as you work them so we can get them fixed or otherwise off the list. There are a number in need of love.
[18:05] <JFo> There are several subsystems owned by all that need to be reviewed for inclusion in our top 50 list.
[18:06] <JFo> ..
[18:06] <bjf> [TOPIC] Triage Status (JFo)
[18:06] <MootBot> New Topic:  Triage Status (JFo)
[18:06] <JFo> There has been an increase in people interested in working on triaging bugs. There are a number of folks working today on the Bug Day
[18:06] <JFo> that have helped us triage bugs in the past, but have not been active on BugDays. Marjo blogged my Bug Day e-mail and I blogged about it
[18:06] <JFo> on the qa.ubuntu.com blog. I'll do that for each bug day we have going forward and will keep track of the growth in interest as a result.
[18:06] <JFo> ..
[18:07] <bjf> [TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/)
[18:07] <MootBot> New Topic:  Open Discussion or Questions: Raise your hand to be recognized (o/)
[18:07] <bjf> #
[18:07] <bjf> # Note: This will be the last meeting of the Maverick development cycle. The next
[18:07] <bjf> #       meeting will be November 8th.
[18:07] <bjf> #
[18:07] <JFo> yay, Happy Last Meeting of the Cycle!
[18:07] <JFo> :)
[18:07] <apw> yay
[18:07] <cking_> phew
[18:07] <bjf> thanks everyone
[18:07] <bjf> #endmeeting
[18:07] <MootBot> Meeting finished at 12:07.
[18:07] <JFo> thanks bjf
[18:07] <cking_> bjf, thanks
[18:07] <smb> bjf, ta
[18:08] <JFo> 7 minutes of meeting goodness
[18:08] <JFo> we are darn efficient
[18:08] <cking_> dear sir, is this a record?
[18:08] <bjf> cking_, i think so
[18:08] <JFo> it is the fastest one I have been in
[18:08] <cking_> blink and it's over
[18:08] <JFo> heh
[18:08] <bjf> now all the londoners can go to the pub and dinner
[18:08] <JFo> wooo!
[18:09] <cking_> slackers
[18:09] <JFo> wait... :-(
[18:09]  * JFo can only go to lunch
[18:09] <bjf> JFo, just realizes he's not in london
[18:09] <JFo> :-(
[18:09] <manjo> man what just happened  ?
[18:09]  * JFo cries
[18:09] <bjf> manjo, did you blink and it was over?
[18:10] <JFo> heh
[18:10] <manjo> almost
[18:10] <manjo> ok. see you later folks
[18:10]  * manjo returns to his pile of netbooks
[18:53] <xfaf> yo
[18:58] <hggdh> ~ô~
[18:58] <RoAkSoAx> o/
[18:58] <mathiaz> o/
[18:58] <JamesPage> o/
[18:58] <mjeanson> hi
[18:59] <jiboumans> o/
[18:59] <ttx> \o
[18:59] <kirkland> howdy all
[19:00] <kirkland> i think i'm chairing today, right?
[19:00] <ttx> kirkland: if you can, yes
[19:00] <jiboumans> kirkland: 3rd time's a charm ;)
[19:00] <kirkland> wooho
[19:00] <kirkland> o
[19:00] <kirkland> #startmeeting
[19:00] <Daviey> o/
[19:00] <MootBot> Meeting started at 13:00. The chair is kirkland.
[19:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[19:00] <kirkland> [TOPIC] Review ACTION points from previous meeting
[19:00] <MootBot> New Topic:  Review ACTION points from previous meeting
[19:00] <kirkland> hmm, i don't see any outstanding actions at https://wiki.ubuntu.com/ServerTeam/Meeting
[19:01] <kirkland> in which case, if there are none, I suppose we'll just move on
[19:01]  * kirkland checks log
[19:01] <kirkland> ah, here are a couple
[19:01] <kirkland> --> SpamapS to chase drizzle in maverick decide between "broken" and "removed" with slight possibility of "beta"
[19:01] <kirkland> SpamapS: ?
[19:02] <SpamapS> sorry
[19:02] <SpamapS> drizzle is out of maverick
[19:02] <kirkland> SpamapS: carry over to next week?
[19:02] <SpamapS> removed earlier this week
[19:02] <kirkland> SpamapS: alrighty, done?
[19:02] <SpamapS> In discussing the beta period with their developers, its better this way. :)
[19:02] <SpamapS> kirkland: yes done
[19:02] <kirkland> thanks
[19:02] <kirkland> --> jiboumans to send an email to ubuntu-server@ and/or blog post for call for ideas
[19:03] <kirkland> jiboumans: ?
[19:03] <jiboumans> kirkland: not done </shame>
[19:03] <kirkland> jiboumans: carry over to next week?
[19:03] <smoser> o/
[19:03] <jiboumans> kirkland: i'll do so today
[19:03] <kirkland> jiboumans: k
[19:03] <kirkland> [ACTION] jiboumans to send an email to ubuntu-server@ and/or blog post for call for ideas
[19:03] <MootBot> ACTION received:  jiboumans to send an email to ubuntu-server@ and/or blog post for call for ideas
[19:03] <kirkland> --> mathiaz to send out a call for ideas on ubuntu to the puppet community
[19:03] <kirkland> mathiaz: ?
[19:03] <mathiaz> kirkland: carry over
[19:03] <mathiaz> kirkland: I'll do it later today
[19:04] <mathiaz> (just to copy jiboumans )
[19:04] <kirkland> mathiaz: alrighty
[19:04] <kirkland> [ACTION] (carryover) (carryover) mathiaz to send out a call for ideas on ubuntu to the puppet community
[19:04] <MootBot> ACTION received:  (carryover) (carryover) mathiaz to send out a call for ideas on ubuntu to the puppet community
[19:04]  * kirkland worries about a buffer overflow on that one :-)
[19:05] <kirkland> [TOPIC] Maverick development - jiboumans
[19:05] <MootBot> New Topic:  Maverick development - jiboumans
[19:05] <jiboumans> not much to say right now; we're winding down
[19:05] <zul> yay!
[19:05] <kirkland> release status -- ttx
[19:05] <jiboumans> ttx is at the release spring in london while i'm detained in the US
[19:05] <jiboumans> all his :)
[19:06] <ttx> Mostly in good shape, nothing critical in the daily bug triage
[19:06] <ttx> a couple of FTBFS... one in likewise-open I fixed on Monday, the other is axis2c
[19:06] <ttx> We'll probably postpone that one since it's such a PITA to get right
[19:06]  * Daviey screams
[19:07] <ttx> Daviey: do you agree ?
[19:07] <kirkland> ttx: yeah, i think i've looked at that one, if its the one i'm thinking of :-/
[19:07] <ttx> kirkland: yes, THAT one.
[19:07] <Daviey> ttx, yes - doko also inestigating
[19:07] <kirkland> ttx: ugh
[19:07] <Daviey> investigating*
[19:07] <ttx> The other is Bug 653154
[19:07] <ttx> but is about to be debunked as "not-reproduced"
[19:07] <ttx> Daviey: right ?
[19:08] <Daviey> yah
[19:08] <Daviey> will do shortly
[19:08] <ttx> so we don't have any fix queued for release now.
[19:08] <ttx> (as of now)
[19:08] <ttx> next topic :)
[19:08] <Daviey> \o/
[19:08] <kirkland> ttx: thanks
[19:08] <kirkland> [TOPIC] The road to 10.10.10 release (ttx)
[19:08] <MootBot> New Topic:  The road to 10.10.10 release (ttx)
[19:08] <SpamapS> Actualy I think  bug 653154 might have a duplicate
[19:08] <kirkland> ttx: looking forward?
[19:09] <ttx> ISOs should hit tomorrow.
[19:09] <ttx> so it will be ISO testing season again
[19:09]  * hggdh is happy
[19:09] <ttx> and hopefully we'll be set by Friday
[19:09] <smoser> ttx, are there bugs not included yet that are targetted ?
[19:10] <smoser> (probably I should know the link to such things, but shame on me)
[19:10] <ttx> smoser: the only other bug in the list that we might consider is Bug 617496
[19:10] <ttx> the url is https://wiki.ubuntu.com/ServerTeam/MaverickReleaseStatus
[19:10] <ttx> please make sure to raise any bug you stumble upon in daily triage
[19:10] <kirkland> ttx: okay, so every should prime their ISO cache today using TestDrive, and just incrementally sync the diff tomorrow, right?  ;-)
[19:11] <ttx> that would critically affect maverick
[19:11] <SpamapS> ttx: bug 653362 Is I think the duplicate
[19:11] <ttx> kirkland: yes :) unfortunately my laptop is utterly slow, I need to switch to onf of those SSDs
[19:11] <kirkland> ttx: thanks
[19:11] <inkvizitor68sl> hmmm... i hope there i will get answer...) what i have to do to be able to receive new CDs (better - in enough amount to share it).
[19:11] <ttx> so daviey will bring a couple spare laptops so that we do ISO testing in London
[19:12] <kirkland> noted, ttx is looking for an SSD donation
[19:12] <SpamapS> ttx: and bug 653152
[19:12] <ttx> Daviey: looks like it's a bit reproductible after all.
[19:12] <mathiaz> Daviey: are you heading to the release sprint as well?
[19:12] <SpamapS> ttx: They may not have showed up on the radar because I marked it as Medium
[19:12] <ttx> SpamapS: volunteering to clear it out before we rool ISOs tomorrow ?
[19:12] <Daviey> ttx: oh joy
[19:12] <kirkland> ttx: alrighty -- anything else 10.10.10 worthy?
[19:12] <Daviey> mathiaz: some of it.
[19:13] <ttx> we need someone in US TZ to take care of it
[19:13] <ttx> ideally before we spin ISOs :)
[19:13] <SpamapS> ttx: I'm not entirely familiar with dovecot, but I'm happy to attack it if nobody else wants it. :)
[19:13] <Daviey> rocking!
[19:13] <ttx> mathiaz: ^or you :)
[19:13] <SpamapS> Will need somebody to upload.
[19:14] <kirkland> SpamapS: i can sponsor
[19:14] <SpamapS> Don't we have some people in .jp ?
[19:14] <kirkland> SpamapS: ASAP, though
[19:14] <ttx> SpamapS: mathiaz works on JP tz
[19:14] <SpamapS> kirkland: yeah I'll get on it right away
[19:14] <kirkland> alright, let's take any specific bug discussion to #ubuntu-server
[19:14] <Daviey> SpamapS: i had a Chinese the other day, if that helps?
[19:14] <kirkland> and keep focused here
[19:14] <kirkland> ttx: anything more from you on this topic?
[19:14] <ttx> kirkland: no. Questions ?
[19:15] <ttx> smoser: ideally we would prepublish cloud images early
[19:15] <kirkland> ttx: is this going to be the best Ubuntu Server Release ever?
[19:15] <ttx> smoser: so that you don't have to be on call on Sunday :)
[19:15] <smoser> ttx, well, yes, and ideally with the correct labels
[19:15] <smoser> :)
[19:15] <ttx> kirkland: I hope it will be the quietest.
[19:15] <kirkland> ttx: awesome
[19:16] <smoser> i'll get that all taken care of and send cjwatson instructions on what to do. including a phone number.
[19:16] <kirkland> moving along ....
[19:16] <kirkland> [TOPIC] Natty preparation (jib)
[19:16] <MootBot> New Topic:  Natty preparation (jib)
[19:16] <ttx> and that Cloud10/42 will help show that to the worls
[19:16] <ttx> d
[19:16] <jiboumans> Slowly gearing up for Natty. Like last week, https://wiki.ubuntu.com/ServerTeam/NattyIdeaPool is live and we already have quite a few ideas. If you haven't contributed yours yet, please do so this week. On Friday, we'll be taking a snapshot of this and start making a rudimentary UDS planning.
[19:16] <cjwatson> smoser: I will not be working on Sunday, so ...
[19:16] <jiboumans> as always if you'll be at UDS and already have some topics you'll know you'll work on, feel free to file the blueprints already
[19:16] <cjwatson> smoser: contact skaet
[19:16] <smoser> ooh... then we need a RT for skaet to have access to nectarine
[19:17] <jiboumans> after release, the server team will spend some serious time on setting up our UDS plans & sessions
[19:17] <kirkland> [LINK] https://wiki.ubuntu.com/ServerTeam/NattyIdeaPool
[19:17] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/NattyIdeaPool
[19:17] <jiboumans> that's all there's to say right nwo i think -- any questions?
[19:17] <smoser> [ACTION]: smoser get RT open for skaet to have access to nectarine for publishing UEC images
[19:17] <smoser> [ACTION]: smoser to get skaet info on how to publish EC2 images
[19:18] <kirkland> jiboumans: might we devote some time in next week's meeting to such open ideas/brainstorming?
[19:18] <jiboumans> absolutely
[19:18] <zul> heh some people already started
[19:18] <jiboumans> right now it's a braindump area: add whatever comes up
[19:19] <kirkland> cool
[19:19] <ttx> In the weeks following release, please also remember to keep up the triaging effort, in case our first maverick users hit a major issue, we need to be ready to fix it
[19:19] <jiboumans> kirkland: i've also just sent out the call for ideas/blueprints so you can mark that done
[19:19] <kirkland> ttx: agreed
[19:19] <kirkland> jiboumans: noted
[19:20] <kirkland> jiboumans: anything else on this topic?
[19:20] <jiboumans> not from me
[19:20] <kirkland> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[19:20] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[19:20] <hggdh> yeah
[19:21] <hggdh> we sent our proposal for regression-* tags to -devel. If no complains, we will be implementing it soon (after 10.10.10)
[19:21] <kirkland> hggdh: cool, what does that mean?
[19:22] <hggdh> we will be dropping regression-potential
[19:22] <hggdh> and using regression-release even for a development release
[19:22] <kirkland> ah
[19:22] <kirkland> understood
[19:22] <hggdh> -potential does not seem to gain us much (if at all), apart from more work
[19:23] <hggdh> and... I will start on euca testing for release as soon as the ISO is published
[19:23] <kirkland> hggdh: okay, anything else?
[19:23] <kirkland> any questions for QA?
[19:23] <Daviey> \o/
[19:24] <kirkland> [TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:24] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:24] <kirkland> jjohansen is not feeling well today
[19:24] <kirkland> and it appears that jj-afk is away
[19:24] <smoser> so lets move on there.
[19:25] <kirkland> if there are any kernel related issues, please note them now ...
[19:25] <kirkland> and we'll take them up offline ....
[19:25] <kirkland> going once
[19:25] <kirkland> going twice
[19:25] <kirkland> gone.
[19:25] <kirkland> [TOPIC] Weekly Updates & Questions for the Documentation Team (sommer)
[19:25] <MootBot> New Topic:  Weekly Updates & Questions for the Documentation Team (sommer)
[19:26] <kirkland> sommer doesn't appear to be around either ....
[19:26] <kirkland> going once
[19:26] <Daviey> :(
[19:27] <kirkland> going twice
[19:27] <kirkland> gone.
[19:27] <kirkland> [TOPIC] Weekly Updates & Questions for the Ubuntu Community Team (kim0)
[19:27] <MootBot> New Topic:  Weekly Updates & Questions for the Ubuntu Community Team (kim0)
[19:27] <kirkland> kim0 doesn't appear to around ...
[19:27]  * kirkland misses his friends
[19:28]  * ttx hugs hggdh for being around :)
[19:28] <kirkland> anything to mention, Community related?
[19:28]  * hggdh blushes
[19:28] <hggdh> I have been chatting with kim0
[19:28] <kirkland> going once
[19:28] <smoser> hggdh, are you implying that he's around, just hiding from us.  thanks.
[19:28] <hggdh> about community involvement. We intend to get together and discuss this on UDS
[19:29] <kirkland> hggdh: yes, good
[19:29] <hggdh> smoser: actually it was last week :-)
[19:29] <kirkland> anyone planning a release party?
[19:29] <kirkland> (that's community related...)
[19:29] <zul> ill be having turkey that day
[19:29] <kirkland> or planning to attend a release party?
[19:30] <SpamapS> There's a release party in Hollywood that I'll be attending on Monday evening
[19:30] <RoAkSoAx> o/
[19:30] <SpamapS> nobody wants to go on Sunday ;)
[19:30] <kirkland> SpamapS: oh?  cool ... I'll be in SoCal next week, I think
[19:30] <SpamapS> http://www.borderstylo.com/posts/205-company-culture-at-border-stylo
[19:30] <MootBot> LINK received:  http://www.borderstylo.com/posts/205-company-culture-at-border-stylo
[19:30] <SpamapS> At their offices
[19:30] <kirkland> [ACTION] Everyone to celebrate the 10.10.10 release in their own unique ways
[19:30] <MootBot> ACTION received:  Everyone to celebrate the 10.10.10 release in their own unique ways
[19:30] <SpamapS> :)
[19:30] <ttx> I've been discussing server subcommunities at Open World Forum
[19:31] <kirkland> [TOPIC] Open Discussion
[19:31] <MootBot> New Topic:  Open Discussion
[19:31] <kirkland> anything else?
[19:31] <ttx> i.e. groups specializing in the maintenance of subsystems like "directory" or "windows integration"
[19:31] <smoser> i had an item on open discussion agenda.
[19:31] <RoAkSoAx> or cluster :)
[19:31] <ttx> RoAkSoAx: yes ! though this one is alive and kicking already
[19:32] <smoser> SRU 649591 (mountall spins eating cpu when 'nobootwait' option exists in fstab followed by a comma)
[19:32] <smoser> bug
[19:32] <RoAkSoAx> ttx: we still need UEC HA Clustering though
[19:32] <smoser> bug 649591
[19:32] <SpamapS> I'd really like to see cluster stack get some attention. Building a redundant database server or load balancer on ubuntu should be easy.
[19:32] <ttx> I've seen widespread interest in that, so I hope we'll pull that off
[19:32] <RoAkSoAx> SpamapS: that's easy... the hard part will be the itnegration with UEC xD
[19:33] <ttx> (been talking to huats and RevolutionLinux guys)
[19:33] <mathiaz> ttx: with whom have you been discussin the topics at openworld?
[19:33] <ttx> mathiaz: I read your mind and answer your question before it's asked.
[19:33] <RoAkSoAx> ttx: mjeanson from revolutionlinux is interested in the cluster since they work in Ubuntu
[19:34] <smoser> ok.. my bug. I need bug 649591 back to lucid.  I've got a proposed pull, but need sponsoring.  can i get someone to please sponsor for me.
[19:34] <ttx> smoser: yes you can.
[19:35] <ttx> smoser: maybe not me, but you should get someone
[19:35] <smoser> thats why i'm asking.
[19:35]  * ttx needs to pack tonight
[19:35] <smoser> mathiaz, zul, kirkland, one of you, please ?
[19:35] <zul> sponsoring mountall makes me nervous
[19:36] <kirkland> smoser: i don't mind sponsoring
[19:36] <RoAkSoAx> btw... after this UDS the ubuntu-server package set will be up and running right?
[19:36] <smoser> great.  its not my patch, its cjwatson. so you don't even really have to trust me.
[19:36] <kirkland> smoser: poke me in another channel shortly and let's walk through it
[19:36] <kirkland> smoser: hmm, so why didn't cjwatson upload it?
[19:37] <smoser> he uploaded to maverick.
[19:37] <ttx> I'd say, he is a bit busy with maverick release.
[19:37] <smoser> i am just pushing for lucid (and 'now' rather than later)
[19:37] <kirkland> RoAkSoAx: you mean the ubuntu-server package set?
[19:37] <kirkland> smoser: ah, okay
[19:37] <RoAkSoAx> kirkland: yes
[19:37] <kirkland> smoser: yeah, grab me in #ubuntu-server after the meeting
[19:38] <kirkland> RoAkSoAx: i'm not sure who owns that to-do....
[19:38] <kirkland> ttx: do you know?
[19:38] <ttx> kirkland: that would be mathiaz
[19:38] <ttx> it's part of the deffered items in mavercik-server-seed-review
[19:38] <ttx> deferred, even
[19:38] <kirkland> mathiaz: eta on ubuntu-server package set?
[19:38] <mathiaz> after UDS
[19:38] <kirkland> ttx: mathiaz: cool
[19:38] <RoAkSoAx> cool
[19:38] <kirkland> alright, i think that's about it ...
[19:39] <mathiaz> I'll probably schedule a session at UDS to figure out how to review the best
[19:39] <kirkland> [TOPIC] Announce next meeting date and time
[19:39] <MootBot> New Topic:  Announce next meeting date and time
[19:39] <kirkland> Tuesday 2010-10-12 at 1800 UTC - #ubuntu-meeting
[19:39] <kirkland> see you soon!
[19:39] <mathiaz> it's a 350+ package list
[19:39] <kirkland> mathiaz: yeah, review at UDS is a good idea
[19:39] <kirkland> adios, all
[19:40] <kirkland> #endmeeting
[19:40] <MootBot> Meeting finished at 13:40.
[19:40] <Daviey> o/
[19:40] <ttx> \o
[19:40] <RoAkSoAx> o/
[21:20] <cjwatson> kirkland: yeah, that mountall patch should be good for lucid too, just insufficient round tuits
[21:20] <kirkland> cjwatson: ack
[21:20] <kirkland> cjwatson: thanks for following up