== Agenda == * Review ACTION points from previous meeting * ALL: please check the SRU tracker for 'needs-verification' bugs * http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html * Natty Development * Weekly Updates & Questions for the QA Team (hggdh) * Weekly Updates & Questions for the Kernel Team (smb) * Weekly Updates & Questions for the Documentation Team (sommer) * Weekly Updates & Questions for the Ubuntu Community Team (kim0) * Open Discussion * Announce next meeting date and time * Tuesday, February 1 2011 16:00 UTC == Minutes == ## Use title4 (ie ==== ) for each section of the minutes ## Only topics discussed during the meetings should be put in the minutes. ## Status reporting is done via another channel. ## Start by summarizing all actions taken during the meeting in one section. ## It makes things simpler when reviewing actions in the following meeting. ==== Meeting Actions ==== * '''ACTION''' ''SpamapS'' - Add "verify SRU fixes" to the [ServerTeam/GettingInvolved] wiki page. ==== Other Topics ==== * Reviewing the action for ALL to check for verification-needed bugs, the list has remained managable and the process seems mostly to be working. * Natty Development - Alpha2 is close, some WI's may need to be postponed but nothing specific yet. * Kernel Team (smb) - EC2 t1.micro and i386 fixes for natty kernel are pending - should be in next kernel * SpamapS suggested adding an "Upcoming Events" section to the agenda for Ubuntu Server interested people to talk about and coordinate events they'll be attending. * QA Team (hggdh), Community Team (kim0), and Documentation Team (sommer) representatives were all absent. ==== Agree on next meeting date and time ==== Next meeting will be on Tuesday, February 1 at 16:00 UTC in #ubuntu-meeting. == Log == {{{ [16:02] #startmeeting [16:02] Meeting started at 10:02. The chair is SpamapS. [16:02] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [16:02] [TOPIC] Review ACTION points from previous meeting [16:02] New Topic: Review ACTION points from previous meeting [16:02] ALL: please check the SRU tracker for 'needs-verification' bugs [16:02] How does everyone feel about the needs-verification bugs? [16:03] I see that most are getting turned around quickly [16:04] * SpamapS taps the mic [16:04] this thing on? [16:04] stupid question: process-wise, how does someone mark something verified? just a comment? a tag? [16:05] change the tag [16:05] ie do we need to do something to kick the nxt step in sru process? [16:05] ok [16:05] A comment, the SRU team will accept it by tagging verification-done [16:05] a comment also helps :) [16:05] kthx [16:05] but isn't it that done but someone in QA? [16:05] no, RoAkSoAx - that was dropped [16:05] it was? [16:05] We don't have any QA resources allocated for verifying server SRU's [16:06] The requirement is that its done by somebody other than the developer or the SRU team member [16:06] It used to be the case that QA had to verify it... that was inefficent [16:06] Although, there have been occassions i have -done, my own fixes - which really, really sucks. [16:06] I see. [16:06] yeah, it undermines the whole point of verification [16:07] so anyway, we can certainly verify eachothers' bugs.. [16:07] tho its even better if the reporter can do it, or somebody who is affected [16:08] anyway, the current process doesn't seem to tax people or be too inefficient, so I think we'll just keep it up. I think we can drop this action item. [16:08] +1 [16:09] actually, we should do one thing.. add it here: https://wiki.ubuntu.com/ServerTeam/GettingInvolved [16:09] I'll take that action on myself [16:09] +1 :) [16:09] [ACTION] SpamapS - add SRU verification to ServerTeam GettingInvolved page. [16:09] ACTION received: SpamapS - add SRU verification to ServerTeam GettingInvolved page. [16:10] [TOPIC] Natty Development [16:10] New Topic: Natty Development [16:10] Anybody have anything big to report? [16:10] Seems like our alpha2 chart looks a little behind [16:11] is it time to start postponing things? [16:11] alot of the stuff already has been postponed [16:11] or if you have some little things that can be knocked off do them ;) [16:12] right, thats the dip on Jan 13 .. we're still *way* over scope from where we started, at 60 or so work items [16:12] i am making progress. [16:12] i promise [16:12] * SpamapS cracks the whip [16:12] smoser: back to work! [16:12] I've got a few non-Hudson bits and pieces I intend to complete this week [16:12] i'll get a cloud-init in tonight or tomorrow that will move all IN_PROGRESS on https://blueprints.launchpad.net/ubuntu/+spec/cloud-server-n-cloud-init [16:13] RoAkSoAx, How is the cluster stack spec looking? [16:13] \O/ [16:14] Daviey: well so far I just have one more bug, on which I'm waiting for upstream to give the last word [16:14] smoser, Don't be afraid to scream for help btw. [16:14] RoAkSoAx, Oh great [16:14] Hey did you guys notice the "development over time" bit at the bottom of the burndown page? [16:15] 2011-01-1462 (+10)22 (-37) [16:15] SpamapS, packageselection-server-n-upstart-server-enhancement are the remaining A2 critical? === bjf[afk] is now known as bjf [16:15] THE remaining, rather. [16:16] Daviey: yeah, it'll be done [16:16] win [16:16] I'm not so sure about some of the webscale tech ones .. specifically handlersocket and percona are tricky because they have to build inside the mysql tree [16:16] but I'll postpone those if need be [16:17] but some proposed licensing changes from Oracle in Hudson may hold things up on the Hudson packaging front :-( [16:17] SpamapS: that would be a good idea because its a mess right now [16:17] JamesPage: BLOCKED is good when you're waiting on somebody else. :) [16:18] Anyway, I think we can move on. [16:18] SpamapS: OK [16:18] robbiew: any thoughts btw? [16:18] nope...get'em done [16:18] * SpamapS knows robbiew is probably waiting for a highlight to look up from his angry birds [16:18] or postpone [16:19] heh [16:19] [TOPIC] Weekly Updates & Questions for the QA Team (hggdh) [16:19] New Topic: Weekly Updates & Questions for the QA Team (hggdh) [16:19] postponing to alpha-3 is okay...just don't overload it [16:19] hggdh: you're up [16:20] hggdh, I might ask at some point if you fancy testing a Euca Maverick SRU. :) [16:20] (SRU candidate) [16:20] smb: you ready? We can skip hggdh for now... [16:20] sort of :) [16:21] [TOPIC] Weekly Updates & Questions for the Kernel Team (smb) [16:21] New Topic: Weekly Updates & Questions for the Kernel Team (smb) [16:21] sounds good enough to me, GO [16:21] Ok, so the main achievment is fixing bug 686602 [16:21] Launchpad bug 686602 in Pluck CMS "Admin Menu doesn't show in RTL" [Undecided,New] https://launchpad.net/bugs/686602 [16:21] err [16:21] EWRONGNUM [16:22] Anyways should be the not booting natty on ec2 t1.micro [16:22] Apart from that added two other SRU items for Lucid ec2 [16:23] so i386 t1.micro's work on Natty now? [16:23] Well... it will... next time a kernel is uploaded [16:23] actually amd64 and i386 [16:23] right.. next time the team delivers the bags of candy... [16:23] heh [16:23] nice work on that admin menu, smb [16:24] admin menu? [16:24] yeah what would we do without Pluck CMS [16:24] so, is there a -13 kernel now ? [16:24] smb, it was a bad joke. from your bad bug paste. [16:24] smoser, Currently only my test kernels [16:24] when is -13 due ? [16:24] and will that be in it? [16:24] smoser, Doh! :) [16:25] i'm looking forward to natty booting on i386 (which i believe is in -13), and also t1.micro, which i'm not sure if will make -13. [16:25] soon [16:25] but it will have the fix [16:26] Right, there was the one bug about nx protection (i386) [16:26] Not sure this made it into the current upload but we turn off that option in the next kernel [16:26] oh great. so we're expecting to be able to boot on all instance types. that is huge. [16:26] Upstream seems about to have a real fix for it [16:27] I am following that and will re-test as soon as that is there [16:27] current (-12) kernels do not boot on i386 on ec2. [16:27] you rock, mr smb. [16:27] Until then we just turn the config option off for i386 virtual [16:28] I thanks that is all I had [16:28] ok, anybody have more questions? [16:28] I don't see sommer or kim0 [16:28] :( [16:28] hggdh: ping? [16:29] Ok, well that brings us to... [16:29] [TOPIC] Open Discussion [16:29] New Topic: Open Discussion [16:30] Nothing here [16:30] I was thinking of adding one thing to the meeting standard stuff.. [16:30] upcoming events [16:30] Dustin will be at Strata next week [16:30] Several other team members will be at events all over the place.. [16:30] would be good to talk about them here [16:31] So, I'll add it to the meeting agenda for next week. [16:31] Anything else? [16:31] I had one actually [16:31] does anybody else notice that natty server boots to a blank screen instead of getty? [16:31] bring it on [16:32] i haven't. i HAVE noticed tha i get the same qeustions 3 ties during install [16:32] I haven't tried an ISO more recent than 10 days ago.. but the VMs I've installed from that ISO never boot to getty [16:32] SpamapS: what graphics card are you using? [16:32] blank screen on a serial console install? [16:32] robbiew: kvm [16:32] vms...nevemind [16:32] :) [16:32] SpamapS: well mine did until I tried today but they now seem to be OK [16:32] who controls the installer? [16:33] i tried one yesterday and it booted fine [16:33] console on tty1 [16:33] but i did get repeated questions about location/kbd [16:33] Ok.. probably got fixed in the recent plymouth stuff [16:33] hallyn: cjwatson typically does server installer stuff [16:33] have you tried doing alt-f2? [16:33] ok, maybe i'll talk to him about it next week [16:33] (i know he's still hip-deep in plymouth :) [16:33] [TOPIC] Announce next meeting date and time [16:33] New Topic: Announce next meeting date and time [16:34] Tuesday, February 1 2011 16:00 UTC [16:34] That is all! Thanks everyone [16:34] #endmeeting [16:34] Meeting finished at 10:34. }}}