[15:56] <lynxman> o/
[16:00] <hallyn> \o
[16:00] <smb> \o
[16:00] <utlemming> \o
[16:00] <jamespage> o/
[16:00] <jamespage> I'm in the chair today
[16:00] <Daviey> o/
[16:00] <Daviey> (Note, i will be largely absent this time - is someone else happy to drive the dev review?)
[16:01] <jamespage> #startmeeting
[16:01] <meetingology> Meeting started Tue Jan 31 16:01:30 2012 UTC.  The chair is jamespage. 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:01] <jamespage> #topic Review ACTION points from previous meeting
[16:02] <Daviey> None.
[16:02] <jamespage> \o/
[16:02] <jamespage> #topic Precise Development
[16:02]  * jamespage passes the baton to Daviey
[16:03] <jamespage> (who hopefully is prepared)
[16:03] <Daviey> 16:00 < Daviey> (Note, i will be largely absent this time - is someone else happy to drive the dev  review?)
[16:04] <jamespage> lol
[16:04] <hallyn> Daviey: why don't you hand jamespae the url with the concerning bugs
[16:04] <hallyn> then i'm sure jamespage will be happy to drive
[16:04] <Daviey> http://status.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html :)
[16:04] <jamespage> http://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:04] <Daviey> good thinking that man!
[16:04] <jamespage> So whilst we review this we need to consider that Alpha 2 is due on the 2nd Feb and Beta 1 on the 16th
[16:05] <jamespage> ticktockticktock
[16:06] <jamespage> do we really just run through these?
[16:06] <jamespage> OK so bug 883988
[16:06] <zul> its on the upstream radar
[16:06] <jamespage> zul: when is a fix expected?
[16:07] <zul> jamespage: ill bug jaypipes
[16:07] <jamespage> nice one
[16:07] <jamespage> bug 893926
[16:08] <jamespage> Guess that is still in progress
[16:08] <jamespage> bug 911812
[16:09] <jamespage> not sure if roaksoax is here...
[16:09] <adam_g> jamespage: i spoke to andres about that friday. i think that is fixed released in a number of recent releases, and should propose to lucid.
[16:09] <adam_g> not sure what he's found out, though
[16:09] <jamespage> smoser, bug 913009
[16:09] <jamespage> progress?
[16:10] <smoser> hm..
[16:10] <smoser> no, no progress.
[16:10] <jamespage> adam_g: I see bug 916992 is fixed - nice one!
[16:11] <jamespage> SpamapS, bug 914392
[16:11] <jamespage> any eta from the juju team on when that will be resolved?
[16:12] <smoser> branch is in merge queue i beleve
[16:12] <jamespage> great
[16:12] <SpamapS> jamespage: thats got a fix upstream in a branch, ready for testing
[16:12] <jamespage> adam_g: bug 922232 - I see that there is a fixed proposed upstream
[16:13] <Ursinha> what's the importance of this bug?
[16:13] <adam_g> jamespage: yeah, didnt realize a QA bot had tagged it failing a unit test, pushed a second rev. last night.
[16:13] <adam_g> Ursinha: the tgt bug? high, i'd say
[16:13] <Ursinha> adam_g, may I set it?
[16:14] <adam_g> Ursinha: sure.
[16:14] <Ursinha> oh, I can't :)
[16:14] <adam_g> i thought i did for the ubuntu task
[16:14] <jamespage> adam_g: you did - thats fine
[16:14] <jamespage> we can't set the upstream task importance which is fair enough
[16:15] <Ursinha> that's fine
[16:15] <Ursinha> so the downstream is in progress
[16:15] <jamespage> Ok; bug 923681
[16:16] <jamespage> interesting that the automated testing has not picked that up because it uses tasksel (albeit through preseeds).
[16:17] <jamespage> bug 875262;
[16:18] <jamespage> currently assigned to koolhead17
[16:18] <jamespage> ..
[16:18] <SpamapS> he's been working on it
[16:18] <SpamapS> I've been helping him when I can
[16:19] <jamespage> SpamapS, think that will make alpha-2?
[16:20] <Daviey> SpamapS: Can you clarify what is holding it up?
[16:21] <jamespage> OK; lets come back to that if/when
[16:21] <jamespage> bug 890362
[16:22] <jamespage> adam_g, zul: any thoughts on this one? It would nice to land something for alpha-2
[16:22] <zul> james: yeah its on my todo list
[16:22] <jamespage> great
[16:23] <SpamapS> Sorry I had something here distracting me
[16:23] <jamespage> np
[16:23] <jamespage> any feedback?
[16:23] <SpamapS> Whats holding it up is that koolhead17 is new to packaging, and needs guidance, and is in a very incompatible time zone with me.
[16:23] <arosales> zul, do you think 890362 will make alpha 2?
[16:24] <SpamapS> We also need to merge PHP 5.3.9 .. but thats not going to make alpha-2
[16:24] <jamespage> SpamapS, ack - I think Daviey and I are more compatible timewise...
[16:24] <zul> arosales: probably i was going to do some work on it this afternoon
[16:24] <jamespage> so feel free to point him in our direction
[16:24] <arosales> zul: ok, thanks.
[16:25] <jamespage> roaksoax has been working on bug 898840
[16:26] <SpamapS> jamespage: he's in India
[16:26] <SpamapS> jamespage: but I think he can work on this stuff only after working hours, which should fall into your TZ
[16:26] <jamespage> great
[16:26] <jamespage> I thought you mean't roaksoax for a minute then
[16:27] <jamespage> I guess bug 898840 won't make alpha-2
[16:27] <jamespage> I believe bug 904681 is now fixed
[16:28] <jamespage> test when green today in jenkins
[16:28] <jamespage> https://jenkins.qa.ubuntu.com/view/Precise%20ISO%20Testing%20Dashboard/view/Daily/job/precise-server-amd64_minimal-virtual/79/
[16:28] <hallyn> that'd be grrreat
[16:28] <jamespage> wonders what we actually did to fix it....
[16:29] <jamespage> bug 906654 is not currently milestone targetted
[16:29] <adam_g> jamespage: i think that will eventually be marked invalid, the openstackx library is to be deprecated and removed from openstack entirely this cycle
[16:29] <jamespage> adam_g, zul - any thoughts on this and when/if it might happen
[16:30] <jamespage> adam_g: good
[16:30] <jamespage> pls can you comment to that effect.
[16:30] <zul> jamespage: i think openstackx i sbeing dropped so i need to doubleechk
[16:30] <adam_g> jamespage: happening soon if not already
[16:30] <jamespage> adam_g, zul: same with bug 907197
[16:31] <zul> jamespage: still havent reproduced it
[16:31] <jamespage> zul: ack
[16:31] <jamespage> rbasak, around? care to update on bug 879666
[16:32] <rbasak> I will update the patch for oneiric-updates
[16:32] <rbasak> but the patch isn't present in precise atm
[16:32] <rbasak> so can't complete the SRU justification
[16:32] <rbasak> Was speaking to Daviey about this earlier
[16:32] <rbasak> I think he wants the patch taken into precise too
[16:32] <jamespage> OK
[16:33] <Daviey> zul: Please re-introduce that patch to precise.
[16:33] <zul> ack
[16:33] <jamespage> lynxman was working on bug 916489
[16:33] <jamespage> which needs a new upstream release of ipxe
[16:33] <jamespage> but I know he's short on time for this now
[16:34] <lynxman> jamespage: unfortunately my management requires my attention elsewhere, new release is almost ready
[16:34] <jamespage> Daviey: still key that makes alpha-2?
[16:34] <lynxman> jamespage: I reckon tops weekend will be here
[16:35] <Daviey> jamespage: no, it can wait
[16:35] <Daviey> I thought we were just waiting on the version string resolution?
[16:36] <jamespage> bug 833499
[16:36] <jamespage> looks like we have a workaround for the moment
[16:37] <jamespage> zul, smoser: is that getting any upstream focus in esses?
[16:37] <smoser> probably not.
[16:37] <zul> still on my neverending todo list
[16:38] <jamespage> zul: is bug 901881 there as well?
[16:39] <zul> jamespage: keystone is in transition right now so that is in limbo kind of
[16:39] <jamespage> right - I understand
[16:39] <jamespage> so not in the short term then
[16:39] <zul> no...
[16:39] <jamespage> rbasak, hows OpenMPI looking (bug 889644)
[16:39] <rbasak> it's built in a ppa now
[16:40] <rbasak> next step is to try building its dependencies against it
[16:40] <rbasak> debian armel ftbfs, but ubuntu is ok
[16:40] <Daviey> neat
[16:40] <jamespage> rbasak, likely to land for beta-1?
[16:41] <Daviey> rbasak: Depends on the testing of rdepends, rebuild right?
[16:41] <rbasak> yep
[16:42] <rbasak> if it works then we can get it in the archive straight away
[16:42] <rbasak> Holdups will depend on any bugs
[16:42] <jamespage> OK bug 907206
[16:42] <jamespage> nearly there how
[16:42] <zul> will be uploaded friday
[16:42] <jamespage> zul: sweet
[16:43] <jamespage> bug 887186 and bug 891977 for roaksoax; hopefully he's on those
[16:43] <Daviey> I merged that a few days ago
[16:43] <jamespage> adam_g: bug 923817
[16:44] <adam_g> jamespage: fix proposed, waiting on a +1 our openstack packaging
[16:44] <jamespage> readhy for review I see - friday zul?
[16:44] <zul> yeah
[16:44] <jamespage> nice
[16:45] <jamespage> So I won;t go through the other teams list; but we probably what to add the MIR's for juju to the list for tracking in precise
[16:45] <jamespage> #action jamespage to get juju MIR's added to server precise release tracking
[16:45] <meetingology> ACTION: jamespage to get juju MIR's added to server precise release tracking
[16:45] <jamespage> #topic Ubuntu Server Team Events
[16:46] <jamespage> rbasak, Daviey and I at FOSDEM this weekend
[16:46] <Daviey> Right!
[16:46] <jamespage> \o/
[16:46] <jamespage> any other events?
[16:46] <jamespage> nope
[16:46] <jamespage> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:46] <jamespage> hggdh: around?
[16:46] <hggdh> yep
[16:47] <SpamapS> WAIT
[16:47] <SpamapS> events
[16:47]  * jamespage rewinds the tape
[16:47] <SpamapS> https://juju.ubuntu.com/Events
[16:47] <jamespage> #link https://juju.ubuntu.com/Events
[16:47] <SpamapS> Tomorrow, Mark Mims and David Medberry will be at MongoDB Boulder to talk about juju
[16:48] <SpamapS> And at the end of the month, juju will be at Strata
[16:48] <SpamapS> that is all
[16:48] <jamespage> ta
[16:48] <jamespage> hggdh?
[16:48] <hggdh> Alpha is in, folks. As much test as possible will be appreciated. We are looking good, though, so far :-)
[16:48] <hggdh> and this is it, right now
[16:48] <hggdh> ..
[16:48] <jamespage> I noted that the ISO testing dashboard was looking sweet for server :-)
[16:48] <jamespage> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:48] <smb> Random list of things I was involved at least as part of the problem, not
[16:48] <smb> necessarily, yet, part of the solution:
[16:48] <smb> * bug 923685
[16:48] <smb> * bug 922754
[16:48] <hggdh> yes... isn't life good?
[16:48] <smb> * bug 824089 and bug 913760
[16:48] <smb> * bug 922137
[16:48] <smb> * bug 922486
[16:48] <smb> * bug 921816
[16:49] <smb> Over to smoser for more... ;)
[16:49] <Daviey> jamespage: (MIR bugs added.)
[16:49] <jamespage> Daviey: ta
[16:49] <smb> ..
[16:49] <smoser> i dont have anything specific for smb at the moment.
[16:49] <Daviey> bug 922754 is one for jodh i think
[16:50] <smb> Daviey, He is on it
[16:50] <jamespage> I'm sure he will love that :-)
[16:50] <jamespage> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:50] <jamespage> how is arm server looking rbasak
[16:50] <Daviey> I thought it was fixed now TBH
[16:50] <roaksoax> smb where u abl
[16:50] <rbasak> The kernel is fixed now
[16:50] <jamespage> \o/
[16:50] <rbasak> juju is working in a local environment too!
[16:50] <jamespage> (I can re-install again!)
[16:50] <SpamapS> /o/
[16:50] <rbasak> I'm not sure that the installer is carrying the latest kernel
[16:50] <smb> roaksoax, abl 2 do what? :)
[16:51] <rbasak> But you can use the latest kernel image and the installer will work
[16:51] <Daviey> rocking!
[16:51] <jamespage> any questions for robbiew?
[16:51] <robbiew> hey
[16:51] <jamespage> sorry that should be rbasak
[16:51] <jamespage> doh!
[16:51] <robbiew> lol
[16:52] <roaksoax> smb where able to resolvr yhe orchestra/squid issue u were having?
[16:52] <jamespage> nope - great
[16:52] <jamespage> #topic Open Discussion and Community
[16:53] <SpamapS> Wait, "and Community" ?
[16:53] <jamespage> Anyone got anything they would like to discuss?
[16:53] <SpamapS> did we miss the point of removing the "Community" section?
[16:53] <robbiew> FeatureFreeze is Feb16th :)
[16:53] <SpamapS> *the entire meeting is about the community*
[16:53] <robbiew> justsayn
[16:53] <smb> roaksoax, currently running mostly without proxy enabled. as I try to use apt-cacher-ng as proxy which seems to be flakey with precise. but the complete strange fails seem to have disappeared
[16:53] <robbiew> SpamapS: I expect we'll need an FFS for juju stuff
[16:53] <robbiew> ...and maas <- Daviey
[16:54] <Daviey> robbiew: I have lots of FFF's
[16:54] <jamespage> SpamapS, you are quite correct
[16:54] <Daviey> FFS*
[16:54] <robbiew> \o/
[16:54] <roaksoax> smb ok ;) then it was cache issue or even archive
[16:54] <jamespage> #topic Open Discussion
[16:54] <SpamapS> jamespage: ty.. lets fix the agenda for the next meeting too
[16:54] <jamespage> SpamapS, agreed - will do that when I write the minutes
[16:55]  * jamespage pokes Daviey
[16:55] <Daviey> right!
[16:55] <SpamapS> I promise I'll do an extra 2 or 3 turns as moderator once daylight savings time returns
[16:55] <jamespage> lol
[16:56] <jamespage> so if thats all folks...
[16:56] <jamespage> #Announce next meeting date and time
[16:56] <jamespage> 1600UTC on 7th Feb
[16:56] <jamespage> until next week
[16:56] <jamespage> #endmeeting
[16:56] <meetingology> Meeting ended Tue Jan 31 16:56:52 2012 UTC.
[16:56] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-01-31-16.01.moin.txt
[16:56] <SpamapS> jamespage: thanks!
[16:56] <Ursinha> thanks jamespage
[16:57] <arosales> thanks jamespage
[16:59] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[16:59] <apw> o/
[16:59] <sforshee> o/
[16:59] <cking> o/
[16:59] <tgardner> o/
[16:59] <bjf> o/
[16:59] <herton> o/
[16:59] <arges> 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 Jan 31 17:00:13 2012 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/Precise
[17:00] <smb> \o
[17:00] <jsalisbury> # Meeting Etiquette
[17:00] <jsalisbury> #
[17:00] <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
[17:00] <ppisati> o/
[17:00] <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
[17:00] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:00] <ppisati> P/omap4: a new kernel version (1405.7) was released, with improved PM support and fixes for the usb subsystem (CMA revert).
[17:00] <ppisati> P/master: problems with mmc were due to twl4030's GPIO lines being inactive at boot time since support was factored out in a kernel module; recompiling it in the main kernel made omap3 boards boot off the mmc again (12.20).
[17:01] <ppisati> SRU: new kernels were released for every supported arch/release.
[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> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:02] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-precise/canonical-kernel-distro-team-precise-alpha-2.html
[17:02] <ogasawara> I've pushed out any open work items from Alpha-2 to Beta-1.
[17:02] <ogasawara> Additionally, some work items have come to my attention but I'm unaware
[17:02] <ogasawara> of anyone from our team actually working on them:
[17:02] <ogasawara> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-ceph
[17:02] <ogasawara> [canonical-kernel-team] investigate large xattr support patch from Ted T'so in ext4: TODO
[17:02] <ogasawara> [canonical-kernel-team] potentially help push large xattr support to ext4: TODO
[17:02] <ogasawara> Did anyone attend that session at UDS and commit us to those work items?
[17:02] <ogasawara> I suspect these may just get postponed.
[17:02] <apw> those were for the cluster filesystem thing
[17:03] <apw> for use in openstack iirc
[17:03] <apw> ..
[17:03] <ogasawara> k, i'll follow up and see if I can find out more.
[17:03] <ogasawara> Also, https://blueprints.launchpad.net/ubuntu/+spec/ubuntu-arm-p-optional-initrd
[17:03] <ogasawara> [canonical-kernel-team] provide a kernel with uuid support in the internal initrd for measuring
[17:03] <ogasawara> I vaguely recall there were discussions regarding this work item at the
[17:03] <ogasawara> rally, but I'm unaware of what the outcome was?
[17:05] <tgardner> oagdunno where that one is. I think ogra was gonna do some testing
[17:05] <tgardner> ogasawara, ^
[17:05] <ogasawara> ack
[17:05] <ogasawara> ..
[17:05] <tgardner> punted...
[17:05] <ogra_> tgardner, well, the foundations WIs were all postponed/blocked yesterday
[17:06] <ogasawara> ogra_: blocked on the above work item?
[17:06] <ogra_> i can indeed do a test of with/without initrd, but that wont tell anything about with/with minimal initrd in kernel
[17:06] <ogra_> ogasawara, yes
[17:06] <ogra_> but i cant speak for slangasek :)
[17:06] <tgardner> ogra_, but don't we have an option to generate a minimal initrd now ?
[17:07] <ogra_> he set his items to blocked
[17:07] <ogra_> wrt my item i can easily provide you with data tomorrow if that helps anyone
[17:07] <tgardner> ogra_, I think those would be interesting numbers.
[17:08] <ogra_> tgardner, i dont think so ... when i said minimal i meant the in-kernel initrd just containing teh blkid command as we had discussed
[17:08] <ogra_> though i think slangasek would even like to see that done in-kernel with a patch (which i think you already said is to intrusive)
[17:09] <apw> ogra_, probabally we should discuss a plan for this feature offline, we are clearly confused on who is doing what when in which order
[17:09] <ogra_> apw, k
[17:09] <slangasek> tgardner: FSVO "minimal" that always includes udev and sundry other utilities
[17:09] <ogra_> slangasek, not necessarily, thats why we have devtmpfs, no ?
[17:09] <tgardner> slangasek, I guess I was referring to the "tailored" initrd so taht we could see if there was _any_ time differences
[17:10] <slangasek> there is no support for generating any genuinely minimal initramfs out of initramfs-tools
[17:10] <ogra_> right, it will always be bloated and at least contain both libc's
[17:12] <tgardner> ..
[17:12] <apw> we'll discuss it offline ..
[17:12] <jsalisbury> Everyone OK with moving on?
[17:12] <ogra_> ..
[17:12] <jsalisbury> [TOPIC] Blueprint: hardware-p-kernel-power-management (cking)
[17:12] <cking> nothing to report this week
[17:12] <cking> ..
[17:12] <jsalisbury> [TOPIC] Status: Precise Development Kernel (ogasawara)
[17:12] <ogasawara> Last week we rebased to v3.2.2 and uploaded.  There is a potential
[17:12] <ogasawara> regression in v3.2.2 that I'm concerned about, bug 923512.  jsalisbury
[17:12] <ogasawara> is working with the bug reporters and has a test kernel with the
[17:12] <ogasawara> offending patch reverted.  If anyone else has hw which uses the ath9k
[17:12] <ogasawara> driver, it would be nice if you could test.  I'd consider this would
[17:12] <ogasawara> warrent an upload to fix before the milestone which is in 2 days, Thurs
[17:12] <ogasawara> Feb 2.  This means we'd likely have to upload by end of day today.
[17:12] <ogasawara> ..
[17:13] <jsalisbury> [TOPIC] Status: CVE's (apw)
[17:14] <apw>  
[17:14] <apw> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:14] <apw>  
[17:14] <apw> Currently open CVEs for each supported branch:
[17:14] <apw>  
[17:14] <apw> || Package                                  || Open      || Defd ||
[17:14] <apw> ||                                          ||           ||      ||
[17:14] <apw> || linux Hardy                              ||   20 (+3) ||    8 ||
[17:14] <apw> || linux Lucid                              ||   14 (+2) ||    5 ||
[17:14] <apw> || linux Maverick                           ||   14 (+3) ||    5 ||
[17:14] <apw> || linux Natty                              ||   13 (+3) ||    5 ||
[17:14] <apw> || linux Oneiric                            ||   10 (+1) ||    5 ||
[17:14] <apw> || linux Precise                            ||    7      ||    5 ||
[17:14] <apw> || linux-ec2 Lucid                          ||   14 (+2) ||    5 ||
[17:14] <apw> || linux-fsl-imx51 Lucid                    ||   14 (+3) ||    4 ||
[17:14] <apw> || linux-mvl-dove Lucid                     ||    0 (-9) ||    0 ||
[17:14] <apw> || linux-mvl-dove Maverick                  ||   10 (+1) ||    4 ||
[17:14] <apw> || linux-ti-omap4 Maverick                  ||   15 (+3) ||    4 ||
[17:14] <apw> || linux-ti-omap4 Natty                     ||   12 (+5) ||    4 ||
[17:14] <apw> || linux-ti-omap4 Oneiric                   ||    7 (+1) ||    4 ||
[17:14] <apw> || linux-ti-omap4 Precise                   ||    5      ||    4 ||
[17:14] <apw> || linux-lts-backport-maverick Lucid        ||   14 (+3) ||    5 ||
[17:14] <apw> || linux-lts-backport-natty Lucid           ||   13 (+3) ||    5 ||
[17:14] <apw> || linux-lts-backport-oneiric Lucid         ||   10 (+1) ||    5 ||
[17:14] <apw>  
[17:14] <apw> Note that the table has a new column this week, the "Defd" column
[17:14] <apw> represents the number of CVEs which have been referred back to security for
[17:14] <apw> resoution, either for lack of a fix or if the fix is not clearly complete.
[17:14] <apw>  
[17:14] <apw> Nine new CVEs were added this week, of which about 6 have been resolved.
[17:14] <apw> We have also finally dropped lucid/mvl-dove from the table above.
[17:14] <apw>  
[17:14] <apw> ..
[17:14] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Oneiric/Natty/Maverick/Lucid/Hardy (bjf/herton)
[17:15] <bjf> Here is the status for the main kernels, until today (Jan. 24):
[17:15] <bjf>  
[17:15] <bjf>  * Hardy - 2.6.24-30.98
[17:15] <bjf>   * Nothing new this cycle.
[17:15] <bjf>  
[17:15] <bjf>  * Lucid - 2.6.32-38.85
[17:15] <bjf>   * Proposed is frozen due to 10.04.4 prep.
[17:15] <bjf>  
[17:15] <bjf>  * Maverick - 2.6.35-32.65
[17:15] <bjf>   * Verification testing.
[17:15] <bjf>  
[17:15] <bjf>  * Natty - 2.6.38-13.55
[17:15] <bjf>   * Verification testing.
[17:15] <bjf>  
[17:15] <bjf>  * Oneiric - 3.0.0-16.27
[17:15] <bjf>   * Verification testing.
[17:15] <bjf>  
[17:15] <bjf> Current opened tracking bugs details:
[17:15] <bjf>  * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:15] <bjf>  
[17:15] <bjf> For SRUs, SRU report is a good source of information:
[17:15] <bjf>  * http://people.canonical.com/~kernel/reports/sru-report.html
[17:15] <bjf>  
[17:15] <bjf> Future stable cadence cycles:
[17:15] <bjf>  * https://wiki.ubuntu.com/PrecisePangolin/ReleaseInterlock
[17:15] <bjf> ..
[17:15] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:16] <jsalisbury> OK, Thanks everyone
[17:16] <apw> jsalisbury, thanks
[17:16] <jsalisbury> #endmeeting
[17:16] <meetingology> Meeting ended Tue Jan 31 17:16:26 2012 UTC.
[17:16] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-01-31-17.00.moin.txt