=== doko_ is now known as doko === dholbach_ is now known as dholbach === greyback is now known as greyback|bia === greyback|bia is now known as greyback === smb` is now known as smb === bladernr_afk is now known as bladernr_ [14:30] hi everybody [14:30] #startmeeting [14:30] Meeting started Tue Mar 27 14:30:39 2012 UTC. The chair is mmrazik. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [14:30] Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired [14:31] hi [14:31] We are here to have a public meeting on QA stuff we do in Product Strategy [14:31] today we would like to share some details on what we do with utouch in terms of quality [14:31] [TOPIC] unit and integration testing for the utouch-stack === meetingology changed the topic of #ubuntu-meeting to: unit and integration testing for the utouch-stack [14:31] tvoss: its yours :) [14:32] mmrazik, thanks :) [14:32] Hi all, my name is Thomas and I'm working as a quality engineer in the utouch team [14:32] let me present the "architecture" of utouch briefly [14:33] the stack mainly consists of 3 (4) components [14:33] utouch-frame is an abstraction layer that takes care of device, window and touch event handling [14:34] and it abstracts away from "platform specifics" regarding touches [14:34] utouch-grail sits on top of utouch-frame and provides gesture recognition capablities [14:35] utouch-geis integrates both utouch-frame and grail to provide gesture recognition services to applications via different interfaces [14:35] for example: DBus [14:35] finally, we have utouch-evemu optionally below frame [14:36] obviously, a stack like utouch requires both unit-testing and integration-testing === vrruiz is now known as rvr [14:37] for both purposes, we rely on utouch-evemu to inject "fake" input events to the system [14:37] and this testing/injection layer allows us to record and replay corner/test cases [14:38] we use google test and its extension xorg-gtest to implement both our unit _and_ our integration testing [14:38] tvoss: so evemu exists just for testing purposes? Or is it needed in production environment as well. [14:39] mmrazik, evemu is mainly used for testing purposes [14:39] it relies on a kernel interface (uinput) to inject input events even below X [14:39] ok. I was just curious [14:39] (it used to be a runtime dependency in the old utouch stack, but isn't anymore) [14:40] as X and XI 2.2 are parts of our stack as well [14:40] any other questions so far? [14:41] * MrChrisDruif waits for the full "presentation" [14:41] a quick side note on xorg-gtest: it's a google test fixture/testing environment that takes care of starting/stopping a dummy x server environment [14:43] in our integration testing scenarios, we rely on xorg-gtest to start up a dummy server, insert fake events via evemu, and let them pass through the X server to utouch-frame [14:43] and to utouch-grail subsequently [14:44] with this chain in place, we are able to test both touch handling and gesture recognition with the help of pre-recorded touch sequences [14:45] so far for the actual testing setup. are there any questions? If not, I would go on with our continouos integration architecutre [14:45] just curious -- how many tests do we have in place right now? [14:45] for the integration part [14:45] mmrazik, all together, I would estimate like 20 overall cases [14:46] where each case might contain different types of gestures to be recognized etc [14:46] grail has 18, frame has 2 or 3 [14:46] some of them are regression tests [14:46] cnd, thanks [14:46] geis has maybe 5? [14:47] thx [14:47] okay :) [14:48] we use jenkins for continouos integration purposes [14:48] and we recently started working on a virtualization setup that allows us to build _and_ test frame, grail and geis in a vm [14:49] this allows us to do ci both for different releases/versions of ubuntu and for different platforms [14:49] currently, we run our builds and tests for precise on both i386 and amd64 [14:50] but we are planning to extend this to further versions and platforms in the future [14:50] I'd highly suggest ARM [14:51] MrChrisDruif, yeah, we are working on that [14:51] Seeing most tablets and smartphones are ARM, I wonder why that wasn't the first one [14:52] MrChrisDruif, well, problem here is the availability of vm's [14:53] only qemu supports arm at the present moment (at least, for alien host architectures) [14:53] MrChrisDruif, also, the code is platform agnostic [14:53] the tests will likely catch trivial bugs like variable size differences [14:53] MrChrisDruif: and HW in general. While our lab is "full" of x86* HW we don't have ARM ATM. [14:53] but as tvoss said. It is on our radar and we are actively working on this [14:54] the current plan is to have a functional setup for ARM testing for the 12.10 development cycle [14:54] which starts in few months [14:54] actually its more like a month [14:54] mmrazik, indeed :) [14:55] okay, putting all of the parts together, we are currently running builds and all of the tests for every merge to the trunk's projects [14:56] Great, thanks (had to check what agnostic code meant) [14:56] developers are provided with the unit test results/build logs and code coverage analysis results [14:56] (P.s.: 12.04 is in 30 days, so less then a month) [14:57] for the latter, we rely on instrumented code and gcov/lcov/gcovr to extract the results [14:57] MrChrisDruif: ack [14:57] MrChrisDruif, thanks [14:57] any other questions? [15:00] well, thanks for reading then :) [15:00] tvoss: thanks for the presentation [15:00] mmrazik, yw :) [15:00] thanks everybody for participating and see you next month [15:00] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology [15:00] Meeting ended Tue Mar 27 15:00:40 2012 UTC. [15:00] Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-03-27-14.30.moin.txt [15:00] Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-03-27-14.30.html [15:59] o/ [15:59] o/ [15:59] o/ [15:59] * SpamapS is finally going to chair [15:59] o/ [16:00] o/ [16:00] jamespage: don't you dare [16:00] * jamespage stands back [16:00] all yours! [16:00] who, almost had some friction there [16:00] hello [16:00] * SpamapS has no idea how his name kept getting pushed back, given he hasn't chaired in 3 months [16:00] actually I think SpamapS is in the chair for at least the next month [16:01] Server meeting? [16:01] Alright, we have a lot to get to and not much time so lets GO [16:01] #startmeeting Ubuntu Server Team [16:01] Meeting started Tue Mar 27 16:01:13 2012 UTC. The chair is SpamapS. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [16:01] Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu Server Team Meeting | Current topic: [16:01] No actions from last week, so lets get right into precise dev [16:01] #topic Precise Development === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu Server Team Meeting | Current topic: Precise Development [16:02] |o| [16:02] o/ [16:02] (btw, kvm disk io perf regrssion might ought to be added to agenda, not sure) [16:03] BTW, it would be helpful to have the release bug tracker in the meeting agenda [16:03] * SpamapS does not know the link [16:03] http://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html [16:03] SpamapS: probably should add that link and the server team blueprint link [16:03] I recall adding the link to the meeting page [16:04] Ok well I added the report link to the meeting [16:04] ubuntu server team blueprint link (for reference) http://status.ubuntu.com/ubuntu-precise/ubuntu-server.html [16:04] although that will obviously change with different cycles. [16:04] Ok, lots of bugs still to get through [16:05] bug #959426 [16:05] Launchpad bug 959426 in Glance "nova + glance services die if started before db is reachable" [High,In progress] https://launchpad.net/bugs/959426 [16:05] SpamapS: in progress [16:05] werd [16:05] bug #960276 [16:05] Launchpad bug 960276 in nova (Ubuntu) "a bad AMI can hang an entire compute node" [Critical,Confirmed] https://launchpad.net/bugs/960276 [16:05] chucks workin a replacement to the console fifo patch we're carrying [16:06] Ah, so thats something we broke? [16:06] :) [16:06] can somebody mark that bug In Progress/zulcss? kthx [16:06] is that related to the cosnole log growing indefinately? [16:06] bug #883988 [16:06] Launchpad bug 883988 in glance (Ubuntu Precise) "db migration failing when upgrading glance - trying to create existing tables" [High,Confirmed] https://launchpad.net/bugs/883988 [16:07] SpamapS: i have a patch for that, just trying to get upstream to sign off on it before we apply it. should happen this week, ive sent it already [16:07] hallyn: yeah [16:07] sweet [16:08] adam_g: should be status Triaged then [16:08] SpamapS: yeah, ill update bot [16:08] *both [16:08] and probably linked to upstream [16:09] bug #924739 [16:09] Launchpad bug 924739 in squid3 (Ubuntu Precise) "after upgrade from oneiric to precise, previous squid config unused, cannot be used when relocated" [High,Triaged] https://launchpad.net/bugs/924739 [16:09] heh, its all adam_g, All morning [16:09] /afternoon/evening depending on timezone ;) [16:09] ive sadly made no progress on that since last time, theres so much going on. if anyone else wants to help with that transition bug, please step up! :) [16:10] I suspect that will affect lucid to precise as well [16:10] yes, theres not much we can do to work around it but we can do our best to make it as obvious to users thats the transition has happened [16:10] anybody else have some available bandwidth to take over bug #924739? [16:10] Launchpad bug 924739 in squid3 (Ubuntu Precise) "after upgrade from oneiric to precise, previous squid config unused, cannot be used when relocated" [High,Triaged] https://launchpad.net/bugs/924739 [16:11] bug #928990 [16:11] Launchpad bug 928990 in cloud-init (Ubuntu) "fsck / dirty filesystem on instance is death" [High,Triaged] https://launchpad.net/bugs/928990 [16:11] SpamapS, adam_g: I can spare a few cycles - lemme catchup with adam_g later [16:11] smoser: is that just there for good measure? [16:11] probably. [16:12] i'd love it if someone wanted to take it [16:12] :) [16:12] but i dont have it on my list of things that i'm going to fix right now. [16:12] bug #930916 [16:12] Launchpad bug 930916 in amavisd-new (Ubuntu) "amavis start-stop script fails to stop amavisd" [High,Confirmed] https://launchpad.net/bugs/930916 [16:13] I haven't poked it since last time, but intend to.. soon.. I swear. ;) [16:13] smoser: I can't commit entirely to fixing it...but I can try. I have a lot on my plate, but I'm blocked today, so I'll take a stab [16:13] bug #959262 [16:13] Launchpad bug 959262 in python-novaclient (Ubuntu) "[Errno 13] Permission denied: '/var/www/.novaclient'" [High,Confirmed] https://launchpad.net/bugs/959262 [16:13] SpamapS: that one is fixed upstream, but we need to get it on their radar so its backported to essex/milestone-proposed. shouold happen today [16:13] otherwise we can patch, but shouldnt need to. its trivial [16:14] adam_g: is it definitely going to happen before release, or 0-day SRU? [16:14] bug #880339 [16:14] Launchpad bug 880339 in mysql-5.5 (Ubuntu Precise) "AppArmor profile needs update" [Medium,Incomplete] https://launchpad.net/bugs/880339 [16:15] SpamapS: should happen well before [16:15] That one is actually Fix Committed .. just need to get 5.5.22 in as well [16:15] we really don't need to be thinking about 0-day SRU's yet. [16:15] adam_g: alright [16:15] Daviey: lot of bugs here.. not much time. ;) [16:16] bug #907197 [16:16] Launchpad bug 907197 in nova (Ubuntu) "ip address can't be injected into the instance when using lxc " [Medium,Incomplete] https://launchpad.net/bugs/907197 [16:17] Bueller? Bueller? [16:17] zul: ^^ ? [16:17] no response from user [16:17] SpamapS: if we have time to plan to do a 0-day SRU at this stage, we have time to get it in the release. :) [16:17] bug #966069 [16:17] Launchpad bug 966069 in horizon (Ubuntu) "/etc/apache2/conf.d/dashboard.conf contains wrong paths in the Ubuntu package" [Medium,New] https://launchpad.net/bugs/966069 [16:18] Daviey: I admire your optimism! :) [16:18] zul is already cracking that one out i think [16:18] SpamapS: fixed in bzr [16:18] \o/ [16:18] bug #901881 [16:18] Launchpad bug 901881 in glance (Ubuntu) "nova and glance should depend on python-keystone" [Low,New] https://launchpad.net/bugs/901881 [16:19] zul: can you make sure the status is right on that bug? === ralsina is now known as ralsina_lunch [16:19] yep [16:19] bug #959426 [16:19] Launchpad bug 959426 in Glance "nova + glance services die if started before db is reachable" [High,In progress] https://launchpad.net/bugs/959426 [16:20] SpamapS: in progress just like the nova task [16:20] same fix, basically [16:21] sweet [16:21] on to blueprints [16:21] http://status.ubuntu.com/ubuntu-precise/ubuntu-server.html [16:22] so we are at week 24/28 Bet2 release on the 29th [16:22] ~85% thorough the cycle if you count all the way up to release [16:23] Overall progress is 77%, so we have a few blueprints we need to evaluate if we are going to be able to complete this cycle [16:23] SpamapS: Would you like to iterate through the blueprints? [16:23] arosales: I was just looking through them for those that seem behind [16:23] servercloud-p-juju-charm-testing [16:24] m_3 and I are working on getting that one back on track this week. [16:24] servercloud-p-openstack-testing [16:25] adam_g: only one TODO left, Collaborate on defining charm use workflow between OpenStack and Ubuntu: TODO ... seems like that doesn't make much sense to do before 12.04 releases [16:25] servercloud-p-automated-boot-testing [16:26] That one is mine, and I need to update the status. jamespage has saved me on this one, and we actually have a single reboot test now for LAMP :) [16:26] SpamapS: its something we'll likely be discussing at ODS in a couple of weeks, so left as a TODO till then. but right, its not release critical by any means [16:26] adam_g: alright sounds good [16:26] servercloud-p-cloud-power-management [16:27] I'm going to invite aquette to come to next week's meeting so we can discuss this [16:27] SpamapS: that sounds great [16:28] #action SpamapS invite aquette to next server team meeting to discuss servercloud-p-cloud-power-management [16:28] ACTION: SpamapS invite aquette to next server team meeting to discuss servercloud-p-cloud-power-management [16:28] https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-arm-service-orchestration [16:28] SpamapS: EOF? [16:29] couple more [16:29] rbasak: that one looks mostly on track, just pinging you on it since its < 75% [16:29] rbasak: We can go through, [racb] Validate cobbler enlistment works: TODO .. later if you want? [16:30] also [racb] Validate juju using orchestra: TODO should probably be maas. :) [16:30] I feel a bit blocked on the new orchestra stuff and ARM support [16:30] rbasak: Grab me after this? [16:30] It's not quite clear what needs to be done with regard to this. [16:30] Daviey: OK [16:30] https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-ceph [16:31] MIR still pending.. I think I'll postpone a few of the items in that one this week. [16:31] we may want to take more active role in that one next cycle [16:31] the MIR team are *too* loaded right now. [16:31] Yes, I think the MIR team needs another member. [16:31] Adding anything other than pure essential stuff is a no-go [16:32] Its likely we'll continue to add openstack components and other bits. [16:32] Ie, if it's not the on the cd, it's a hard push to consider a MIR now. [16:32] https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-orchestra [16:32] That one is mostly on track, but looks a little behind [16:33] now accurate [16:33] https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-openstack [16:33] Perhaps just lagging on WI updates? [16:33] zul: ^^ [16:34] Daviey: yeah need to update it today [16:34] mostly on track though [16:34] https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-kvm-document-suggested-changes [16:34] Just updated that. What remains TODO, I intend TODO [16:34] sweet [16:34] groovy [16:35] just a couple more [16:35] https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-juju-mir [16:35] Been working with jdstrand on this directly all week. [16:36] seemed intensive [16:36] We have some security concerns to address, but otherwise it is progressing. [16:36] https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-openstack-charms [16:37] adam_g: ^ [16:37] Some of these I think can be pushed as updates to the charms post-release [16:37] SpamapS: those are all not release critical, and not sure which will get done before release [16:37] adam_g: perhaps just POSTPONE them and if you end up doing them, go back and change them to DONE? [16:37] i think pots-UDS calm would be a better time to address those, short of the swift tasks.. those charms need updating for keystone auth [16:38] SpamapS: yeah, sounds good [16:38] https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-juju-roadmap [16:38] Last one [16:39] juju team is landing many of those this week [16:39] - Okay.. So.. Beta-2... - [16:40] aye [16:40] I'll be doing another spin later on today. [16:40] how come? [16:40] Is there anything else which is a candidate for inclusion ? [16:40] zul: Some changes required on the cd. [16:40] :) [16:40] Daviey: there are some other openstack rc1's that trickled in after freeze [16:40] nova, especially [16:40] adam_g: I saw a less than important quantum upload [16:41] anything else? [16:41] Daviey: i think nova was the only in-main component [16:41] zul ? [16:41] Has that been uploaded? Is it in the queue? [16:41] oh! [16:41] keystone, though not in main [16:41] it beens uploaded for a while now [16:41] ok [16:41] I also pruned some things from the cd.. [16:41] (including puppet and zsh) [16:42] Anything else beta-2 critical ? [16:42] not zsh!! ;) [16:42] Daviey: I can get you a few MB in mysql-client [16:42] SpamapS: fear not, it's still in mai. [16:42] SpamapS: have bags of space right now :) [16:42] now ruby is off the cd :) [16:42] ok good [16:42] (about ruby being gone, not your space.. who cares about space? ;) [16:43] Okay, nothing else of importance.. lets skip beta-2 and go straight to release. :) [16:43] https://bugs.launchpad.net/ubuntu/+source/vde2/+bug/776818 [16:43] Launchpad bug 776818 in vde2 (Ubuntu) "[MIR] vde2" [Undecided,Confirmed] [16:43] space...the final frontier...these are the voyages of the.. [16:43] basically i was wondering if anyone else wanted to asnwer jdstrand's question: "does serverr team want this" [16:44] i think the answer is, users want it so yes, [16:44] heh, at this point, "Not for P" [16:44] naturally :) [16:44] but if the answer is yes, better to answer that now so when they have time, mir team can consider [16:45] otoh, [16:45] vde2 is way behind debian's version, and noone has cared enough to mention it [16:45] I know it sucks to keep pushing back but this is LATE [16:45] hallyn: I'd like a UDS session on making kvm rock harder.. this can be discussed there [16:45] lets push this to Q and make sure it happens in Q [16:46] SpamapS: of course it's pushed to Q, but i don't think answering the q should be pushed to q [16:46] all right ifne [16:46] Sounds good [16:46] hallyn: we can push it to discuss at UDS-Q. :) [16:46] time to move on [16:46] #topic Ubuntu Server Team Events === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu Server Team Meeting | Current topic: Ubuntu Server Team Events [16:46] Daviey: (we did that last time :) [16:46] hallyn: *doh* [16:47] Daviey: (note that comment was written *at* uds-p) [16:47] Events, Openstack Design Summit [16:47] events... uds coming up :) [16:47] jcastro and marcoceppi are presenting on juju at POSSCON http://www.posscon.org/ [16:47] - Apr 16-18 in San Francisco [16:48] ^ ODS [16:48] Also the conference is the 2 days after that :) [16:48] m_3 @ DevOptsDays Austin April 2-3 [16:48] url? [16:48] m_3 and robbiew will be at DevOpsDays Austin next week http://devopsdays.org/ [16:49] thx [16:49] arosales: jynx [16:49] :-) [16:49] thanks for providing the URL [16:49] ok, we have just 11 minutes left [16:49] #topic Weekly Updates & Questions for the QA Team (hggdh) === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu Server Team Meeting | Current topic: Weekly Updates & Questions for the QA Team (hggdh) [16:49] hggdh: anything to report? [16:49] I suspect once Daviey does his respin we should all try to crank out some ISO testing [16:50] nothing, except I had just finished the server tests when I heard of the respin... [16:50] .. [16:50] someone buy the man a cupcake :( [16:50] hggdh: I just threw something across the room in your honor [16:50] SpamapS: actually, yes, help will be very appreciated ;-) [16:50] SpamapS: thank you. I hope it did not break anything [16:51] 4 more test cases will be added to the tracker later doay [16:51] today [16:51] Seriously, people, give the iso a try.. http://iso.qa.ubuntu.com [16:51] Daviey: perfect [16:51] ping on ubuntu-server when respin complete? [16:51] hallyn: sure [16:51] #topic Weekly Updates & Questions for the Kernel Team (smb) === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu Server Team Meeting | Current topic: Weekly Updates & Questions for the Kernel Team (smb) [16:51] Hi [16:51] Meddled a bit more in libvirt and could find the reason why xen shutdown is not seen in some cases. Sent patches upstream (to be so far ignored) and asked hallyn for sponsorship into precise. [16:51] Hey smb.. How is our lovely kernel? [16:51] Apart from that not that much exiting. :) [16:52] .. [16:52] smb: i386 on heavy boxes? Is that being worked on? [16:52] Yes, apw wanted to think about a few things [16:52] Daviey, you read Andy's analysis, right ? [16:52] He had a few ideas how to go forward there [16:52] smb: In time for kernel final freeze? [16:52] tgardner: Yes, it was very compressive [16:53] comprehensive [16:53] * smb believes the probablility is good [16:53] Daviey, I don't think there is anything we'll do before freeze [16:53] much love to the kernel team.. I have no complaints... both my macs, and my hundreds of short lived EC2 instances have all worked perfectly. :) [16:53] tgardner: I tohught the outcome was a printk "System incompatible with current kernel" etc. [16:53] Daviey, I think we can do that [16:54] except I think there's possibility our kvm guest perf woes might need kernel love... need to dig further [16:54] tgardner: I am adding to our MIN system requirements a MAX system requirement for i386, for the release notes. [16:54] hallyn: You've been speaking to smoser about kvm perf? [16:54] hallyn, Keep me posted there [16:54] yes [16:54] both [16:54] groovy [16:54] Daviey, Andy knows the most about this, but he's not in right now. [16:54] yeah, thats gonna be fun. [16:54] ok, thanks tgardner / smb [16:55] Alright moving on [16:55] #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak) === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu Server Team Meeting | Current topic: Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak) [16:55] i just want to make sure that we do a reasonable job, and ideally pick off the low hanging fruit for this cycle, not next. [16:55] Nothing to report. Any questions for me? [16:55] rbasak: mind running an lxc testsuite on arm in next week or two? [16:55] rbasak: I can has armserver?! kthxbai [16:55] hallyn: sure. [16:55] (i need to convert it to pyunit, but for now...) [16:55] thx [16:56] hopefully no weird apparmor related glitches there [16:56] rbasak: thanks! [16:56] #topic Open Discussion === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu Server Team Meeting | Current topic: Open Discussion [16:57] Nothin' from me, expect - well done on getting this far chaps! [16:57] s/pect/cept/ [16:57] ta [16:57] +1 [16:58] indeed, 12.04 is going to be awesome. :) [16:58] #topic Announce next meeting date and time === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu Server Team Meeting | Current topic: Announce next meeting date and time [16:59] Tue, April 3, 16:00 UTC, right here [16:59] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology [16:59] Meeting ended Tue Mar 27 16:59:21 2012 UTC. [16:59] Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-03-27-16.01.moin.txt [16:59] Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-03-27-16.01.html [16:59] thanks everybody! [17:00] #startmeeting [17:00] ## [17:00] Meeting started Tue Mar 27 17:00:06 2012 UTC. The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [17:00] ## This is the Ubuntu Kernel Team weekly status meeting. [17:00] ## [17:00] [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting [17:00] Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired [17:00] [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Precise [17:00] # Meeting Etiquette [17:00] # [17:00] # NOTE: '..' indicates that you are finished with your input. [17:00] # 'o/' indicates you have something to add (please wait until you are recognized) [17:00] Roll Call for Ubuntu Kernel Weekly Status Meeting [17:00] o/ [17:00] o/ [17:00] o/ [17:00] o/ [17:00] o/ [17:00] \o [17:00] o/ [17:00] o/ [17:00] [TOPIC] ARM Status (ppisati) === meetingology changed the topic of #ubuntu-meeting to: ARM Status (ppisati) [17:01] P/omap4: since a critical bug (lp963512 - "Latest kernel updates broke video on omap4") was affecting 3.2.0-1410.13, for beta2 the kernel was reverted to a previous working version (3.2.0-1409.12). AFAIK the regression came with latest rebase on master (3.2.1[0-2]) while the TI BSP was unchanged - so it's either a bad interaction between upstream/TI BSP or it's a brand new bug we got from upstream. [17:01]