=== jjohansen is now known as jj-afk | ||
=== doko_ is now known as doko | ||
=== yofel_ is now known as yofel | ||
=== Quintasan_ is now known as Quintasan | ||
cp1 | The calendar appears to have multiple meetings scheduled at the same time coming up. Has anyone been working on resolving it? | 16:10 |
---|---|---|
JFo | cp1, what calendar are you referring to? | 16:28 |
=== jj-afk is now known as jjohansen | ||
smoser | cp1, JFo probably http://www.ubuntu-news.org/calendars/fridge/ | 16:58 |
smoser | which, does in fact show overlaping meetings | 16:58 |
charlie-tca | but it does depend on where the meeting is held, too. | 16:59 |
Daviey | Hello! | 17:00 |
cp1 | It is supposed to be in UTC time, so it shouldn't matter where you are. I have it available via my google cal and it adjusts to EST. | 17:01 |
JFo | cp1, oh right, not all of those meetings are held in this chanel | 17:02 |
hallyn | \o | 17:03 |
JFo | interesting that the app review board meeting is scheduled to be at 5 though | 17:03 |
smb | Just minor nitpick that the headline says fridge calendar is used for #ubuntu-meeting... :-P | 17:03 |
cp1 | I sent an email to the two people running the conflicting meetings. | 17:03 |
* JFo goeas away | 17:03 | |
smb | But we are invading server-team meeting | 17:03 |
cp1 | Yes we invaded, or they haven't started yet... | 17:03 |
smb | They try :) | 17:04 |
robbiew | get out | 17:04 |
smb | \o | 17:04 |
robbiew | lol | 17:04 |
charlie-tca | Also, sometimes the meeting times get confused and come out wrong | 17:04 |
* hallyn holds off on hitting the trigger | 17:04 | |
SpamapS | o/ | 17:04 |
Daviey | hallyn, just shoot them all. | 17:04 |
hallyn | are we good to go, or should another meeting take precedence? | 17:04 |
hallyn | ok | 17:05 |
hallyn | #startmeeting | 17:05 |
MootBot | Meeting started at 11:05. The chair is hallyn. | 17:05 |
MootBot | Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] | 17:05 |
RoAkSoAx | o/ | 17:05 |
Daviey | \o | 17:05 |
hallyn | oh no, my clipboard isn't working, this is gonna be a slow one | 17:05 |
SpamapS | already on oneiric? ;) | 17:05 |
robbiew | oh man...don't get me started | 17:05 |
Daviey | oneiric is rocking. | 17:06 |
hallyn | [TOPIC] Review ACTION items from previous meeting | 17:06 |
MootBot | New Topic: Review ACTION items from previous meeting | 17:06 |
hallyn | no items? | 17:06 |
Daviey | don't think there was | 17:06 |
hallyn | [TOPIC] Oneiric Development | 17:06 |
MootBot | New Topic: Oneiric Development | 17:06 |
Daviey | Review blueprints! | 17:07 |
Daviey | Thanks everyone who filed their blueprints already. | 17:07 |
Daviey | This Thursday is feature definition freeze | 17:07 |
Daviey | This means that they should all be squared away by then. | 17:07 |
Daviey | We really, really need peer reviews | 17:07 |
RoAkSoAx | mine are waiting review | 17:07 |
Daviey | (open to everyone in ~ubuntu-server) | 17:07 |
RoAkSoAx | :) | 17:07 |
SpamapS | ugh.. | 17:08 |
Daviey | RoAkSoAx, I thought i sent you a mail asking some questions yesterday? :) | 17:08 |
hallyn | action? | 17:08 |
* SpamapS needs to finish boot-experience spec.. :-P | 17:08 | |
zul | i would like some reviews as well | 17:08 |
RoAkSoAx | Daviey: uhmmmmmmm I didn't receive anything | 17:08 |
RoAkSoAx | :S | 17:08 |
Daviey | Blueprints are the most important outcome of this week, really. | 17:08 |
hallyn | [ACTION] All: spec peer reviews | 17:08 |
MootBot | ACTION received: All: spec peer reviews | 17:08 |
RoAkSoAx | Daviey: maybe you forgot to clic send :D | 17:09 |
* Daviey checks | 17:09 | |
robbiew | what | 17:09 |
robbiew | no | 17:09 |
robbiew | I got iut | 17:09 |
robbiew | it | 17:09 |
hallyn | Daviey: for the meeting notes, what's that link again to get the list of server specs? | 17:09 |
Daviey | RoAkSoAx, Subject: Infrastructure power management (server-o-infra-power) ? | 17:09 |
smoser | what does "spec peer reviews" mean ? | 17:10 |
Daviey | anyway, we'll take that out of band. | 17:10 |
robbiew | hallyn: https://blueprints.launchpad.net/sprints/uds-o?searchtext=server-o | 17:10 |
smoser | where would i do such a thing ? | 17:10 |
robbiew | sort by spec name | 17:10 |
Daviey | smoser, Question the implementation, and direction. | 17:10 |
hallyn | thx | 17:10 |
smoser | where? | 17:10 |
* Daviey will send a post to ubuntu-server ml today with further details. | 17:10 | |
smoser | in the whiteboard ? | 17:10 |
Daviey | smoser, on the whiteboard. | 17:10 |
smoser | what a messy place for such a thing. I have no suggestion for anything better. | 17:10 |
smoser | but conversations there are just about impssible to follow. | 17:11 |
robbiew | fwiw, all approved blueprints can be found here: http://blueprints.launchpad.net/~ubuntu-server/+specs?role=assignee | 17:11 |
RoAkSoAx | Daviey: no nothign... didn't receive anything.. that bluprint is being driven by Arnaud from Eaton btw | 17:11 |
hallyn | [LINK] http://blueprints.launchpad.net/~ubuntu-server/+specs?role=assignee | 17:11 |
MootBot | LINK received: http://blueprints.launchpad.net/~ubuntu-server/+specs?role=assignee | 17:11 |
hallyn | [LINK] https://blueprints.launchpad.net/sprints/uds-o?searchtext=server-o | 17:11 |
MootBot | LINK received: https://blueprints.launchpad.net/sprints/uds-o?searchtext=server-o | 17:11 |
RoAkSoAx | Daviey: cause it is not powernap :), but rather NUT | 17:11 |
Daviey | RoAkSoAx, Yeah, i was asking input - i'll send it again. | 17:11 |
RoAkSoAx | Daviey: cool ;) | 17:12 |
Daviey | That is all from me.. | 17:12 |
Daviey | ta | 17:12 |
hallyn | [TOPIC] Ubuntu Server Team Events | 17:12 |
MootBot | New Topic: Ubuntu Server Team Events | 17:12 |
hallyn | anything new coming up? | 17:13 |
hallyn | i intend to be at first part of plumber's for security mini-conf | 17:13 |
Daviey | Nothing exciting comes to mind... i think we are all still resting. | 17:13 |
Daviey | hallyn, Oh - interesting.. we all look forward to the blog post covering that. | 17:13 |
hallyn | moving on, then | 17:13 |
hallyn | [TOPIC] Weekly Updates & Questions for the QA Team (hggdh) | 17:14 |
MootBot | New Topic: Weekly Updates & Questions for the QA Team (hggdh) | 17:14 |
hallyn | hggdh: around? | 17:14 |
hallyn | ok, moving on | 17:15 |
hallyn | [TOPIC] Weekly Updates & Questions for the Kernel Team (smb) | 17:15 |
MootBot | New Topic: Weekly Updates & Questions for the Kernel Team (smb) | 17:15 |
hallyn | smb: hey | 17:15 |
smb | hello | 17:15 |
smb | Just one reminder about my asking about iscsitarget to be only userspace dkms for oneiric. | 17:15 |
smb | I think it should be ok as it is imo not required for installation or boot | 17:16 |
hallyn | any questions for smb? | 17:16 |
* smb wonders whether he got moderated out of server-ml | 17:16 | |
hallyn | huh | 17:16 |
Daviey | smb, no - i waved you through | 17:16 |
smb | Daviey, Ta. :) | 17:17 |
hallyn | ok, moving on then | 17:17 |
smb | (actually meant still stuck in the moderation queue) | 17:17 |
smb | ok with me | 17:17 |
hallyn | Daviey: want an action to push that through? :) | 17:17 |
hallyn | [TOPIC] Weekly Updates & Questions from the Ubuntu Community | 17:17 |
MootBot | New Topic: Weekly Updates & Questions from the Ubuntu Community | 17:18 |
Daviey | hmm | 17:18 |
Daviey | hallyn / smb: i passed your message through the queue when you sent it. | 17:18 |
cp1 | I wanted to ask about how we might do a better job with security updates. For example the last exim update was kind of slow compared to Debian, and if I had known about it earlier I could have helped patch it and get it out sooner. In that case some people at exim.org knew about the issue about a month ahead of time. So how can we improve issues like that? | 17:18 |
smb | Daviey, Understood that. Just thought my initial question was not put the right way | 17:19 |
hallyn | does the security team have a list of pending security updates, for volunteers to look through? | 17:19 |
hallyn | jdstrand: ^ | 17:19 |
Daviey | non embargoed ones, i guess. | 17:20 |
Daviey | I don't know that you can split bugs by server, and security in launchpad easily. | 17:20 |
kees | hallyn: yes: http://people.canonical.com/~ubuntu-security/cve/main.html | 17:20 |
hallyn | [LINK] http://people.canonical.com/~ubuntu-security/cve/main.html | 17:20 |
MootBot | LINK received: http://people.canonical.com/~ubuntu-security/cve/main.html | 17:20 |
dholbach | Daviey, package sets! | 17:20 |
hallyn | kees: thanks | 17:20 |
jdstrand | hallyn: yes, it is incorporated into the sponsoring list and patch piloting. that said, we will be offering up 10-15 packages a month for people to contribue to, as part of the security-o-community bp | 17:20 |
kees | hallyn: and if you want to watch specific package, http://people.canonical.com/~ubuntu-security/cve/ | 17:21 |
ScottK | If you are aware of an embargoed issue and have a patch, you can file a private security bug with it so the security team can get a running start at it. | 17:21 |
ScottK | cp1: ^^^ | 17:21 |
jdstrand | hallyn: this is of course all in addition to what kees just mentioned | 17:21 |
ScottK | I've done this a number of times and it's worked out nicely. | 17:21 |
hallyn | jdstrand: ScottK: dholbach: thanks :) | 17:21 |
hallyn | cp1: maybe you can convert that to an rss feed :) | 17:22 |
cp1 | My problem is I wasn't aware of it early enough. | 17:22 |
kees | cp1: if you want to watch exim4 specifically, this works: http://people.canonical.com/~ubuntu-security/cve/pkg/exim4.html | 17:23 |
hallyn | Right, whatever form the list takes - or if you watch one of the many CVE lists - you do simply need to watch it or have a running search for exim | 17:23 |
cp1 | CVE tagging isn't always helpful, for example mhonarc has some issues now and the bug in lauchpad doesn't have the CVE's associated with it. | 17:23 |
hallyn | just have a cronjob scrape it daily and check for diffs... | 17:23 |
hallyn | So we need to do a better job with taggin? | 17:24 |
Daviey | yah.. more stuff to do :) | 17:24 |
hallyn | cp1: let's discuss anything further in #ubuntu-hardened | 17:25 |
hallyn | moving on, | 17:25 |
hallyn | [TOPIC] Open Discussion | 17:25 |
MootBot | New Topic: Open Discussion | 17:25 |
hallyn | any? | 17:25 |
Daviey | Blueprints, Blueprints and Blueprints | 17:25 |
Daviey | :) | 17:25 |
SpamapS | BadgersBadgersBadgers | 17:26 |
* RoAkSoAx hates university's wifi network :) | 17:26 | |
hallyn | I'm hoping to fill in the packaging requests for all spice related packages before i slip away | 17:26 |
ttx | RoAkSoAx: switch :) | 17:26 |
SpamapS | hallyn: do not go quietly into the night | 17:26 |
RoAkSoAx | ttx: can't... I'm gonna be here for the rest of the day | 17:26 |
ScottK | hallyn: You know what packaging requests get you, right? | 17:26 |
RoAkSoAx | :( | 17:26 |
ScottK | hallyn: With a packaging request and a package you've created then you'll get a package. | 17:26 |
hallyn | ScottK: not sure i follow | 17:27 |
Daviey | 1. Packaging Request | 17:27 |
Daviey | 2. Package | 17:27 |
Daviey | 3 Profit! | 17:27 |
RoAkSoAx | Daviey: 3. Upload | 17:28 |
Daviey | We've solved it. | 17:28 |
RoAkSoAx | 4. Profit | 17:28 |
hallyn | yeah, i did them out of order... | 17:28 |
hallyn | dat be how i roll | 17:28 |
Daviey | Thanks for the meeting hallyn . | 17:28 |
hallyn | [TOPIC] Announce next meeting date and time | 17:28 |
MootBot | New Topic: Announce next meeting date and time | 17:28 |
SpamapS | One more topic.. any pies in the face planned for UDS-P ? | 17:28 |
hallyn | Tuesday, May 31st 2011 16:00 UTC | 17:29 |
ScottK | hallyn: Just filing package requests almost never results in an actual package being created. | 17:29 |
zul | SpamapS: yeah thats what motivates me ;) | 17:29 |
hallyn | ScottK: i just want the permission to upload them to universe :) | 17:29 |
hallyn | ScottK: you're just telling me i need to do the packaging, right? | 17:29 |
ScottK | hallyn: No packaging bug is needed for that. | 17:29 |
ScottK | yes. | 17:29 |
SpamapS | hallyn: quick end it before it grows another head! | 17:29 |
hallyn | #endmeeting | 17:29 |
MootBot | Meeting finished at 11:29. | 17:29 |
hallyn | :) | 17:29 |
hallyn | ScottK: yup, thanks | 17:29 |
hallyn | thanks all, see ya | 17:30 |
SpamapS | hallyn: ty! | 17:30 |
ScottK | There is no requirement in Ubuntu for such things. | 17:30 |
ScottK | No requirement in Debian either, but Lintian tells fibs about that. | 17:30 |
hallyn | ScottK: lemme move to #ubuntu-server and inquire further | 17:30 |
ScottK | OK | 17:30 |
bjf | tick | 17:57 |
bjf | tock | 17:57 |
jjohansen | \o | 17:59 |
ppisati | o/ | 17:59 |
apw | o/ | 17:59 |
herton | o/ | 17:59 |
smb | \o | 17:59 |
sforshee | o/ | 17:59 |
bjf | #startmeeting | 18:00 |
JFo | o/ | 18:00 |
MootBot | Meeting started at 12:00. The chair is bjf. | 18:00 |
MootBot | Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] | 18:00 |
bjf | ## | 18:00 |
bjf | ## This is the Ubuntu Kernel Team weekly status meeting. | 18:00 |
bjf | ## | 18:00 |
bjf | [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting | 18:00 |
bjf | [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty | 18:00 |
MootBot | LINK received: https://wiki.ubuntu.com/KernelTeam/Meeting | 18:00 |
MootBot | LINK received: https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty | 18:00 |
bjf | # Meeting Etiquette | 18:00 |
bjf | # | 18:00 |
bjf | # NOTE: '..' indicates that you are finished with your input. | 18:00 |
bjf | # 'o/' indicates you have something you'd like to add (wait until you are recognized) | 18:00 |
bjf | # | 18:00 |
bjf | [TOPIC] Release Metrics (JFo) | 18:00 |
MootBot | New Topic: Release Metrics (JFo) | 18:00 |
JFo | Release Meeting Bugs (0 bugs, 18 Blueprints) | 18:00 |
JFo | ==== Release Milestoned Bugs (24 across all packages) ==== | 18:00 |
JFo | * 0 linux kernel bugs () | 18:00 |
JFo | * 0 linux-ti-omap4 bugs () | 18:00 |
JFo | * 0 linux-meta-ti-omap4 bug () | 18:00 |
JFo | ==== Release Targeted Bugs (171 across all packages) ==== | 18:00 |
JFo | * 21 linux kernel bugs () | 18:00 |
JFo | * 6 linux-ti-omap4 bugs () | 18:00 |
JFo | * 0 linux-meta-ti-omap4 bug () | 18:00 |
JFo | ==== Milestoned Features ==== | 18:00 |
JFo | * 1 blueprint (Including HWE Blueprints) | 18:00 |
JFo | ==== Natty Updates Bugs ==== | 18:00 |
JFo | * 28 Linux Bugs () | 18:00 |
JFo | ==== Maverick Updates Bugs ==== | 18:00 |
JFo | * 5 Linux Bugs (no change) | 18:01 |
JFo | ==== Lucid Updates Bugs ==== | 18:01 |
JFo | * 17 Linux Bugs (up 1) | 18:01 |
JFo | ==== Bugs with Patches Attached:90 (up 3) ==== | 18:01 |
JFo | * [[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on | Bugs with Patches]] | 18:01 |
JFo | * [[http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/ | Breakdown by status]] | 18:01 |
JFo | .. | 18:01 |
bjf | [TOPIC] Blueprints: Oneiric Bug Handling (JFo) | 18:01 |
bjf | [LINK] https://blueprints.launchpad.net/ubuntu/+spec/other-kernel-o-bug-handling | 18:01 |
MootBot | New Topic: Blueprints: Oneiric Bug Handling (JFo) | 18:01 |
MootBot | LINK received: https://blueprints.launchpad.net/ubuntu/+spec/other-kernel-o-bug-handling | 18:01 |
JFo | All alpha 1 items are in progress: | 18:01 |
JFo | [jeremyfoshee] work with SRU team and KRM to develop/define process for addressing development kernel bugs.: INPROGRESS | 18:01 |
JFo | * started this conversation with an e-mail. | 18:01 |
JFo | [jeremyfoshee] Generate specific hotlist for devel bugs focus: INPROGRESS | 18:01 |
JFo | * will initially use the same requirements as the 'by team' hotlist, but focused on Oneiric | 18:01 |
JFo | * copied the hotlist script and currently working through changes | 18:01 |
JFo | [jeremyfoshee] drive new state bugs to 0 and maintain 0 new status bugs daily: INPROGRESS | 18:01 |
JFo | * 8 current oneiric bugs. All have been initially triaged and are now going through deeper analysis | 18:01 |
JFo | * so far this has helped me determine what skills I'd like to further develop | 18:01 |
JFo | [jeremyfoshee] identify which scripts we no longer run which we should port forward (with the aim of 0 New bugs): INPROGRESS | 18:01 |
JFo | * Brad's confirmed script is doing a great job currently of identifying what bugs are complete | 18:01 |
JFo | enough to be set confirmed | 18:02 |
JFo | * Started the discussion on this in e-mail. Will follow up with some thoughts as soon as I have had the time | 18:02 |
JFo | to evaluate the responses and chatted with Pete (he's been quite busy lately :)) | 18:02 |
JFo | .. | 18:02 |
bjf | [TOPIC] Blueprints: Oneiric Config Review (ogasawara) | 18:02 |
bjf | [LINK] https://blueprints.launchpad.net/ubuntu/+spec/other-kernel-o-config-review | 18:02 |
MootBot | New Topic: Blueprints: Oneiric Config Review (ogasawara) | 18:02 |
MootBot | LINK received: https://blueprints.launchpad.net/ubuntu/+spec/other-kernel-o-config-review | 18:02 |
ogasawara | We just need to schedule a follow on config review session to look at jj's config comparisons. I suggest we do this at the Rally. I'm continuing to work through some of the config options noted from UDS, none of which are critical for the Alpha-1 release. | 18:02 |
ogasawara | .. | 18:02 |
bjf | [TOPIC] Blueprints: Oneiric Delta Review (ogasawara) | 18:03 |
bjf | [LINK] https://blueprints.launchpad.net/ubuntu/+spec/other-kernel-o-ubuntu-delta-review | 18:03 |
MootBot | New Topic: Blueprints: Oneiric Delta Review (ogasawara) | 18:03 |
MootBot | LINK received: https://blueprints.launchpad.net/ubuntu/+spec/other-kernel-o-ubuntu-delta-review | 18:03 |
ogasawara | apw, bjf, jjohansen, kees, lag, manjo, mpoirier, ralveti, rtg: you have Alpha-1 work items to review your set of Ubuntu patches. Please take a moment to review or postpone till Alpha-2. See https://wiki.ubuntu.com/KernelTeam/Specs/KernelOneiricUbuntuDeltaReview for your specific set of patches. | 18:03 |
ogasawara | .. | 18:03 |
bjf | [TOPIC] Blueprints: Oneiric Server Requirements (smb) | 18:03 |
bjf | [LINK] https://blueprints.launchpad.net/ubuntu/+spec/other-kernel-o-server-requirements | 18:03 |
MootBot | New Topic: Blueprints: Oneiric Server Requirements (smb) | 18:03 |
MootBot | LINK received: https://blueprints.launchpad.net/ubuntu/+spec/other-kernel-o-server-requirements | 18:03 |
smb | All good (nothing started) | 18:03 |
smb | .. | 18:03 |
bjf | [TOPIC] Status: General Oneiric (ogasawara) | 18:04 |
MootBot | New Topic: Status: General Oneiric (ogasawara) | 18:04 |
ogasawara | We've uploaded the 2.6.39-3.9 kernel which is based on upstream v2.6.39 final. I intend to keep us on v2.6.39 final for our Alpha-1 release on Thurs June 2. | 18:04 |
ogasawara | .. | 18:04 |
bjf | [TOPIC] Status: Stable Kernel Team (sconklin / bjf) | 18:04 |
MootBot | New Topic: Status: Stable Kernel Team (sconklin / bjf) | 18:04 |
sconklin | || | 18:04 |
sconklin | || All kernel packages in -proposed have had verification complete and will be published when Certification and | 18:04 |
sconklin | || QA are complete (Not all series receive Certification). The Stable team will prepare new kernel packages this | 18:04 |
sconklin | || week to begin a new cycle. | 18:04 |
sconklin | || | 18:04 |
sconklin | || As decided at UDS, the stable kernel cadence will change to a three week cycle, in order to allow time to | 18:04 |
sconklin | || properly prepare the kernel packages | 18:04 |
sconklin | .. | 18:04 |
bjf | [TOPIC] Security & bugfix kernels - Maverick/Lucid/Hardy (sconklin / bjf) | 18:05 |
MootBot | New Topic: Security & bugfix kernels - Maverick/Lucid/Hardy (sconklin / bjf) | 18:05 |
sconklin | Oh, forgot to mention that we Have Herton helping us now (YAY) | 18:05 |
sconklin | || Package || Upd/Sec || Proposed || TiP || Verified || | 18:05 |
sconklin | || || || || || || | 18:05 |
sconklin | || lucid linux-ec2 || 2.6.32-314.27 || 2.6.32-316.31 || 8 || 8 || | 18:05 |
sconklin | || --- linux-ports-meta || 2.6.32.31.23 || 2.6.32.32.24 || 0 || 0 || | 18:05 |
sconklin | || --- linux-meta-lts-backport-maverick || 2.6.35.25.36 || 2.6.35.28.37 || 0 || 0 || | 18:05 |
sconklin | || --- linux-lts-backport-maverick || 2.6.35-25.44~lucid1 || 2.6.35-28.50~lucid1 || 13 || 13 || | 18:05 |
sconklin | || --- linux-backports-modules-2.6.32 || 2.6.32-31.31 || 2.6.32-32.32 || 0 || 0 || | 18:05 |
sconklin | || --- linux-firmware || 1.34.7 || 1.34.10 || 0 || 0 || | 18:05 |
sconklin | || --- linux || 2.6.32-31.61 || 2.6.32-32.62 || 4 || 4 || | 18:05 |
sconklin | || --- linux-meta || 2.6.32.31.37 || 2.6.32.32.38 || 1 || 0 || | 18:05 |
sconklin | || --- linux-meta-ec2 || 2.6.32.314.15 || 2.6.32.316.17 || 0 || 0 || | 18:05 |
sconklin | || || || || || || | 18:05 |
sconklin | || maverick linux-ports-meta || 2.6.35.28.21 || 2.6.35.29.22 || 0 || 0 || | 18:05 |
sconklin | || --- linux-backports-modules-2.6.35 || 2.6.35-28.20 || 2.6.35-29.21 || 0 || 0 || | 18:05 |
sconklin | || --- linux-meta || 2.6.35.28.36 || 2.6.35.29.37 || 0 || 0 || | 18:05 |
sconklin | || --- linux-firmware || 1.38.6 || 1.38.8 || 1 || 0 || | 18:05 |
smb | \o | 18:06 |
sconklin | || --- linux || 2.6.35-28.50 || 2.6.35-29.51 || 11 || 9 || | 18:06 |
sconklin | || || || || || || | 18:06 |
sconklin | || natty linux-ti-omap4 || || 2.6.38-1209.13 || 10 || 10 || | 18:06 |
sconklin | || --- linux-backports-modules-2.6.38 || || 2.6.38-9.3 || 0 || 0 || | 18:06 |
sconklin | || --- linux-meta-ti-omap4 || || 2.6.38.1209.7 || 0 || 0 || | 18:06 |
sconklin | || --- linux-meta || || 2.6.38.9.23 || 0 || 0 || | 18:06 |
sconklin | || --- linux || || 2.6.38-9.43 || 9 || 9 || | 18:06 |
sconklin | || || || || || || | 18:06 |
sconklin | .. | 18:06 |
smb | Maverick proposed fails to boot on ec2. Currently investigating. | 18:06 |
smb | .. | 18:06 |
bjf | smb go | 18:06 |
bjf | heh | 18:06 |
bjf | [TOPIC] Incoming Bugs: Regressions (JFo) | 18:07 |
MootBot | New Topic: Incoming Bugs: Regressions (JFo) | 18:07 |
JFo | Incoming Bugs | 18:07 |
JFo | 9 Oneiric Bugs () | 18:07 |
JFo | 1207 Natty Bugs (up 273) | 18:07 |
JFo | 1142 Maverick Bugs (up 13) | 18:07 |
JFo | 1029 Lucid Bugs (up 7) | 18:07 |
JFo | Current regression stats (broken down by release): | 18:07 |
JFo | ==== regression-update ==== | 18:07 |
JFo | * 1 natty bug () | 18:07 |
JFo | * 42 maverick bugs (up 1) | 18:07 |
JFo | * 74 lucid bugs (no change) | 18:07 |
JFo | * 4 karmic bugs (no change) | 18:07 |
JFo | * 0 hardy bugs (no change) | 18:07 |
JFo | ==== regression-release ==== | 18:07 |
JFo | * 458 natty bugs (down 26) | 18:07 |
JFo | * 244 maverick bugs (up 2) | 18:07 |
JFo | * 222 lucid bugs (up 4) | 18:07 |
JFo | * 37 karmic bugs (down 1) | 18:07 |
JFo | * 2 hardy bugs (no change) | 18:07 |
JFo | ==== regression-proposed ==== | 18:07 |
JFo | * 1 natty bugs (up 1) | 18:07 |
JFo | * 2 maverick bugs (no change) | 18:07 |
JFo | * 0 lucid bugs (no change) | 18:07 |
JFo | * 0 karmic bugs (no change) | 18:07 |
JFo | .. | 18:07 |
bjf | probably don't need to be tracking the karmic bugs :-) | 18:08 |
JFo | thanks bjftrue | 18:08 |
JFo | : | 18:08 |
JFo | :) | 18:08 |
bjf | [TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/) | 18:08 |
MootBot | New Topic: Open Discussion or Questions: Raise your hand to be recognized (o/) | 18:08 |
bjf | sorry for the long, drawn out meeting, the one right after UDS is usually brutal | 18:09 |
bjf | :-) | 18:09 |
kamal | :-) thanks bjf | 18:09 |
bjf | thanks everyone | 18:09 |
bjf | #endmeeting | 18:09 |
MootBot | Meeting finished at 12:09. | 18:09 |
JFo | bjf, thank you sir | 18:09 |
smb | thanks bjf | 18:09 |
apw | :) | 18:09 |
ppisati | cool | 18:09 |
kees | ogasawara: thanks, I'll get nx-emu done today | 18:45 |
ogasawara | kees: no hurry | 18:45 |
=== yofel_ is now known as yofel | ||
=== skFIN is now known as skfin | ||
=== stalcup is now known as vorian |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!