=== txwikinger2 is now known as txwikinger === nxvl_ is now known as nxvl === nellery_ is now known as nellery === asac_ is now known as asac === persia_ is now known as persia [09:36] @schedule berlin [09:36] Schedule for Europe/Berlin: 28 Oct 12:00: Asia Oceania Membership Board | 28 Oct 17:00: Server Team | 28 Oct 18:00: Kernel Team | 28 Oct 20:00: EMEA Membership Board | 29 Oct 18:00: QA Team | 29 Oct 23:00: Platform Team === emonkey-t is now known as emonkey === ubottu changed the topic of #ubuntu-meeting to: Current meeting: Asia Oceania Membership Board Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 28 Oct 16:00: Server Team | 28 Oct 17:00: Kernel Team | 28 Oct 19:00: EMEA Membership Board | 29 Oct 17:00: QA Team | 29 Oct 22:00: Platform Team [10:53] ahoi [10:54] Greetings. [10:54] Good evening. [10:54] Good evening [10:54] No applicants on the agenda... [10:54] yep.. [10:55] i feel bad for being happy about that :Þ [10:55] especially since release time is coming up, and there's plenty of people doing awesome work [10:56] and zakame, belutz not turning up for quite some time! [10:57] Did you ever hear back from them regarding the possible time change? [10:57] i havent seen a peep on the list [10:57] they probably filter the list mail off, and are more likely to look at actual inbox [10:58] persia: No [10:59] lifeless: there? [10:59] Hrm. I think the rest of us said positive things about it (although it's of especial interest to all of you because of the time). [11:00] hi [11:01] lifeless: Hey! glad... [11:01] we are five today, and no one turning up... [11:02] easy meeting then [11:02] week after next I can't be here [11:02] good.. I will take it up with the community council next time for sure on two aspects.. [11:02] 1) Adding two more members to the Board [11:03] 2) Requesting them to consider two-three months of contribution is enough for considering memberships [11:04] and the time factor, We need to decide among ourselves, May be we will wait till new members arrive before deciding on that, assuming CC approves it [11:04] lifeless: Ok [11:05] is that fine with every one? [11:05] amachu, So we're asking for replacements for zakame/belutz? Doesn't make sense to make the team larger unless we propose the time change. [11:05] I don't know about 2) [11:05] 1) makes sense if we're going to vary the times more [11:06] its 10pm here now, any .nz folk its midnight for [11:06] persia: no, not replacements for them, we were discussing about having nine on board three from each zone [11:07] amachu, That only makes sense if we do the time split. [11:08] We need to time split, but I am only considering who the new members would and what would be their opinions.. [11:09] huh? [11:09] Other boards are seven. Why do we need nine? [11:09] Answer: Because we want to split the time. [11:09] persia: yes.. [11:10] So, the time split and the request for two additional members (7-9) are the *same* request. [11:10] Asking for going from 5 active to 7 active is a different question. [11:10] yes.. [11:10] time split to be decided among ourselves, and approval from CC for two more members [11:11] I will put forth we have decided to split time and hence we need two more on board.. [11:11] i'd recommend making real contact with the guys before dethroning them. [11:11] I agree. [11:11] elkbuntu: thats true [11:12] I agree that real contact is important. [11:12] amachu: I think persia's point is that when we split the time we become de facto a split subboard [11:12] so its not so much adding members as reforming into smaller boards [11:12] I also think we need CC approval for the time split, rather than just agreeing between ourselves. [11:13] lifeless, Well, kinda. I'm expecting three members to sit on both (UTC +8,+9), and three members from ~10-+12, and three members from +5:30 - +7) to bring us to quota each week. [11:13] agreed. i think we need to put ourselves on the agenda for the next 3rd week/CC clash. [11:13] I have no objections to a full split, but that's different. [11:14] persia: CCs approval for time split? === bazhang_ is now known as bazhang [11:15] amachu, I'd think so : it's a big change from how we were asked to organise. [11:16] definitely We will be putting forth that to the CC and that as the reason for new Board members.. [11:17] OK. We still need to track down our lost sheep though. I'm especially surprised by Belutz who was so active at the start. [11:18] It would be nice if they could state whether they intend to continue helping with the board. [11:18] s/could/would/ [11:18] we need, may be I will mail them personally this time [11:19] That sounds like a good plan. [11:19] If that doesn't work, perhaps we can try to catch them on IRC individually (if anyone has a good script to track people). [11:19] Send them memos? [11:19] Or whatever they are called? [11:20] That is if they have registered with freenode., [11:20] I was thinking personal conversations, as that's more reliable. [11:20] True. [11:20] I will mail them to take their opinions [11:20] I think there is a tool that can track when people join, and open chat, but I'm not familiar enough with IRC. [11:20] persia, or we could just steal someone's private jet and hunt them in person [11:20] I also think mail is the better first step, and IRC stalking should only be done if mail fails. [11:21] elkbuntu, That's lower on the list. I was thinking telephone before personal vist. [11:21] ML post, personal email, IRC, telephone call, physcial visit : in rough order of decreasing invasiveness. [11:21] nothing personal about smart bombs [11:21] i figured the plane would bump it up in priority [11:23] lifeless, You've clearly not investigated the options available from miniaturisation : smaller planes, smaller bombs, more personal. [11:24] :) [11:24] so is that all for the week? [11:25] * persia has no additional agenda items [11:25] * TheMuso has no agenda items. [11:25] lifeless & elkbuntu ? [11:26] I have no agenda [11:26] i think so [11:28] Thank you all.. [11:28] Thanks. [11:29] We will have our next meeting on 04 Nov 08, Will keep the mailing list updated on other happenings [11:30] See you all then. === e-jat is now known as norly === ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 28 Oct 16:00: Server Team | 28 Oct 17:00: Kernel Team | 28 Oct 19:00: EMEA Membership Board | 29 Oct 17:00: QA Team | 29 Oct 22:00: Platform Team | 30 Oct 12:00: Ubuntu Mobile Team [13:34] boredandblogging: hi [13:34] LjL: hi [13:35] boredandblogging: can you explain to me what the current status of the events calendar is in more detail? namely, what are the places one can get a feed [13:35] LjL: there are two feeds being maintained at the moment [13:36] the fridge feed and google calendar feed [13:36] we would like the bot to read the google feed [13:37] the issue is that the bot doesn't properly deal with repeating events in the calendar [13:37] so if a meeting is booked for every Tuesday at 9am [13:38] it will only show the first Tuesday [13:38] and none of the others [13:42] boredandblogging: you mean in the topic, or in @schedule, or everywhere...? [13:45] boredandblogging: and what's the URL to the google calendar anyway? [13:46] LjL: yeah, everywhere [13:49] LjL: http://www.google.com/calendar/ical/j5q85mmi6ujvjtii5s1n3li5io%40group.calendar.google.com/public/basic.ics [14:00] boredandblogging: so wait, ubottu right now is reading the Fridge iCal feed (not the Google feed, although it's also in iCal format), right? *but* even if it were reading the Google feed, repeating events wouldn't be handled properly, is that right too? [14:15] LjL, That's a correct summary. === dholbach_ is now known as dholbach [14:33] persia, boredandblogging: sorry that i'm just catching up, but... while the normal ubottu code simply can't parse the Google Calendar file at all (it bails out with an error), it was pretty trivial to fix that. now i don't know if it's outputting the right stuff, but it's not failing at least - was that already done before? [14:34] LjL, There's a patch floating about for that. The problem is the function to determine the next N meetings, or compare the current time to see if it is a meeting. [14:35] The current code can tell that something is recurring, but since Google only sends it once, and expects the client to be able to determine the recurrance, it doesn't know when it will happen again. [14:38] persia: wait, you're saying that after a while, the recurring event simply won't be in the ical feed anymore, and the client is expected to have it cached from before? [14:39] LjL: No, I'm saying that the iCal feed has the date of the first occurance and the rules to determine follow-up occurances, rather than one entry per occurance. [14:39] persia: ah ok, that's not *so* bad then [14:39] The current code can't handle the calculations to determine when the event recurs. [14:39] No, it's just the need for a recurrance processing module to be written. Should be a few days work for someone with enough python knowledge. [14:41] persia: from the samples i see in the current calendary, the "BYDAY" rule looks like the most irritating to implement [14:42] and as far as i can see, it's currently parsed by totally ignored [14:42] LjL, Yeah, that's about the state of things. Just needs someone to dig into it. === jdstrand_ is now known as jdstrand [14:44] persia: do you know what BYDAY=-1SU means? last sunday of the month? [14:44] I have no idea, but that seems a reasonable guess. [14:59] * mathiaz waves [14:59] o/ [14:59] hello [14:59] yo [15:00] how is everyone doing? [15:00] cold [15:01] * mathiaz hands a pile of mentos to zul [15:01] wohoo..... [15:02] all right - let's get this started [15:02] #startmeeting [15:03] Meeting started at 10:02. The chair is mathiaz. [15:03] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [15:03] Today's agenda: https://wiki.ubuntu.com/ServerTeam/Meeting [15:03] last week's minutes: https://wiki.ubuntu.com/MeetingLogs/Server/20081021 [15:04] I don't see any outstanding actions from last weeks meeting. [15:04] o/ [15:04] someone wants to add something wrt to the topics from last week meeting? [15:05] seems like not. let's move on [15:05] [TOPIC] Final blockers. [15:05] New Topic: Final blockers. [15:05] So we're testing the -server iso candidates for Final. [15:06] Anyone came accross a bug that should be noted in the release notes? [15:06] mathiaz: not sure what's the status on iscsi [15:06] [TOPIC] iscsi in intrepid [15:06] New Topic: iscsi in intrepid [15:07] so we've decided to not update iscsi for release [15:07] intrepid will ship with an iscsi that doesn't support more than one iscsi target [15:08] everything is tracked in bug 289470 [15:08] Launchpad bug 289470 in open-iscsi "open-iscsi user-space does not match kernel module version" [Critical,In progress] https://launchpad.net/bugs/289470 [15:09] there will be a note added to the release notes [15:10] nijaba: do you have other questions? [15:10] mathiaz: nope, that's pretty clear [15:10] so the plan is to fix iscsi in an SRU [15:11] anything else to mention with regards to potential blockers for release? [15:12] seems like not. [15:12] so release! [15:12] yay [15:13] well - let's do some testing first :D [15:13] kirkland: around? [15:14] hm. well [15:14] [TOPIC] Server FAQ [15:14] New Topic: Server FAQ [15:14] nijaba: ^^? [15:15] yes, I have noticed that the server FAQ on help.u.c is quite outdated [15:15] https://help.ubuntu.com/community/ServerFaq [15:15] I was wondering if someone would enjoy helping me updtaing it [15:16] sure [15:17] nijaba: do you think about updating the list of questions? [15:17] sommer: I think we should start listing what are the appropriate questions [15:17] nijaba: or just updating the answer [15:17] and then work on the answers [15:17] nijaba: ya, some of those are pretty old [15:17] anyone is welcome to add questions [15:17] mathiaz: sorry, my connectivity is been intermittent this morning [15:18] do you see two faqs, a new one for hardy? [15:18] nealmcb: nope, only one for server [15:18] and cover both dapper and hardy? [15:19] yep [15:19] yeah it makes sense to have it all on one page [15:20] it seems that most questions are fairly generic and not tied to a specific release [15:20] so action for next week: prepare questions [15:20] who would like to do that? [15:20] nijaba: sommer ? [15:21] sure, I can put a list together [15:21] anyone is welcome, but sommer and I seem to have commited to it. I think we can just go ahead and add at the bottom of the cirrent page [15:22] [ACTION] sommer and nijaba to review the list of questions to be included in the Server FAQ [15:22] ACTION received: sommer and nijaba to review the list of questions to be included in the Server FAQ [15:22] nijaba: anything else? [15:22] not on this subject [15:23] [TOPIC] Ubuntu "easy server" for the home user [15:23] New Topic: Ubuntu "easy server" for the home user [15:23] kirkland: ^^? [15:23] xivulon: ^^? [15:23] mathiaz: this is from a user who pinged me privately [15:24] xivulon: are you around? [15:24] mathiaz: evidently not .... [15:24] ok. [15:24] mathiaz: sorry. [15:25] kirkland: do you want to postpone it to next week? [15:25] mathiaz: he claimed to have some ideas as to making the server easier to use for the home user [15:25] might be a DST issue ? [15:25] mathiaz: yes, let's postpone one week [15:25] ok [15:26] I spoke with him about that for a bit at the last UDS : he has a bunch of ideas on the topic. [15:26] persia: will he attend UDS? [15:26] some of the history of this topic is at http://brainstorm.ubuntu.com/idea/68/ [15:26] * persia tries to find the jaunty registration page [15:27] Idea #68: GUI configuration front end for common services [15:27] mathiaz, He's registered at https://launchpad.net/sprints/uds-jaunty so I suspect so. [15:27] * nealmcb wonders if ubottu should help with brainstorms like with bugs [15:28] persia: great. [15:28] [TOPIC] Open Discussion [15:28] New Topic: Open Discussion [15:28] anything to add? [15:29] is there an Ibex tshirt? [15:29] nijaba: don't know [15:30] nijaba: you plan to make one? [15:30] mathiaz: you should go ask Kat, this is so IMPORTANT ;) [15:31] * kirkland notes that the 'Frozen Bubble' joke at the last server meeting made the news [15:31] * zul keeps quiet [15:31] https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue114#Server Team Meeting October 21st, 2008 [15:32] well that didn't paste well [15:32] kirkland: Frozen Bubble is *not* a joke, that's serious [15:32] You all do know that Frozen Bubble is blamed for delaying Sarge, and Sarge delays were oft discussed in the post "There will be an Ubuntu" discussions, right? [15:33] persia: yes, kees has told the story [15:33] Do take care with the level of your addictions : it's free to start, and makes you feel good, but ... [15:34] persia: thanks for finally shedding some light on this :) [15:34] persia: smoker do know about addictions ;) [15:36] hi guys just back [15:36] Is there any action to take wrt to Frozen Bubble? [15:36] still in time? was in another meeting [15:37] xivulon: sure [15:38] the other day I was discussing with kirkland and superm1 whether there was any interest in a ubuntu-home-server [15:39] basically a dumbed down web interface for home users, possibly on the back of ubuntu-easy-business-server [15:40] I had drafted a very basic spec some time ago' on the subject (https://wiki.ubuntu.com/ZeroConfServer) [15:41] but then was taken by wubi development and have dropped the idea [15:41] xivulon: have you seen http://brainstorm.ubuntu.com/idea/68/ Idea #68: GUI configuration front end for common services [15:42] not yet [15:43] there has been strong interest expressed in this sort of thing for a long time, and ebox and Augeas are helping us close in on it, but still it is taking a long time.... [15:43] xivulon: there is also a spec written by ScottK - https://blueprints.launchpad.net/ubuntu/+spec/server-flavors [15:43] yes something like that, my idea was to do it as simple as possible [15:43] for instance home users do not need groups [15:44] all permissions should be set directly for users [15:44] and there are other services of interest to home users that are not necessarily relevant for businesses [15:44] xivulon: like nealmcb said, the topics has already been discussed in former UDS. [15:44] xivulon: as it seems you're coming the next one, we'll probably have some time to sit down and discuss this topic a bit [15:45] xivulon: thanks for the zeroconfserver spec - I'll look at it and agree that a very simple interface for the home would also be great [15:45] of course sometimes UI simplicity is hard to achieve :) [15:45] xivulon: writting a spec is a good step [15:46] basic concept is to provide a simple interface for common tasks, advanced users can also tweak /etc settings [15:46] xivulon: I'd focus on the user cases and specify who is the target user [15:46] the interface should not "break down" if more advanced configrations are used [15:46] xivulon: that's the tricky part. [15:47] xivulon: agreed. These concerns have already been raised and no perfect solution haven't been found yet. [15:47] I will revamp the spec a bit, was a couple of years ago' and just a quick draft [15:47] we will then take it from there [15:47] xivulon: sounds like a good plan to me. [15:47] I'd think that home users would far rather move on to something like ebox than editing in /etc.... [15:48] but do look at augeas.... [15:48] allright - anything else on this subject? [15:48] xivulon: ? [15:48] nealmcb: is augeas already used in ebox? [15:49] xivulon: thanks again - I'm glad to have more folks thinking about this! [15:49] raphink: not yet as far as I know, but there have been discussions [15:49] nealmcb: ok thanks [15:49] are ebox folks coming to uds? [15:50] nealmcb: I don't know === ubottu changed the topic of #ubuntu-meeting to: Current meeting: Server Team Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 28 Oct 17:00: Kernel Team | 28 Oct 19:00: EMEA Membership Board | 29 Oct 17:00: QA Team | 29 Oct 22:00: Platform Team | 30 Oct 12:00: Ubuntu Mobile Team [15:50] allright - anything else to add? [15:51] We're testing the final isos - help is welcome - #ubuntu-testing is the place to hang out. [15:52] [TOPIC] Agree on next meeting date and time [15:52] New Topic: Agree on next meeting date and time [15:52] next week, same place, same time? [15:52] 16UTC to adapt to DST? [15:52] DST will be effective in the US at that time IIUC [15:53] yay for DST [15:53] nijaba: seems like a good idea [15:54] so next week, 16:00 UTC in #ubuntu-meeting? [15:54] +1 [15:54] +1 [15:55] +0 rather, I don't really mind either way [15:55] +1 for me [15:55] well - let's switch to 16:00 UTC so that the meeting doesn't move. [15:55] dendrobates: hi :) [15:55] stupid time change. [15:55] dendrobates: you wanted to add something? [15:56] nope [15:56] ok great === lieb is now known as lieb_ [15:56] see you all next week, same place at 16:00UTC [15:56] Note that the meeting does change for some people if you change the time. For some people it even moves from the not unreasonable 1am to the very awkward 3am. === lieb_ is now known as lieb_commute [15:57] (because of recent corresponding opposite DST correction) [15:57] persia: hm... are you refering to the australians? [15:57] For 3am, yes. [15:57] For me, you're just moving it from 0:00 to 1:00, but I mostly just watch, without that much to add. [15:58] persia: hm - right. However I haven't seen many australians active in the server team meeting for the last 3/4 months now [15:58] Well, it was 1:00 even then :) [15:58] Anyway, I'm just providing information, rather than saying it's a bad time. [15:59] ok. [15:59] so let's go back to iso testing [15:59] will dst really change next week? I thought it was delayed [15:59] o/ [16:00] nealmcb: according to timeanddate.com yes [16:00] hmm - I guess not - ok [16:00] ok - happy iso testing! [16:00] see ya all next week! [16:00] #endmeeting [16:00] Meeting finished at 11:00. [16:00] later all [16:08] morning [16:09] @schedule berlin [16:09] Schedule for Europe/Berlin: Current meeting: Server Team 28 Oct 18:00: Kernel Team | 28 Oct 20:00: EMEA Membership Board | 29 Oct 18:00: QA Team | 29 Oct 23:00: Platform Team | 30 Oct 13:00: Ubuntu Mobile Team === lieb_commute is now known as lieb === ubottu changed the topic of #ubuntu-meeting to: Current meeting: Kernel Team Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 28 Oct 19:00: EMEA Membership Board | 29 Oct 17:00: QA Team | 29 Oct 22:00: Platform Team | 30 Oct 12:00: Ubuntu Mobile Team [17:01] Hello everyone... time for the kernel team weekly meeting [17:01] #startmeeting [17:01] Meeting started at 12:01. The chair is pgraner. [17:01] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [17:01] * lieb wakes up [17:01] [TOPIC] Welcome new members [17:01] New Topic: Welcome new members [17:02] I'd like to welcome Steve Conklin as the newest member of the kernel team. Steve is joining us from HP. [17:02] sconklin: Welcome! [17:02] hi all! [17:03] schily, Welcome +1 [17:03] dude [17:03] sweet [17:03] sconklin: welcome! [17:03] Steve will be working with rtg and smb_tp on stable maint for awhile. [17:04] [TOPIC] Intrepid Status [17:04] New Topic: Intrepid Status [17:04] So far the release is looking very good. No major issues or breakdowns. We are on schedule. About to hit test cycles [17:05] Many of the team are in London today in the war room and its very calm :-) [17:05] We will keep our fingers crossed and are looking forward to the release party on Thurs. evening. [17:05] * BenC wishes he had planned to be in london this week [17:06] [TOPIC] Intrepid Updates [17:06] New Topic: Intrepid Updates [17:06] With Intrepid winding down we need to address all the bugs that didn't make the release. [17:06] They are tagged with "intrepid-updates' [17:07] pgraner: there is at least one oops in i4965 w/802.11n that needs some TLC [17:07] If you have any bugs (i.e. the Dell double key bug) that need to go out we need to get them tagged ASAP. [17:07] I'd like to get everyone focused on getting those bug knocked out ASAP. [17:08] The current list is at: [17:08] [LINK] https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bugs?field.searchtext=&orderby=-importance&search=Search&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.milestone%3Alist=2134&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=& [17:08] field.tags_combinator=ANY [17:08] LINK received: https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bugs?field.searchtext=&orderby=-importance&search=Search&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.milestone%3Alist=2134&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=& [17:08] They are already tagged, take a look and if you know of any that should be there get them tagged. Next meeting we will set the release date of this kernel [17:09] [ACTION] pgraner to add kernel date to next weeks agenda [17:09] ACTION received: pgraner to add kernel date to next weeks agenda [17:09] We will do a separate security kernel. We need to work with kees on the ordering based on CVE severity. [17:10] smb_tp: once Intrepid goes out, it falls with you as maint. [17:10] Any questions? [17:10] pgraner, Yep sure [17:10] CVE severity was low according to kees. (up to now) [17:11] smb_tp: I know thats why we need to figure out do we do the bugs first or the CVEs [17:11] * pgraner things at this point bugs [17:11] s/things/thinks/ [17:11] * smb_tp thinks so, too [17:11] [TOPIC] Status of wireless backport (timg) [17:11] New Topic: Status of wireless backport (timg) [17:11] rtg: can we get this into the bug fix kernel? [17:12] Im keeping pace with Linville's updates. Its testing right now, but looks good. [17:12] rtg: i.e. how much more time do you need [17:12] I'm want to make sure I don't hose the -mid guys [17:12] I'll test for another day or so, but I think its ready [17:12] rtg: understand. You have a week to estimate a timeframe. [17:13] k, anything else? [17:13] rtg: not from me on this topic [17:14] [TOPIC] QA Bugs [17:14] New Topic: QA Bugs [17:14] ogasawara: whats new? [17:14] I wanted to point out https://bugs.edge.launchpad.net/ubuntu/+bug/287711/comments/4 [17:14] Ubuntu bug 287711 in linux-backports-modules-2.6.27 "wireless network lags - rt61pci driver" [High,Triaged] [17:14] rtg: you aware of this one? [17:15] nope, lemme have a look. [17:15] [LINK] http://people.ubuntu.com/~ogasawara/intrepid-buglist.html [17:15] LINK received: http://people.ubuntu.com/~ogasawara/intrepid-buglist.html [17:15] i mean, I'll look later [17:15] rtg: Cool. [17:15] additionally, I was working with bug 286169 and we've narrowed it down to a patch that was cherrypicked from upstream [17:16] Launchpad bug 286169 in linux "battery and thermal dissappears after few minutes of booting. on msi ex600 laptop" [High,Triaged] https://launchpad.net/bugs/286169 [17:16] ogasawara: nice. Can you start tagging them with the updates tag [17:16] pgraner: sure [17:17] ogasawara: that EC storm patch fixed some other issues. [17:17] [ACTION] ogasawara to tag low hanging fruit bugs for intrepid-updates [17:17] ACTION received: ogasawara to tag low hanging fruit bugs for intrepid-updates [17:17] rtg: ok cool [17:17] I've also started putting Intrepid SRU candidates at http://people.ubuntu.com/~ogasawara/kernel-sru.html [17:18] but it looks like the ones I've posted so far have patches in the 2.6.27.x stable kernels [17:18] ogasawara: whats the difference between an update and the SRU list your keeping? The release team created the "updates" tag for the post release issues? [17:19] ogasawara: they appear to be very similar if not the same [17:20] pgraner: it was a list created prior to the tag. if they overlap now I'll just start tagging and avoid maintaining a separate list. [17:20] ogasawara: awesome. [17:21] I think rtg's RFC would take care of the 2nd point ogasawara made about things being in the 2.6.27 stable tree [17:21] I haven't seen alot of feedback on it, can everyone respond to it ASAP if not we will take a decision very soon (like next week) [17:22] [ACTION] pgraner to add rtg's RFC to agenda for decision next week [17:22] ACTION received: pgraner to add rtg's RFC to agenda for decision next week [17:22] pgraner: I haven't seen any real dissent, its just carping about the details. [17:24] ogasawara: anything else? [17:24] pgraner: all good here [17:24] [TOPIC] UDS Status & Prep [17:24] New Topic: UDS Status & Prep [17:25] I'll be sending out an email with the list of topics and dependencies to other tracks to the mailing list next week and soliciting input from the community at large. [17:25] Other than that there has not been much due to the intrepid release [17:26] [ACTION] pgraner to send email to list on UDS topics and plan along with solicitation of community input. [17:26] ACTION received: pgraner to send email to list on UDS topics and plan along with solicitation of community input. [17:27] [TOPIC] Open discussion [17:27] New Topic: Open discussion [17:27] Anyone have items they would like to bring up/discuss? [17:28] I've backported 2.6.27.4 into ubuntu-hardy-next. Its currently cooking in the kernel-ppa [17:28] rtg: are you announcing that anywhere besides this meeting? i.e. a CFT type email with the link? [17:29] pgraner: I usually do, but its been awhile since I made an update [17:29] I'll wait until I have a successful build :) [17:29] rtg: that helps [17:30] I want to remind everyone to assign bugs to yourself when you take one. This helps everyone know who to talk to if there are questions etc... [17:30] Anyone have other items? === ubottu changed the topic of #ubuntu-meeting to: Current meeting: Kernel Team Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 28 Oct 19:00: EMEA Membership Board | 29 Oct 17:00: QA Team | 29 Oct 22:00: Platform Team | 30 Oct 12:00: Ubuntu Mobile Team | 30 Oct 13:00: Desktop Team [17:31] Going once... going twice... gone. [17:31] [TOPIC] Roundtable [17:31] New Topic: Roundtable [17:31]