[15:00] <kyleN> SU invites sent
[16:00] <Daviey> hey o/
[16:00] <Daviey> zul: Looks like you ar ein the hot seat?
[16:00] <jamespage> o/
[16:00] <smoser> o/
[16:00] <arosales> hello
[16:00] <zul> crappers
[16:01] <smb> \o
[16:01] <Daviey> zul: is that Canadian for "Woot?"
[16:01] <zul> Daviey:  its a west coast term
[16:01] <zul> i guess we should start
[16:01] <zul> #startmeeting
[16:01] <meetingology> Meeting started Tue Feb 12 16:01:46 2013 UTC.  The chair is zul. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:01] <meetingology> 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
[16:02] <zul> #topic Review ACTION points from previous meeting
[16:02] <zul> so was there any action points from the previous meeting?
[16:02]  * zul is a little unprepared
[16:02] <jamespage> no
[16:02] <zul> sweet
[16:02] <smoser> well, there was one for me.
[16:02] <smoser> to contact release team about alpha2
[16:02] <smoser> which i have done.
[16:03] <zul> smoser: sweet!
[16:03] <jamespage> smoser: in which case I forgot to record it sorry
[16:03] <zul> so next
[16:03] <zul> #topic Raring Development
[16:03] <Daviey> smoser: do you want to drive this?
[16:04] <smoser> yeah
[16:04] <smoser> ok.
[16:04] <smoser> http://reports.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server
[16:05] <smoser> that list looks reasonably well handled.
[16:05] <smoser> so, move on
[16:05] <smoser> alpha2 is thursday.
[16:06] <smoser> i believe that what we've agreed to do is to just tag cloud-images as alpha2
[16:06] <smoser> that will largely involve utlemming and i.
[16:06] <Daviey> (and a call for testing for ISO.)
[16:06] <smoser> utlemming you can make sure that our candiddate (daily) builds have what is necessary?
[16:06] <smoser> (yes, and call for testing ISO)
[16:06] <smoser> and then , get the ISO tracker populated and tests recorded and the like
[16:07] <smoser> (i can help utlemming on that)
[16:07] <utlemming> smoser: yup. We're ready in the build infrastruture department
[16:07] <smoser> we should send out a call for testing.
[16:07] <smoser> any one want to volunteer for that?
[16:07] <utlemming> smoser: and ISO tracking integration has been added already
[16:08] <Daviey> smoser: i'll do that.
[16:08] <smoser> ok. so just as long as we get stuff over there, and let the release team know the amis we want populated, i'm good with that.
[16:08] <smoser> thank you Daviey
[16:08] <smoser> #ACTION Daviey send request for testing
[16:08] <meetingology> ACTION: Daviey send request for testing
[16:08] <Daviey> roaksoax: How is MAAS looking in raring?
[16:10] <smoser> ok, we'll skip that repsonse maybe for general discussion section roaksoax
[16:10] <smoser> so, we're at alpha-2 in the cycle.
[16:10] <smoser> feature freeze is not too far off (March 7)
[16:10] <jamespage> sorry - I was distracting roaksoax elsewhere
[16:10] <smoser> be aware of that in your work.
[16:11] <smoser> #subtopic blueprints
[16:11] <smoser> http://status.ubuntu.com/ubuntu-raring/group/topic-raring-servercloud-overview.html
[16:12] <roaksoax> Daviey: its looking good. Now with SRU approval we should be getting things done pretty quickly
[16:12] <smoser> red are servercloud-r-openstack-ha, servercloud-r-openstack-grizzly, servercloud-r-image-access (smoser), servercloud-r-cloudarchive, servercloud-r-openstack-ubuntu-images
[16:12] <smoser> and servercloud-r-apt-improvements.
[16:12] <roaksoax> Daviey: so that will enable me to upload trunk to raring (since MAAS in raring is what is to be SRU'd)
[16:12] <smoser> so, pelease, if you are in charge of one of those , please make some effort to get it into shape
[16:12] <smoser> or to raise the fact that it might not be in good shape.
[16:13] <smoser> anything else for this topic ?
[16:13] <Daviey> -apt-improvements i fear will be postponed
[16:13] <Daviey> rbasak: ^?
[16:13] <smoser> i fear that indefinitely :-(
[16:14] <hallyn> fwiw, user namespaces will not be sufficiently enabled in the raring kernel.  we will have a kernel in a ppa for ~ubuntu-lxc for raring, and r+1 will have fully enabled usernamespaces.
[16:14] <hallyn> (this relates to a few items in the lxc blueprint)
[16:14] <Daviey> hallyn: :(
[16:14] <hallyn> oh it's ok, r+1 is so gonna rock
[16:14] <Daviey> \o/
[16:14] <hallyn> fully unprivileged creation and use of containers
[16:15] <zul> as long as the next lts rocks
[16:15] <hallyn> ooooh it will
[16:15] <zul> anything else?
[16:15] <smoser> hallyn, "fully unprivileged creation and use of containers" sounds crazy awesome.
[16:15] <rbasak> I hope to have the apt code done for feature freeze, but I'm not sure it'll go into raring in time for review. But I'm hoping that it'll land when S opens at the latest
[16:16] <smoser> rbasak, well, please remember that shoving it into R to be optionally enabled is quite preferable
[16:16] <jamespage> zul: re the tracking report; I checked the package list
[16:16] <rbasak> smoser: ack
[16:16] <smoser> so that it makes it easier for people to test.
[16:16] <jamespage> it looks OK - I'll ping round an email with how to make stuff appear on it.
[16:16] <smoser> and doesn't hurt anything.
[16:16] <rbasak> The catch is the desire for ABI compatibility in Debian
[16:16] <zul> which package list?
[16:16] <rbasak> Since I need to modify libapt slightly
[16:17] <jamespage> zul: the list of packages that is maintained for the release tracking report (packages -> teams)
[16:17] <zul> ah
[16:17] <jamespage> (that is going to change to subs)
[16:18] <zul> so i guess its time for a topic change
[16:18] <zul> #topic Ubuntu Server Team Events
[16:18] <zul> any upcoming events?
[16:19] <zul> ODS and UDS will be here sooner to bite you on the bum
[16:19] <Daviey> Yes, moving on :)
[16:19] <arosales> scale11x upcoming
[16:19] <arosales> MongoDB Austin this Friday :-)
[16:19] <Daviey> be there or be relational
[16:19] <zul> hah
[16:19]  * jamespage will be relational then
[16:20] <arosales> I'll be there giving a Juju talk around Juan's sharding blog
[16:20] <jamespage> arosales: nice one
[16:20] <Daviey> Oh nice!
[16:20] <zul> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:20] <zul> hi hggdh you here?
[16:21] <zul> if not
[16:21] <zul> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:21] <smb> More or less was busy with Xen (two issues in Precise, security updates in its package, preparing related security updates in the kernel). There was also some bug smoser had for me but I believe that was something I was nothing I could help further and promptly forgot what that was... :/ Oh, autoloading of some  special net hw modules. I believe the net part has been at least added to some udebs (Precise?) So are there other questions?
[16:21] <zul> hi smb are you here?
[16:21] <smb> ..
[16:21] <smb> zul, yes
[16:22] <zul> smb:  silly cut and paste
[16:22] <smb> zul, Nah, prewrite and press enter. :)
[16:22] <zul> uh huh :)
[16:22] <smoser> yes, smb helped me with bug 1115710 and (related)_ bug 1015339.
[16:22] <zul> anything else for smb and his prewrite awesomeoness?
[16:23] <zul> ok then
[16:23] <zul> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:23] <zul> i know rbasak is around
[16:24] <zul> or his evil twin
[16:24] <zul> who is french
[16:24] <zul> rbasak: any update?
[16:24] <rbasak> Sorry
[16:25] <rbasak> Nothing new to report. Any questions for me?
[16:25] <zul> if not
[16:26] <zul> #topic Open Discussion
[16:26] <zul> so anyone else has something on the agenda?
[16:26] <pmatulis> yes
[16:26] <zul> pmatulis: ?
[16:27] <pmatulis> we need to improve the ubuntu server guide.  seems the way we're doing it now doesn't work
[16:27] <pmatulis> i'm afraid it will become obsolete in a few cycles if things don't improve
[16:28] <zul> pmatulis: why not put out a call to volunteers again on the ubuntu-server mailing list
[16:29] <pmatulis> zul: i did, last week, no one responded
[16:29] <rbasak> pmatulis: what do you propose?
[16:29] <pmatulis> rbasak: i've tried to create ways to focus on the guide
[16:30] <pmatulis> but it doesn't seem to be bearing any fruit
[16:31] <pmatulis> today i created a special team with an associated mailing list.  which i hope to use to awaken prior contributors every cycle
[16:31] <pmatulis> fyi, https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/UbuntuServerGuide
[16:32] <hallyn> test team has worked hard to try and force test additions corresponding to each (UDS) feature item and each SRU item, perhaps we can do something analogous where we collect server guide updates in response to each?
[16:32] <hallyn> don't require a server guide update for each, just collect items,
[16:32] <hallyn> which then a team can go over (and contact the item author if needed)

