/srv/irclogs.ubuntu.com/2010/10/05/#ubuntu-meeting.txt

=== dyfet` is now known as dyfet
=== freeflyi1g is now known as freeflying
=== dyfet` is now known as dyfet
=== Claudinux_ is now known as Claudinux
=== rgreening_ is now known as rgreening
lago/14:02
mpoiriero/14:06
lagNo meeting today then14:07
rsalvetiwell, we should have it, waiting NCommander14:08
GrueMastergive NCommandera few minutes to shake off the cob webs.14:08
davidmG'day14:09
GrueMasterNCommander has been successfully poked.14:10
NCommander#startmeeting14:11
MootBotMeeting started at 08:11. The chair is NCommander.14:11
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]14:11
ogra_acquestion is if he stays awake :)14:11
* NCommander had a time zone adjustment failure14:11
GrueMasterDoes he ever?14:11
ogra_acheh14:11
NCommander[link] https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010100514:12
MootBotLINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010100514:12
NCommanderNo Action items or special items from last week14:12
NCommander[topic] Burndown chart14:12
MootBotNew Topic:  Burndown chart14:12
NCommander[link] http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html14:12
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html14:12
NCommander[link] http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-ubuntu-10.10.html14:13
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-ubuntu-10.10.html14:13
ogra_acOMG !14:13
ogra_acwe're deep red14:14
NCommanderso there's one last action item left open, persia, can you close it? :-)14:14
ogra_acpersia, !!!14:14
ogra_acNCommander, there are three14:14
ogra_ac(see the overall chart)14:14
NCommander[action] persia to close and/or postpone his remaining action items for 10.1014:16
MootBotACTION received:  persia to close and/or postpone his remaining action items for 10.1014:16
NCommanderanything else on the charts?14:16
ogra_acwhat about the buglist ?14:16
NCommander[link] http://qa.ubuntu.com/reports/team-assigned/canonical-mobile-assigned-bug-tasks.html14:16
MootBotLINK received:  http://qa.ubuntu.com/reports/team-assigned/canonical-mobile-assigned-bug-tasks.html14:16
NCommanderogra_ac: that's separate from the burndown charts no?14:16
ogra_ack14:17
* ogra_ac vaguely remembers an action item for NCommander that doesnt seem to have been transferred ;)14:17
ogra_acregarding the bugs :)14:17
* NCommander doesn't :-)14:18
NCommander[action] NCommander to unassign himself from bugs (c/o)14:18
MootBotACTION received:  NCommander to unassign himself from bugs (c/o)14:18
NCommanderanything else on the bug list?14:18
NCommanderI guess not14:19
NCommander[topic] Kernel Status (cooloney, mpoirier, lag)14:19
MootBotNew Topic:  Kernel Status (cooloney, mpoirier, lag)14:19
mpoirierbeen working on b637947 all week - nothing else to report.14:19
mpoirier..14:19
ogra_acNCommander, dont you run so fast !14:19
ogra_ac7me was just typing :P14:19
ogra_acanyway14:19
GrueMasterbug 637947, maybe?14:19
ubottuLaunchpad bug 637947 in linux-ti-omap4 (Ubuntu Maverick) "no sound devices on current ES2.0 boards" [High,Confirmed] https://launchpad.net/bugs/63794714:19
lago/14:20
ogra_acwe're working on it14:20
ogra_actrying to get patches in today14:20
ogra_acsince thats the last chance to make the release14:20
ogra_accan you guys make sure the kernel team is available for us to make uploads etc ?14:21
NCommanderanything 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-boot14:21
lag   * ON GOING : B637947 Latest sound patches are available from TI - configuration problem still exists14:21
lag   * ON GOING : B653002 Currently under investigation - TI suspects a silicone problem14:21
lag   * ON GOING : B637947 Still working on the userspace ALSA or PulseAudio configuration14:21
lag   * FIXED    : B647890 Fixed the building error14:21
lag   * WORKROUND: B633227 Applied patches from Nicolas to set memory 2G:2G - enabled the errata for PL310 lx20 cache controller14:21
lag   * MISC     : "fakeroot debian/rules binary-omap" seems to be broken on Natty - investigation is required14:21
lag   * MISC     : Some members of the Arm team received ES2.1 boards - so far it's as good as ES2.014:22
lag..14:22
NCommanderah, there's lag14:22
lag:D14:22
lagHi ya14:22
ogra_acyeah, we have slow network NCommander :)14:22
ogra_aclots of lag :)14:22
ogra_aclag, Natty ?!?!14:22
ogra_aclag, please stop building omap3 in natty14:23
ogra_acthat either needs to go into a feature branch again or we need to swithc to linaro14:23
lagSpeak to mpoirier14:23
* ogra_ac will add a spec for that14:23
mpoirierogra_ac: that's a company decision...14:23
NCommanderogra_ac: yes well, its not my fault you forgot to pack a high-speed interneet connection from Germany ogra_ac !14:23
ogra_acmpoirier, no14:23
ogra_acmpoirier, we cant work that way, omap3 needs fixes at times where the mainline kernel cant be uploaded anymore ...14:24
ogra_acmpoirier, building omap3 delays the mainline kernel builds a lot14:24
ogra_acboth teams suffer from it being in the core tree14:24
mpoirierwho's idea was it to put it in the core tree ?14:25
ogra_acthats an unbearable situation, we either need to change it back or completely switch to linaro kernels14:25
ogra_acmpoirier, lool's with agreement from the kernel team14:25
mpoirierI suppose it was put there for a reason...14:25
ogra_acwe tried it one release, its not workable14:25
ogra_acyes, "because we can"14:25
ogra_acits a test that failed badly14:26
mpoirierthen let's get the concerned parties together and settle on the issue.14:26
ogra_acwe would have IGEP2 support properly working if we had a feature branch with separate policies14:26
ogra_acmpoirier, thats what i said above14:26
ogra_aci'll create a spec for discussion at UDS14:26
NCommanderogra_ac: mpoirier I think UDS would be the proper venue for this discussion TBH14:26
NCommanderah14:27
ogra_acjust dont waste time on natty branches now14:27
NCommander:-)14:27
NCommanderanyway, can I move on?14:27
ogra_acyep14:27
ogra_acjust again14:27
NCommander[topic] QA Status (GrueMaster)14:28
MootBotNew Topic:  QA Status (GrueMaster)14:28
ogra_acwe need exceptoions and uploads14:28
ogra_ac*today*14:28
GrueMasterRC Testing went well.  No major issues found, except the missing installer icon on dove images, which is now fixed.14:28
ogra_acplease someone be available from the kernel team to do that14:28
GrueMasterNetboot image for omap was missing modules for usb.  No keyboard, no networking.  Colin has worked to fix this for release.14:28
ogra_ac\o/14:29
mpoirierGrueMaster: omap3 or 4 ? when was that discovered ?14:29
ogra_acast week14:29
ogra_ac*last14:29
GrueMasteromap/omap3/beagle.14:29
ogra_acwe dont build netboot for omap414:30
ogra_acand omap3 are just a nice to have goodie14:30
ogra_acleftover from luicd14:30
GrueMasterThis is not a kernel issue.  This was an issue with debian installer.14:30
ogra_acright, that too14:30
GrueMasterThe modules were not included in the netboot image.14:30
ogra_acNCommander, move if there are no other questions14:31
NCommander[topic] ARM Porting/FTBFS status (NCommander, dyfet)14:32
MootBotNew Topic:  ARM Porting/FTBFS status (NCommander, dyfet)14:32
dyfetWe (ncommander and I) discussed plt-scheme yesterday14:32
NCommanderFTBFS looks relatively happy on all architectures, not just ARM excluding openjjfk14:32
ogra_acbelow 100 pkgs !!!14:32
ogra_acthanks to doko !!!14:32
ogra_acwe owe him a lot, he's the only one really working actively on that list atm14:33
NCommander+1 beer to doko14:33
ogra_ac+3 from me :)14:33
NCommander:-)14:34
NCommander[topic] ARM Image Status (ogra, NCommander)14:34
MootBotNew Topic:  ARM Image Status (ogra, NCommander)14:34
ogra_acomap4 runs on panda ES2.1 !!!14:34
* NCommander heard14:34
GrueMasterWOOT!14:34
ogra_acall open RC bugs were fixed apart from sound14:34
NCommanderIts great when hardware is properly designed to be relatively compatible and sane14:34
NCommanderDove is currently looking good, sound issue aside14:35
ogra_acnot sure about omap3 (i didnt test since a while) or dove14:35
ogra_acGrueMaster, how did omap3 look last time you tested ?14:35
NCommanderInstaller icon shows up where it should be, and its relatively fast and responsive14:35
GrueMasterLooked good, other than the missing modules in the netboot image.14:35
NCommandercool14:35
GrueMasterAudio has the same issues across the board, though.14:36
GrueMasteromap, omap4, dove.14:36
ogra_acomap and dove can have SRUs for that14:36
ogra_acomap4 will get fixes today14:36
NCommanderI 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.1014:36
ogra_ac(or workarounds)14:36
ogra_acomap4 too14:36
rsalvetihopefully14:36
ogra_acwe only need the xloader patch14:37
ogra_acthat should be enough, workst case all other fixes can be SRUs14:37
NCommanderogra_ac: check thatwith davidm since thats contray to what I heard yesterday14:37
ogra_acxloader and uboot are the things we cant update14:37
NCommanderotherwise, WOO14:37
ogra_acif they are in shape omap4 is ready for 10.10.1014:37
ogra_acdavidm, ^^^^14:38
ogra_acplease agree14:38
NCommanderogra_ac: why can't you update XLO or u-boot14:38
ogra_acNCommander, because they are not handled by packages in the image14:38
ogra_acwe treat them like BIOS14:38
NCommanderogra_ac: ah. fair enough.We could fix it, but it would be fugly14:38
ogra_aca way we inherit through using flash-kernel from debian14:38
ogra_acNCommander, lets fix it in a non ugly way14:38
ogra_acSPEC !!!14:39
NCommanderogra_ac: right14:39
ogra_acwill need good thinking through14:39
NCommander[action] ogra + davidm to determine armel+omap4 releasability and notify the release team with the result14:39
MootBotACTION received:  ogra + davidm to determine armel+omap4 releasability and notify the release team with the result14:39
ogra_ac++14:39
ogra_acthanks14:39
ogra_aci'll be able to tell tonight14:39
NCommander[topic] Any Other Business14:40
MootBotNew Topic:  Any Other Business14:40
ogra_acreally depends on the kernel team14:40
davidmogra_ac, theree were NO kernel changes for OMAP 4?14:40
ogra_acwe need an uploader for the sound fix14:40
ogra_acdavidm, apart from sound ? no14:40
ogra_acdavidm, es2.1 should work out of the box with the xloader changes14:40
davidmogra_ac, lets have a talk later14:40
ogra_acyep14:40
ogra_aclets wait how today at TI turns out14:40
ogra_acwe can say for sure by end of day14:41
rsalvetirobclark is just testing the instabilities issues we saw yesterday14:41
rsalvetiso soon we should know better if it works or not14:41
rsalvetibut I'd say that we just need x-loader fixes14:41
ogra_ac++14:41
NCommanderanything else left for this meeting?14:42
NCommanderOr can I close it out?14:42
rsalvetinops, hopefully we'll be on-line sooner today14:42
ogra_acactivity reports !!14:42
ogra_acdont foget them :)14:42
rsalvetiI did mine ;-)14:42
ogra_acrsalveti rocks14:42
NCommanderrsalveti: maybe one of you should buy a prepaid broadband solutoin and make a hotspot14:42
ogra_ac(and he's the only one here)14:42
ogra_acNCommander, THATS WHAT WE USE14:42
ogra_acOOPS14:43
rsalvetiyup :-)14:43
ogra_acdamned caps14:43
NCommanderogra_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
NCommanderanyway, about to close the meeting14:43
NCommandergoing once14:43
* ogra_ac slaps NCommander with a holiday inn pancake14:44
NCommandermmmmm, tasty14:44
GrueMasterSo ogra_ac, does thisw mean you will do a status report too?14:44
* ogra_ac slaps GrueMaster with a holiday inn pancake14:44
* GrueMaster has bacon and will slap back.14:44
ogra_acgreasy meeting !14:45
* NCommander notes that ogra_ac and GrueMaster should get a room to save all our visions.14:45
NCommanderanyway14:45
ogra_acNCommander, quick close the meeting14:45
NCommandergoing once14:45
NCommandertwice14:45
NCommanderthree times14:45
NCommander#endmeeting14:45
MootBotMeeting finished at 08:45.14:45
* NCommander resets his alarm to respect the local time14:45
loolmpoirier, ogra_ac: Sorry, I didn't follow; what was my decision wiht the kernel team agreement?14:51
mpoirierlool, at one point or another omap3 became part of mainstream.14:52
mpoiriersince this it the time I got hired, I *think* lucide was a topic branch and was wrapped in mainstream for maverick.14:53
=== chrisccoulson is now known as nosluoccsirhc
kees\o14:54
ogra_aclool, having omap built from the main tree is a pain for everyone14:55
ogra_aclool, so i want either a topic branch for natty again or directly switch to linaro14:56
* ogra_ac takes further discussion to #ubuntu-arm14:56
loolI think this is a large topic14:56
=== nosluoccsirhc is now known as chrisccoulson
ogra_acyep14:57
mdzpitti: hi15:02
cjwatsonhello15:02
cjwatsongosh, am I chair15:03
cjwatsonkees: around?15:03
cjwatsonah yes15:03
mdzah, so you are15:03
mdzI thought it was pitti, but that's the meeting I missed15:03
cjwatsonno obvious sign of Keybuk; pinged sabdfl15:03
pittihello15:04
pitticjwatson: sabdfl is on a conference15:04
pittihe asked to be skipped on the chair rotation15:04
cjwatsonaha15:04
pittiso he might lag or not be present at all15:04
cjwatson#startmeeting15:04
MootBotMeeting started at 09:04. The chair is cjwatson.15:04
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:04
cjwatson[TOPIC] Action review15:04
MootBotNew Topic:  Action review15:04
cjwatsonMartin Pitt to ask Martin Pool about bzr self test instructions on installed system15:04
cjwatsonpitti: ?15:05
keescjwatson: yup15:05
keescjwatson: he asked, but I didn't see a reply15:05
pitticjwatson: done15:06
pittihe replied15:06
cjwatsonKees to add bzr self test to qa-regression-testing project15:06
pittiand even better, they seemed to have made a lot of fixes15:06
pittibzr 2.0.3 should have a fully working test suite15:06
keescjwatson: did that15:06
pittior .2 even15:06
cjwatsonMartin to add bzr microrelease exception to StableReleasePolicy15:06
pittidone15:07
cjwatsonexcellent15:07
cjwatson[TOPIC] Decide/document ubuntu-archive interaction with ARB packages15:07
MootBotNew Topic:  Decide/document ubuntu-archive interaction with ARB packages15:07
cjwatson[LINK] https://lists.ubuntu.com/archives/technical-board/2010-September/000516.html15:07
MootBotLINK received:  https://lists.ubuntu.com/archives/technical-board/2010-September/000516.html15:07
cjwatsonI don't remember whether we discussed this, or if so what the outcome was15:08
cjwatsonnormally, one function of the archive admins is to at least ensure legality of distribution15:08
mdzit's new to me, though I missed the previous meeting15:08
cjwatsonwhich is more or less the bare minimum15:08
cjwatsonthis 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 meeting15:09
mdzso the question is whether archive admins will have responsibility for reviewing ARB packages as well as other kinds of packages?15:10
cjwatsonmy memory is that extras.ubuntu.com is actually a mirror of a PPA owned by the ARB15:10
mdzis there anyone else in a position to do it?15:10
cjwatsonwhich would mean that ubuntu-archive wouldn't actually naturally have access to it, only the ARB15:11
mdzthe ARB themselves?15:11
cjwatson(ScottK may or may not be aware of this)15:11
cjwatsonhttps://wiki.ubuntu.com/PostReleaseApps/Process is not terribly clear on the matter15:11
cjwatsonif it's an ARB-owned PPA, then I think the answer is simple, but the process documentation needs to be expanded to mention that15:12
mdzsounds straightforward enough15:12
cjwatsondoes anyone know the answer to that authoritatively?15:12
mdzpresumably there's an existing archive admin checklist which could be reused?15:12
cjwatsonI knew a couple of months ago ...15:12
mdzI don't know about the PPA implementation15:12
cjwatsonhttps://wiki.ubuntu.com/ArchiveAdministration#NEW%20handling has various things we do15:13
mdzrickspencer3 is here; I could ask him if he's likely to know15:13
cjwatsonI think he would15:13
cjwatsonplease do15:13
mdzok, I'll run over15:13
mdzcjwatson: he doesn't quite know15:14
mdzhe redirected to mvo15:14
mdzmvo: around?15:15
cjwatson[ACTION] cjwatson to ensure that documentation on nature of extras.ubuntu.com archive makes it into process docs15:16
MootBotACTION received:  cjwatson to ensure that documentation on nature of extras.ubuntu.com archive makes it into process docs15:16
mdzcjwatson: maybe we need to chase this offline15:16
cjwatsonI think it's clear that that's needed no matter what15:16
cjwatsonOK, I'll take an action and chase it up tomorrow probably15:16
cjwatson[ACTION] cjwatson to chase up archive processing details for extras.ubuntu.com15:16
MootBotACTION received:  cjwatson to chase up archive processing details for extras.ubuntu.com15:16
cjwatson[TOPIC] Decide on permission changes documented in LP: 174375 - Matt Zimmerman15:16
MootBotNew Topic:  Decide on permission changes documented in LP: 174375 - Matt Zimmerman15:16
cjwatsonI already acked that bug both in person and in LP15:17
mdzbdmurray sent email to the mailing list and didn't get enough of a response to feel comfortable moving forward15:17
mdzI'm +1 on it15:17
mdzmaybe we can just do a quick vote assuming folks have read it?15:17
cjwatsonthere 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 there15:17
cjwatsonanyone feel they need a few minutes to read over bug 174375?15:18
ubottuLaunchpad bug 174375 in Launchpad Registry "Distribution drivers permissions may need redesign" [Low,Triaged] https://launchpad.net/bugs/17437515:18
keesI've read it a few times now :)15:18
mdzhttps://lists.ubuntu.com/archives/technical-board/2010-August/000426.html15:18
* pitti reads to refresh memory15:18
mdzis brian's proposal15:19
mdzwhich is also in the bug at https://bugs.edge.launchpad.net/launchpad-registry/+bug/174375/comments/415:19
ubottuLaunchpad bug 174375 in Launchpad Registry "Distribution drivers permissions may need redesign" [Low,Triaged]15:19
mvomdz: yes, I'm around15:20
mdzmvo: the question earlier was whether extras.ubuntu.com is a mirror of a PPA owned by the ARB15:21
mvomdz: yes, that is the case15:21
mdzmvo: thanks15:21
mvoyw15:21
cjwatsonmvo: thank you, looks like that answers the question; I'll follow up with ScottK et al15:22
mvothanks cjwatson15:22
mdzpitti: refreshed?15:22
pittimdz: yes15:22
cjwatson[VOTE] Approve Brian's proposal for redesign of distribution driver permissions15:23
MootBotPlease vote on:  Approve Brian's proposal for redesign of distribution driver permissions.15:23
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot15:23
MootBotE.g. /msg MootBot +1 #ubuntu-meeting15:23
cjwatson+115:23
MootBot+1 received from cjwatson. 1 for, 0 against. 0 have abstained. Count is now 115:23
kees+115:23
MootBot+1 received from kees. 2 for, 0 against. 0 have abstained. Count is now 215:23
pittiI think bug targetting needs to be more open than just release-managers; the rest looks fairly okay15:23
pittiif we understand "ubuntu drivers" as "team leads, tech leads, etc"15:23
mdz+115:24
MootBot+1 received from mdz. 3 for, 0 against. 0 have abstained. Count is now 315:24
pittiunder that assumption,15:24
pitti+115:24
MootBot+1 received from pitti. 4 for, 0 against. 0 have abstained. Count is now 415:24
cjwatsonpitti: I'm not too concerned about bug targeting, as long as we can control it independently from spec handling15:24
cjwatson(FAOD that doesn't affect my vote either way)15:24
pitticjwatson: *nod*15:24
mdzyeah, the real change is making it a separate slot15:24
cjwatson[ENDVOTE]15:24
MootBotFinal result is 4 for, 0 against. 0 abstained. Total: 415:24
mdzI'll go back to Brian and let him know we acked it, thanks15:24
pittiseparating blueprints and bugs is the main goal here indeed15:24
cjwatsontargeting: Brian says "should be fixed as long as it doesn't exclude uploaders" which is OK by me15:24
pittiright15:25
cjwatson[TOPIC] Scan the mailing list archive for anything we missed15:25
MootBotNew Topic:  Scan the mailing list archive for anything we missed15:25
cjwatsonthe 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:25
keescjwatson: I think it's understood; we're just waiting for a final proposal from fta15:26
pittiI think there is a consensus there15:26
keesright15:26
cjwatsonSeptember'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 period15:26
pittibasically, throw out the upstream updates pretty much blindly15:26
pittibut it's not mature enough yet for main15:26
cjwatsonabsolutely agreed15:27
keesI think the waiting period needs to be dropped, but at the same time, debian/ changes should be limited15:27
pittikees: well, perhaps dropped -> shortened15:27
* kees nods15:27
pittiit should at least build and get a coarse upgrade/install test15:27
keesright, but I call that "testing" :)15:28
pittiwe can drop the 7 days maturing period, but please let's not drop -proposed and at least quick verification15:28
keesyup15:28
mdz+215:28
jdstrandis -proposed required?15:29
jdstrandas kees said, we require testing15:30
pittiuploading the stuff straight to -updates is way too risky IMHO15:30
jdstrandit won't ever blindly be uploaded15:30
pittiif it buids on amd64 and fails on i386, we create uninstallability, etc.15:30
jdstrandeg, I'd run it through qrt15:30
jdstrandpitti: sure, we test both i386 and amd64. it is part of the testing procedures15:30
jdstrand(that is part of the security team's checklist)15:31
pittisounds good15:31
jdstrandI guess what I am getting at is this15:31
jdstrandI noticed yesterday that we are showing chromium as a supported browser in the maverick livecd slideshow15:32
pitti!?15:32
jdstrandyes, I was surprised too...15:32
pittiwell, we'll keep it up to date either way15:32
jdstrandbut the security team will just need to treat it like flashplugin-nonfree-- it is universe, but we know a ton of people use it15:33
cjwatsonthat seems realistic, yes15:33
jdstrandso we test it ourselves in a similar manner15:33
jdstrandie, with all our checklists, etc, etc15:33
pittii. e. it's not an OMGincident if it suddenly breaks with a particular web page15:33
jdstrandcorrect15:34
jdstrandand no USN15:34
pitti(chromiums seems to do that a lot, at least on our arm systems)15:34
jdstrandlike I mentioned, we have a qrt script which should catch any really huge issues15:34
jdstrand(js, ssl, redirects, images, flash, java, etc, etc...)15:35
pittijdstrand: wow, so you call it on different web page types and check that it doesn't "Aw, snap!"? nice15:35
jdstrandI'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 is15:35
jdstrandpitti: yes15:36
jdstrandit is semi-automatic15:36
pittiit seems to have worked pretty well with the last handful of updates15:36
pittiat least from my POV15:36
jdstrandie, it requires you to be looking at the test as it runs and close the browser, but it leads you through repeatable tests15:36
jdstrandyes15:36
cjwatsonok, anything further on this?15:37
pittiso what's remaining on this?15:37
pittistanding SRU exception?15:37
pittiit seems to be pretty much without alternative15:38
keesyeah; should we vote on it?15:38
cjwatsonI haven't heard any disagreement15:38
jdstrandyes. 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 him15:38
pittiwithout requiring the 7 days testing period, too15:38
cjwatsonbut why don't we vote on fta's proposal15:38
cjwatsonwhen it arrives15:38
pitti*nod*15:38
cjwatsonlet's move on for now, then15:39
jdstrand(if he hasn't done so already,-- I am not up to date)15:39
cjwatsonI haven't seen it15:39
cjwatson[TOPIC] Check up on community bugs (standing item)15:39
MootBotNew Topic:  Check up on community bugs (standing item)15:39
cjwatsonnothing except what we just discussed15:39
cjwatson[TOPIC] Select a chair for the next meeting15:39
MootBotNew Topic:  Select a chair for the next meeting15:39
cjwatsonI make it kees15:39
keessounds good15:39
cjwatson[TOPIC] AOB15:39
MootBotNew Topic:  AOB15:39
cjwatsongoing once15:40
cjwatsongoing twice15:40
mdznothing from me15:40
cjwatsonsold to the gentleman with the purple IRC client15:40
cjwatson#endmeeting15:41
MootBotMeeting finished at 09:41.15:41
mdzthanks, cjwatson15:41
pittithanks everyone15:41
keesthanks!15:41
* pitti hops to the next meeting15:41
=== jjohansen is now known as jj-afk
JFoo/17:59
apwo/18:00
cking_\o18:00
* ogasawara waves18:00
mpoiriero/18:00
bjf#startmeeting18:00
MootBotMeeting started at 12:00. The chair is bjf.18:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]18:00
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting18:00
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick18:00
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting18:00
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick18:00
bjf#18:00
bjf# NOTE: '..' indicates that you are finished with your input.18:00
bjf#18:00
bjf[TOPIC] ARM Status (lag)18:01
MootBotNew 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-boot18:01
lag   * ON GOING : B637947 Latest sound patches are available from TI - configuration problem still exists18:01
lag   * ON GOING : B653002 Currently under investigation - TI suspects a silicone problem18:01
lag   * ON GOING : B637947 Still working on the userspace ALSA or PulseAudio configuration18:01
lag   * FIXED    : B647890 Fixed the building error18:01
lag   * WORKROUND: B633227 Applied patches from Nicolas to set memory 2G:2G - enabled the errata for PL310 lx20 cache controller18:01
lag   * MISC     : "fakeroot debian/rules binary-omap" seems to be broken on Natty - investigation is required18:01
lag   * MISC     : Some members of the Arm team received ES2.1 boards - so far it's as good as ES2.018:01
lag..18:01
bjf[TOPIC] Release Metrics: (JFo)18:02
MootBotNew Topic:  Release Metrics: (JFo)18:02
JFoRelease Meeting Bugs (4 bugs, 9 Blueprints)18:02
JFo==== Release Milestoned Bugs (19 across all packages (down 7)) ====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==== Release Targeted Bugs (134 across all packages (down 10)) ====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==== Milestoned Features ====18:02
JFo * 14 blueprints (Including HWE Blueprints)18:02
JFo==== Bugs with Patches Attached:124 (up 3) ====18:02
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
MootBotNew Topic:  Status: Maverick (ogasawara)18:03
ogasawaraAs 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:03
ubottuLaunchpad bug 647071 in linux (Ubuntu Maverick) "0-day Maverick Kernel Upload" [High,Confirmed] https://launchpad.net/bugs/64707118:03
bjf[TOPIC] Security & bugfix kernels - Lucid/Karmic/Jaunty/Hardy/Others (smb)18:04
MootBotNew 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
MootBotNew Topic:  Incoming Bugs: Regressions (JFo)18:04
JFo721 Maverick Bugs (up 92)18:04
JFo1014 Lucid Bugs (up 36)18:05
JFoCurrent regression stats (broken down by release):18:05
JFo==== regression-potential ====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==== regression-update ====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==== regression-release ====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==== regression-proposed ====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
MootBotNew Topic:  Incoming Bugs: Bug day report (JFo)18:05
JFoThe 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
JFoThe focus will be on bugs with patches. We will be working to identify those bugs that have actual, relevant patches.18:05
JFoMore details to follow on the wiki.18:05
JFoWe will continue to have the Team Bug Day to address the Top 50 list as half days on Friday and Monday.18:05
JFoReviewers, 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
JFoPlease 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
JFoThere are several subsystems owned by all that need to be reviewed for inclusion in our top 50 list.18:05
JFo..18:06
bjf[TOPIC] Triage Status (JFo)18:06
MootBotNew Topic:  Triage Status (JFo)18:06
JFoThere has been an increase in people interested in working on triaging bugs. There are a number of folks working today on the Bug Day18:06
JFothat 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 it18:06
JFoon 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:06
bjf[TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/)18:07
MootBotNew 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 next18:07
bjf#       meeting will be November 8th.18:07
bjf#18:07
JFoyay, Happy Last Meeting of the Cycle!18:07
JFo:)18:07
apwyay18:07
cking_phew18:07
bjfthanks everyone18:07
bjf#endmeeting18:07
MootBotMeeting finished at 12:07.18:07
JFothanks bjf18:07
cking_bjf, thanks18:07
smbbjf, ta18:07
JFo7 minutes of meeting goodness18:08
JFowe are darn efficient18:08
cking_dear sir, is this a record?18:08
bjfcking_, i think so18:08
JFoit is the fastest one I have been in18:08
cking_blink and it's over18:08
JFoheh18:08
bjfnow all the londoners can go to the pub and dinner18:08
JFowooo!18:08
cking_slackers18:09
JFowait... :-(18:09
* JFo can only go to lunch18:09
bjfJFo, just realizes he's not in london18:09
JFo:-(18:09
manjoman what just happened  ?18:09
* JFo cries18:09
bjfmanjo, did you blink and it was over?18:09
JFoheh18:10
manjoalmost18:10
manjook. see you later folks18:10
* manjo returns to his pile of netbooks18:10
xfafyo18:53
=== xfaf is now known as zul
hggdh~ô~18:58
RoAkSoAxo/18:58
mathiazo/18:58
JamesPageo/18:58
mjeansonhi18:58
jiboumanso/18:59
ttx\o18:59
kirklandhowdy all18:59
kirklandi think i'm chairing today, right?19:00
ttxkirkland: if you can, yes19:00
jiboumanskirkland: 3rd time's a charm ;)19:00
kirklandwooho19:00
kirklando19:00
kirkland#startmeeting19:00
Davieyo/19:00
MootBotMeeting started at 13:00. The chair is kirkland.19:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]19:00
kirkland[TOPIC] Review ACTION points from previous meeting19:00
MootBotNew Topic:  Review ACTION points from previous meeting19:00
kirklandhmm, i don't see any outstanding actions at https://wiki.ubuntu.com/ServerTeam/Meeting19:00
kirklandin which case, if there are none, I suppose we'll just move on19:01
* kirkland checks log19:01
kirklandah, here are a couple19:01
kirkland--> SpamapS to chase drizzle in maverick decide between "broken" and "removed" with slight possibility of "beta"19:01
kirklandSpamapS: ?19:01
SpamapSsorry19:02
SpamapSdrizzle is out of maverick19:02
kirklandSpamapS: carry over to next week?19:02
SpamapSremoved earlier this week19:02
kirklandSpamapS: alrighty, done?19:02
SpamapSIn discussing the beta period with their developers, its better this way. :)19:02
SpamapSkirkland: yes done19:02
kirklandthanks19:02
kirkland--> jiboumans to send an email to ubuntu-server@ and/or blog post for call for ideas19:02
kirklandjiboumans: ?19:03
jiboumanskirkland: not done </shame>19:03
kirklandjiboumans: carry over to next week?19:03
smosero/19:03
jiboumanskirkland: i'll do so today19:03
kirklandjiboumans: k19:03
kirkland[ACTION] jiboumans to send an email to ubuntu-server@ and/or blog post for call for ideas19:03
MootBotACTION received:  jiboumans to send an email to ubuntu-server@ and/or blog post for call for ideas19:03
kirkland--> mathiaz to send out a call for ideas on ubuntu to the puppet community19:03
kirklandmathiaz: ?19:03
mathiazkirkland: carry over19:03
mathiazkirkland: I'll do it later today19:03
mathiaz(just to copy jiboumans )19:04
kirklandmathiaz: alrighty19:04
kirkland[ACTION] (carryover) (carryover) mathiaz to send out a call for ideas on ubuntu to the puppet community19:04
MootBotACTION received:  (carryover) (carryover) mathiaz to send out a call for ideas on ubuntu to the puppet community19:04
* kirkland worries about a buffer overflow on that one :-)19:04
kirkland[TOPIC] Maverick development - jiboumans19:05
MootBotNew Topic:  Maverick development - jiboumans19:05
jiboumansnot much to say right now; we're winding down19:05
zulyay!19:05
kirklandrelease status -- ttx19:05
jiboumansttx is at the release spring in london while i'm detained in the US19:05
jiboumansall his :)19:05
ttxMostly in good shape, nothing critical in the daily bug triage19:06
ttxa couple of FTBFS... one in likewise-open I fixed on Monday, the other is axis2c19:06
ttxWe'll probably postpone that one since it's such a PITA to get right19:06
* Daviey screams19:06
ttxDaviey: do you agree ?19:07
kirklandttx: yeah, i think i've looked at that one, if its the one i'm thinking of :-/19:07
ttxkirkland: yes, THAT one.19:07
Davieyttx, yes - doko also inestigating19:07
kirklandttx: ugh19:07
Davieyinvestigating*19:07
ttxThe other is Bug 65315419:07
ubottuLaunchpad bug 653154 in dovecot (Ubuntu Maverick) "package mail-stack-delivery (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1" [High,Incomplete] https://launchpad.net/bugs/65315419:07
ttxbut is about to be debunked as "not-reproduced"19:07
ttxDaviey: right ?19:07
Davieyyah19:08
Davieywill do shortly19:08
ttxso we don't have any fix queued for release now.19:08
ttx(as of now)19:08
ttxnext topic :)19:08
Daviey\o/19:08
kirklandttx: thanks19:08
kirkland[TOPIC] The road to 10.10.10 release (ttx)19:08
MootBotNew Topic:  The road to 10.10.10 release (ttx)19:08
SpamapSActualy I think  bug 653154 might have a duplicate19:08
ubottuLaunchpad bug 653154 in dovecot (Ubuntu Maverick) "package mail-stack-delivery (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1" [High,Incomplete] https://launchpad.net/bugs/65315419:08
kirklandttx: looking forward?19:08
ttxISOs should hit tomorrow.19:09
ttxso it will be ISO testing season again19:09
* hggdh is happy19:09
ttxand hopefully we'll be set by Friday19:09
smoserttx, are there bugs not included yet that are targetted ?19:09
smoser(probably I should know the link to such things, but shame on me)19:10
ttxsmoser: the only other bug in the list that we might consider is Bug 61749619:10
ubottuLaunchpad bug 617496 in eucalyptus (Ubuntu Maverick) "'stop eucalyptus' should also stop all -publication services" [Low,Confirmed] https://launchpad.net/bugs/61749619:10
ttxthe url is https://wiki.ubuntu.com/ServerTeam/MaverickReleaseStatus19:10
ttxplease make sure to raise any bug you stumble upon in daily triage19:10
kirklandttx: okay, so every should prime their ISO cache today using TestDrive, and just incrementally sync the diff tomorrow, right?  ;-)19:10
ttxthat would critically affect maverick19:11
SpamapSttx: bug 653362 Is I think the duplicate19:11
ttxkirkland: yes :) unfortunately my laptop is utterly slow, I need to switch to onf of those SSDs19:11
kirklandttx: thanks19:11
ubottuLaunchpad bug 653362 in dovecot (Ubuntu) "package mail-stack-delivery 1:1.2.12-1ubuntu7 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1" [Medium,Confirmed] https://launchpad.net/bugs/65336219:11
inkvizitor68slhmmm... 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
ttxso daviey will bring a couple spare laptops so that we do ISO testing in London19:11
kirklandnoted, ttx is looking for an SSD donation19:12
SpamapSttx: and bug 65315219:12
ubottuLaunchpad bug 653152 in dovecot (Ubuntu) "package mail-stack-delivery 1:1.2.12-1ubuntu7 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 (dup-of: 653362)" [Undecided,New] https://launchpad.net/bugs/65315219:12
ttxDaviey: looks like it's a bit reproductible after all.19:12
mathiazDaviey: are you heading to the release sprint as well?19:12
SpamapSttx: They may not have showed up on the radar because I marked it as Medium19:12
ttxSpamapS: volunteering to clear it out before we rool ISOs tomorrow ?19:12
Davieyttx: oh joy19:12
kirklandttx: alrighty -- anything else 10.10.10 worthy?19:12
Davieymathiaz: some of it.19:12
ttxwe need someone in US TZ to take care of it19:13
ttxideally before we spin ISOs :)19:13
SpamapSttx: I'm not entirely familiar with dovecot, but I'm happy to attack it if nobody else wants it. :)19:13
Davieyrocking!19:13
ttxmathiaz: ^or you :)19:13
SpamapSWill need somebody to upload.19:13
kirklandSpamapS: i can sponsor19:14
SpamapSDon't we have some people in .jp ?19:14
kirklandSpamapS: ASAP, though19:14
ttxSpamapS: mathiaz works on JP tz19:14
SpamapSkirkland: yeah I'll get on it right away19:14
kirklandalright, let's take any specific bug discussion to #ubuntu-server19:14
DavieySpamapS: i had a Chinese the other day, if that helps?19:14
kirklandand keep focused here19:14
kirklandttx: anything more from you on this topic?19:14
ttxkirkland: no. Questions ?19:14
ttxsmoser: ideally we would prepublish cloud images early19:15
kirklandttx: is this going to be the best Ubuntu Server Release ever?19:15
ttxsmoser: so that you don't have to be on call on Sunday :)19:15
smoserttx, well, yes, and ideally with the correct labels19:15
smoser:)19:15
ttxkirkland: I hope it will be the quietest.19:15
kirklandttx: awesome19:15
smoseri'll get that all taken care of and send cjwatson instructions on what to do. including a phone number.19:16
kirklandmoving along ....19:16
kirkland[TOPIC] Natty preparation (jib)19:16
MootBotNew Topic:  Natty preparation (jib)19:16
ttxand that Cloud10/42 will help show that to the worls19:16
ttxd19:16
jiboumansSlowly 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
cjwatsonsmoser: I will not be working on Sunday, so ...19:16
jiboumansas 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 already19:16
cjwatsonsmoser: contact skaet19:16
smoserooh... then we need a RT for skaet to have access to nectarine19:16
jiboumansafter release, the server team will spend some serious time on setting up our UDS plans & sessions19:17
kirkland[LINK] https://wiki.ubuntu.com/ServerTeam/NattyIdeaPool19:17
MootBotLINK received:  https://wiki.ubuntu.com/ServerTeam/NattyIdeaPool19:17
jiboumansthat'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 images19:17
smoser[ACTION]: smoser to get skaet info on how to publish EC2 images19:17
kirklandjiboumans: might we devote some time in next week's meeting to such open ideas/brainstorming?19:18
jiboumansabsolutely19:18
zulheh some people already started19:18
jiboumansright now it's a braindump area: add whatever comes up19:18
kirklandcool19:19
ttxIn 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 it19:19
jiboumanskirkland: i've also just sent out the call for ideas/blueprints so you can mark that done19:19
kirklandttx: agreed19:19
kirklandjiboumans: noted19:19
kirklandjiboumans: anything else on this topic?19:20
jiboumansnot from me19:20
kirkland[TOPIC] Weekly Updates & Questions for the QA Team (hggdh)19:20
MootBotNew Topic:  Weekly Updates & Questions for the QA Team (hggdh)19:20
hggdhyeah19:20
hggdhwe sent our proposal for regression-* tags to -devel. If no complains, we will be implementing it soon (after 10.10.10)19:21
kirklandhggdh: cool, what does that mean?19:21
hggdhwe will be dropping regression-potential19:22
hggdhand using regression-release even for a development release19:22
kirklandah19:22
kirklandunderstood19:22
hggdh-potential does not seem to gain us much (if at all), apart from more work19:22
hggdhand... I will start on euca testing for release as soon as the ISO is published19:23
kirklandhggdh: okay, anything else?19:23
kirklandany questions for QA?19:23
Daviey\o/19:23
kirkland[TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)19:24
MootBotNew Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)19:24
kirklandjjohansen is not feeling well today19:24
kirklandand it appears that jj-afk is away19:24
smoserso lets move on there.19:24
kirklandif there are any kernel related issues, please note them now ...19:25
kirklandand we'll take them up offline ....19:25
kirklandgoing once19:25
kirklandgoing twice19:25
kirklandgone.19:25
kirkland[TOPIC] Weekly Updates & Questions for the Documentation Team (sommer)19:25
MootBotNew Topic:  Weekly Updates & Questions for the Documentation Team (sommer)19:25
kirklandsommer doesn't appear to be around either ....19:26
kirklandgoing once19:26
Daviey:(19:26
kirklandgoing twice19:27
kirklandgone.19:27
kirkland[TOPIC] Weekly Updates & Questions for the Ubuntu Community Team (kim0)19:27
MootBotNew Topic:  Weekly Updates & Questions for the Ubuntu Community Team (kim0)19:27
kirklandkim0 doesn't appear to around ...19:27
* kirkland misses his friends19:27
* ttx hugs hggdh for being around :)19:28
kirklandanything to mention, Community related?19:28
* hggdh blushes19:28
hggdhI have been chatting with kim019:28
kirklandgoing once19:28
smoserhggdh, are you implying that he's around, just hiding from us.  thanks.19:28
hggdhabout community involvement. We intend to get together and discuss this on UDS19:28
kirklandhggdh: yes, good19:29
hggdhsmoser: actually it was last week :-)19:29
kirklandanyone planning a release party?19:29
kirkland(that's community related...)19:29
zulill be having turkey that day19:29
kirklandor planning to attend a release party?19:29
SpamapSThere's a release party in Hollywood that I'll be attending on Monday evening19:30
RoAkSoAxo/19:30
SpamapSnobody wants to go on Sunday ;)19:30
kirklandSpamapS: oh?  cool ... I'll be in SoCal next week, I think19:30
SpamapShttp://www.borderstylo.com/posts/205-company-culture-at-border-stylo19:30
MootBotLINK received:  http://www.borderstylo.com/posts/205-company-culture-at-border-stylo19:30
SpamapSAt their offices19:30
kirkland[ACTION] Everyone to celebrate the 10.10.10 release in their own unique ways19:30
MootBotACTION received:  Everyone to celebrate the 10.10.10 release in their own unique ways19:30
SpamapS:)19:30
ttxI've been discussing server subcommunities at Open World Forum19:30
kirkland[TOPIC] Open Discussion19:31
MootBotNew Topic:  Open Discussion19:31
kirklandanything else?19:31
ttxi.e. groups specializing in the maintenance of subsystems like "directory" or "windows integration"19:31
smoseri had an item on open discussion agenda.19:31
RoAkSoAxor cluster :)19:31
ttxRoAkSoAx: yes ! though this one is alive and kicking already19:31
smoserSRU 649591 (mountall spins eating cpu when 'nobootwait' option exists in fstab followed by a comma)19:32
smoserbug19:32
RoAkSoAxttx: we still need UEC HA Clustering though19:32
smoserbug 64959119:32
ubottuLaunchpad bug 649591 in mountall (Ubuntu Lucid) "mountall spins eating cpu when 'nobootwait' option exists in fstab followed by a comma" [High,Triaged] https://launchpad.net/bugs/64959119:32
SpamapSI'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
ttxI've seen widespread interest in that, so I hope we'll pull that off19:32
RoAkSoAxSpamapS: that's easy... the hard part will be the itnegration with UEC xD19:32
ttx(been talking to huats and RevolutionLinux guys)19:33
mathiazttx: with whom have you been discussin the topics at openworld?19:33
ttxmathiaz: I read your mind and answer your question before it's asked.19:33
RoAkSoAxttx: mjeanson from revolutionlinux is interested in the cluster since they work in Ubuntu19:33
smoserok.. 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
ubottuLaunchpad bug 649591 in mountall (Ubuntu Lucid) "mountall spins eating cpu when 'nobootwait' option exists in fstab followed by a comma" [High,Triaged] https://launchpad.net/bugs/64959119:34
ttxsmoser: yes you can.19:34
ttxsmoser: maybe not me, but you should get someone19:35
smoserthats why i'm asking.19:35
* ttx needs to pack tonight19:35
smosermathiaz, zul, kirkland, one of you, please ?19:35
zulsponsoring mountall makes me nervous19:35
kirklandsmoser: i don't mind sponsoring19:36
RoAkSoAxbtw... after this UDS the ubuntu-server package set will be up and running right?19:36
smosergreat.  its not my patch, its cjwatson. so you don't even really have to trust me.19:36
kirklandsmoser: poke me in another channel shortly and let's walk through it19:36
kirklandsmoser: hmm, so why didn't cjwatson upload it?19:36
smoserhe uploaded to maverick.19:37
ttxI'd say, he is a bit busy with maverick release.19:37
smoseri am just pushing for lucid (and 'now' rather than later)19:37
kirklandRoAkSoAx: you mean the ubuntu-server package set?19:37
kirklandsmoser: ah, okay19:37
RoAkSoAxkirkland: yes19:37
kirklandsmoser: yeah, grab me in #ubuntu-server after the meeting19:37
kirklandRoAkSoAx: i'm not sure who owns that to-do....19:38
kirklandttx: do you know?19:38
ttxkirkland: that would be mathiaz19:38
ttxit's part of the deffered items in mavercik-server-seed-review19:38
ttxdeferred, even19:38
kirklandmathiaz: eta on ubuntu-server package set?19:38
mathiazafter UDS19:38
kirklandttx: mathiaz: cool19:38
RoAkSoAxcool19:38
kirklandalright, i think that's about it ...19:38
mathiazI'll probably schedule a session at UDS to figure out how to review the best19:39
kirkland[TOPIC] Announce next meeting date and time19:39
MootBotNew Topic:  Announce next meeting date and time19:39
kirklandTuesday 2010-10-12 at 1800 UTC - #ubuntu-meeting19:39
kirklandsee you soon!19:39
mathiazit's a 350+ package list19:39
kirklandmathiaz: yeah, review at UDS is a good idea19:39
kirklandadios, all19:39
kirkland#endmeeting19:40
MootBotMeeting finished at 13:40.19:40
Davieyo/19:40
ttx\o19:40
RoAkSoAxo/19:40
cjwatsonkirkland: yeah, that mountall patch should be good for lucid too, just insufficient round tuits21:20
kirklandcjwatson: ack21:20
kirklandcjwatson: thanks for following up21:20
=== ian_brasil___ is now known as ian_brasil

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!