[16:34] <hallyn> i'd say such an undertaking could stand to have a UDS discussion
[16:34] <jamespage> indeed
[16:34] <pmatulis> hallyn: that's an idea, link guide contributions to UDS discussions
[16:34] <hallyn> (in the meantime, a simple stern "make sure you update server guide for anything you've been working on")
[16:34] <hallyn> pmatulis: even put them in the blueprints,
[16:34] <pmatulis> right
[16:34] <hallyn> next to the release notes maybe.
[16:35] <rbasak> Perhaps we should have a standard "upgrade server guide" in every blueprint where it makes sense
[16:35] <rbasak> update server guide that is
[16:35] <jamespage> I think making it a milestoned work item makes alot of sense
[16:35] <jamespage> then you won't get i***ts like me updating stuff a week before release cause its wrong
[16:36] <jamespage> OK _ I'll take an action to add something to the blueprint template - basically a check to see if docs need updating
[16:36] <hallyn> where would it fit though?  I don't think that
[16:37] <hallyn> having one week where we try to remember the last six months' worth of changes works
[16:37] <hallyn> hm yeah, that's a good start
[16:37] <jamespage> well a milestone would indicate the point at which document updates must have been made by
[16:37] <jamespage> not when you actually do the,
[16:37] <jamespage> :-)
[16:37] <jamespage> pmatulis: I'm right in saying there is a cutoff?
[16:37] <hallyn> haha
[16:38] <jamespage> zul: care to action me todo that?
[16:38] <pmatulis> jamespage: yes, there is actually a 'string freeze'
[16:38] <zul> jamespage:  sure
[16:38] <jamespage> thats the one
[16:38] <zul> #action jamespage to milesone documentation updates
[16:38] <meetingology> ACTION: jamespage to milesone documentation updates
[16:39] <zul> anything else?
[16:40] <zul> #topic Announce next meeting date, time and chair
[16:40] <zul> next week, same time, same place and someone else will be the chair
[16:40] <zul> whee!
[16:40] <zul> thanks for coming
[16:41] <zul> #endmeeting
[16:41] <meetingology> Meeting ended Tue Feb 12 16:41:00 2013 UTC.
[16:41] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-12-16.01.moin.txt
[16:41] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-12-16.01.html
[16:41] <jamespage> thanks zul
[16:41] <roaksoax> o/
[16:41] <arosales> zul thanks for chairing
[16:42] <Daviey> thanks zul o/
[17:00] <jsalisbury> #startmeeting
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <meetingology> Meeting started Tue Feb 12 17:00:15 2013 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:00] <meetingology> 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] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/raring
[17:00] <jsalisbury> # Meeting Etiquette
[17:00] <jsalisbury> #
[17:00] <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
[17:00] <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
[17:00] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:00] <ppisati> o/
[17:00] <sconklin> o/
[17:00] <herton> o/
[17:00] <henrix> o/
[17:00] <sforshee> o/
[17:01] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> R/master: still working on last week's "BUG: scheduling while atomic" bug in
[17:01] <ppisati> the ipv6 stack - nothing new to report.
[17:01] <ppisati> ..
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> ..
[17:01] <jsalisbury> I will post updates from ogasawara
[17:01] <jsalisbury> TOPIC] Milestone Targeted Work Items (ogasawara)
[17:01] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:01] <jsalisbury> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
[17:01] <jsalisbury> || apw         || hardware-r-kernel-config-review       || 6 work items ||
[17:01] <jsalisbury> ||             || hardware-r-delta-review               || 3 work items ||
[17:01] <jsalisbury> || ppisati     || hardware-r-kernel-config-review       || 1 work item  ||
[17:01] <jsalisbury> || rtg         || hardware-r-delta-review               || 1 work item  ||
[17:01] <jsalisbury> || smb         || hardware-r-kernel-misc                || 2 work items ||
[17:02] <jsalisbury> ..
[17:02] <jsalisbury> [TOPIC] Status: Raring Development Kernel (ogasawara)
[17:02] <jsalisbury> We have rebased the Raring kernel to the latest v3.8-rc7 upstream
[17:02] <jsalisbury> kernel and uploaded.  Perf has also been re-enabled with the latest
[17:02] <jsalisbury> upload.
[17:02] <jsalisbury> Important upcoming dates:
[17:02] <jsalisbury>  * Raring:
[17:02] <jsalisbury>   * Mon Feb 18 - 13.04 Month 4 Milestone (~1 week)
[17:02] <jsalisbury>  * Precise:
[17:02] <jsalisbury>   * Thu Feb 14 - 12.04.2 Release (2 days)
[17:02] <jsalisbury> ..
[17:02] <jsalisbury> [TOPIC] Status: CVE's (henrix)
[17:02] <henrix> Currently we have 29 CVEs on our radar, with 1 CVE added and 3 CVEs retired this week.
[17:02] <henrix> See the CVE matrix for the current list:
[17:02] <henrix> [LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:02] <henrix> Overall the backlog has decreased slightly this week:
[17:02] <henrix> [LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt
[17:02] <henrix> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:02] <henrix> ..
[17:03] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Quantal/Precise/Oneiric/Lucid/Hardy (bjf/herton/henrix)
[17:03] <henrix> Here is the status for the main kernels, until today (February 12):
[17:03] <henrix>  * Hardy - Nothing in this cycle
[17:03] <henrix>  * Lucid - In Testing; 1 CVE; (2 commits)
[17:03] <henrix>  * Oneiric - In Verification; 3 CVEs; 4 upstream stable release(s); (154 commits)
[17:03] <henrix>  * Precise - In Verification; 0 CVEs; 2 upstream stable release(s); (222 commits)
[17:03] <henrix>  * Quantal - In Verification; 0 CVEs; 2 upstream stable release(s); (375 commits)
[17:03] <henrix> Current opened tracking bugs details:
[17:03] <henrix>  * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:03] <henrix> For SRUs, SRU report is a good source of information:
[17:03] <henrix>  * http://people.canonical.com/~kernel/reports/sru-report.html
[17:03] <henrix> Future stable cadence cycles:
[17:03] <henrix>  * https://wiki.ubuntu.com/RaringRingtail/ReleaseInterlock
[17:03] <henrix> ..
[17:04] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:04] <jsalisbury> Thanks everyone
[17:04] <jsalisbury> #endmeeting
[17:04] <meetingology> Meeting ended Tue Feb 12 17:04:31 2013 UTC.
[17:04] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-12-17.00.moin.txt
[17:04] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-12-17.00.html