| cprofitt | JanC, popey you guys here? | 04:12 |
|---|---|---|
| === rgreening_ is now known as rgreening | ||
| === ShadowChild is now known as lukjad007 | ||
| === ember_ is now known as ember | ||
| === ejat is now known as e-jat | ||
| === asac_ is now known as asac | ||
| === ogra_ is now known as ogra | ||
| === yofel_ is now known as yofel | ||
| pitti | o/ | 15:58 |
| ttx | o/ | 15:58 |
| * slangasek waves | 15:59 | |
| fader | Howdy | 15:59 |
| heno | hey | 16:00 |
| * apw listens in | 16:00 | |
| bjf | o/ | 16:00 |
| * lool waves | 16:00 | |
| mdz | hi | 16:02 |
| cjwatson | yo | 16:02 |
| cr3 | hi folks | 16:02 |
| * pgraner waves | 16:02 | |
| cjwatson | slangasek: are you chairing or is it rotating? | 16:03 |
| slangasek | davidm, Riddell, sbeattie, Hobbsee, ScottK: there? | 16:03 |
| ScottK | slangasek: Here | 16:04 |
| slangasek | cjwatson: I was planning to | 16:04 |
| slangasek | #startmeeting | 16:04 |
| MootBot | Meeting started at 10:04. The chair is slangasek. | 16:04 |
| MootBot | Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] | 16:04 |
| davidm | slangasek, here | 16:04 |
| slangasek | [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-06-19 | 16:04 |
| MootBot | LINK received: https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-06-19 | 16:04 |
| Riddell | hi | 16:04 |
| sbeattie | hey | 16:05 |
| slangasek | hi, folks | 16:05 |
| slangasek | as mentioned in the email, the main topic today is to gather up our feature definitions for karmic | 16:05 |
| slangasek | ttx has asked to go first due to time constraints | 16:06 |
| slangasek | [TOPIC] Server team | 16:06 |
| MootBot | New Topic: Server team | 16:06 |
| ttx | o/ | 16:06 |
| ttx | Not much progress since last week. All specs were filed, but we have too much of them... | 16:06 |
| ttx | so we are in the process of prioritizing them | 16:07 |
| slangasek | ttx: when can we expect that work to be done? | 16:07 |
| ttx | slangasek: I hope on Monday. | 16:07 |
| ttx | slangasek: it's more on dendrobates hands right now | 16:07 |
| slangasek | ok | 16:07 |
| ttx | There is some organizational change under way in the team but it's not complete yet. | 16:07 |
| slangasek | is there a partial list of known confirmed specs that we should look at? | 16:08 |
| mdz | dendrobates: ? | 16:08 |
| ttx | I don't think any of them was formally approved yet. | 16:09 |
| slangasek | ok | 16:09 |
| ttx | server-karmic-eucalyptus-in-main and server-karmic-cloud-power-management are the only two already known to be Essential | 16:09 |
| ttx | slangasek: What exactly do you need to discuss by FeatureDefinitionFreeze ? | 16:10 |
| ttx | sladen: new packages ? MIRs ? | 16:10 |
| slangasek | known essential specs> noted, thanks | 16:11 |
| ttx | The spec with most impact as far as new packages is concerned is probably server-karmic-euca-javadeps-refactoring | 16:11 |
| slangasek | ttx: IMHO it should cover any specs for features being added in karmic | 16:11 |
| ttx | slangasek: that means most of ours. You want to discuss all of them quickly ? Or it doesn't make sense until they are prioritized ? | 16:12 |
| slangasek | let's not spend time on them right now if we don't know which ones are actually planned to be worked on this cycle | 16:13 |
| slangasek | is server-karmic-euca-javadeps-refactoring a prereq for server-karmic-eucalyptus-in-main? | 16:13 |
| ttx | slangasek: not exactly. It makes an easier MIR process to have the package refactored before it's moved to main. | 16:14 |
| slangasek | ok | 16:14 |
| ttx | slangasek: rather than moving a giant trashcan to main. | 16:14 |
| slangasek | yes - even if it's not a prereq, please don't defer server-karmic-euca-javadeps-refactoring for too long in the cycle :) | 16:14 |
| ttx | slangasek: I'm on it already :) | 16:15 |
| cjwatson | what milestone is server-karmic-eucalyptus-in-main targeted for? | 16:15 |
| cjwatson | I have an Essential spec that depends on it, which I've currently targeted for alpha 3 | 16:15 |
| cjwatson | well, I suppose it isn't a hard dependency | 16:15 |
| ttx | cjwatson: we don't even know what Eucalyptus 1.6 dependencies will be yet. | 16:16 |
| slangasek | ttx: the only other thing I had on the list for you guys is bug #326768 - still marked as 'in progress', but no movement since last week, is mathiaz still on this? | 16:16 |
| cjwatson | specifically I'm referring to foundations-karmic-cloud-setup-in-server-installer | 16:16 |
| ubottu | Launchpad bug 326768 in mysql-dfsg-5.0 "mysqld_safe thinks mysqld has crashed when it hasn't" [High,In progress] https://launchpad.net/bugs/326768 | 16:16 |
| ttx | cjwatson: yes, another related spec is server-karmic-eucalyptus-fit-on-cd | 16:17 |
| ttx | both are not expected to be completed before we get upstream eucalyptus 1.6 | 16:17 |
| ttx | I'd say, not before alpha3 | 16:18 |
| ttx | so if you depend on it I'd advise retargting | 16:18 |
| cjwatson | well, I should start on the installer glue anyway | 16:18 |
| cjwatson | it'll take a while | 16:18 |
| cjwatson | I'll just not be able to actually deliver something testable by the general public until later - I'll note it in the whiteboard | 16:19 |
| ttx | cjwatson: I expect to complete both during the platform sprint | 16:19 |
| ttx | slangasek: about the mysql bug, mathiaz is still on it, no progress since last week. I'll make sure he updates the bug | 16:20 |
| ttx | we've been busy with blueprint finalization this week :) | 16:20 |
| slangasek | I don't mean to imply he needs to update the bug if there's been no progress - I'd rather he spend his available time working on it | 16:20 |
| slangasek | ttx: anything else to discuss? | 16:21 |
| ttx | slangasek: nothing from our side. I hope everything will be much clearer next week. | 16:21 |
| slangasek | [TOPIC] QA team | 16:21 |
| MootBot | New Topic: QA team | 16:21 |
| slangasek | heno, fader, sbeattie: hi | 16:22 |
| heno | hi | 16:22 |
| heno | Our roadmap is all ready: https://wiki.ubuntu.com/QATeam/RoadMap Specs are written, approved and prioritised. | 16:22 |
| heno | It's mostly bug management, test coverage and infrastructure; not much that will land in the distro - just some Checkbox enhancements | 16:22 |
| heno | karmic-qa-increase-apport-adoption, karmic-qa-checkbox-expand-test-coverage, karmic-qa-cert-install-from-live-cd-images and karmic-qa-metrics-based-testing are Essential | 16:22 |
| slangasek | ttx: sounds good, thanks | 16:22 |
| slangasek | [LINK] https://wiki.ubuntu.com/QATeam/RoadMap | 16:22 |
| MootBot | LINK received: https://wiki.ubuntu.com/QATeam/RoadMap | 16:22 |
| heno | questions? | 16:23 |
| mdz | heno: well done | 16:23 |
| slangasek | heno: thanks. :) Which are the ones that will land in the distro? I notice two 'checkbox' specs under 'Infrastructure', plus 'Increase Apport Coverage' which probably counts | 16:24 |
| heno | thanks :) we did some heavy-handed prioritisation early on, before most of the drafting | 16:24 |
| fader | slangasek: Of the checkbox ones, I think only karmic-qa-checkbox-expand-test-coverage will land in the distro | 16:24 |
| slangasek | ok | 16:24 |
| fader | It will add new tests to checkbox | 16:24 |
| heno | slangasek: right, some checkbox tweaks and lots of aport hooks | 16:24 |
| fader | The other one is for internal testing of the live CD which is specific to the testing environment | 16:25 |
| slangasek | sounds reasonable then | 16:25 |
| slangasek | do you guys have any concerns about these being delivered before feature freeze? | 16:25 |
| heno | slangasek: ATM, no :) | 16:26 |
| slangasek | okie | 16:26 |
| heno | cr3 can give an update on live cd testing | 16:26 |
| slangasek | anything to discuss regarding hardware testing this week? | 16:26 |
| cr3 | slangasek: live cd tests should start trickling in on Monday | 16:26 |
| fader | Nothing particularly new. As normal, status is here: http://people.ubuntu.com/~fader/hw-testing/current.html | 16:27 |
| fader | As cr3 says we should start getting live cd tests soon, which is a Good Thing | 16:27 |
| heno | ('til now we've only tested alternates) | 16:27 |
| fader | We don't have recent test results as there doesn't appear to have been a recent alternate cd image to test | 16:27 |
| slangasek | fader: I think your hwtest-breaking network kernel bug is still 'fix committed', right? | 16:27 |
| cr3 | live cd changes are in and just pending review, so we're in good shape | 16:27 |
| slangasek | yes, that's apparently my fault | 16:27 |
| fader | slangasek: Correct, but we haven't had an image to test with yet | 16:27 |
| slangasek | (and cjwatson fixed it this morning) | 16:27 |
| fader | So once we get one and test it I will update the bug | 16:27 |
| slangasek | fader: you've lost me - if it's 'fix committed', that implies it's in the git repo pending upload to karmic | 16:28 |
| slangasek | are you saying there's doubt about the correctness of the fix? | 16:28 |
| cjwatson | fader: if it's worth a quick build before the end of your week, we can do one any time from about half an hour from now onward | 16:29 |
| fader | slangasek: Ah, sorry, was thinking 'fix released' | 16:29 |
| slangasek | ok | 16:29 |
| fader | cjwatson: It would be nice to have but to be honest it will be easier to test next week once the live cd testing lands | 16:29 |
| fader | So if we wait until Monday or Tuesday that is fine... we'll be testing a lot of images then anyway | 16:29 |
| heno | slangasek: that's all from QA | 16:30 |
| slangasek | ack, thanks | 16:30 |
| slangasek | [TOPIC] Desktop team | 16:30 |
| MootBot | New Topic: Desktop team | 16:30 |
| lool | Hey | 16:30 |
| lool | Ups, not me yet :) | 16:30 |
| pitti | 1spec definition is by and large in good shape: https://blueprints.launchpad.net/ubuntu/karmic/+specs?searchtext=desktop-karmic- | 16:30 |
| pitti | the ones that are in drafting have been reviewed by me at least once and are just needing some clarifications | 16:30 |
| pitti | the main ones that are still missing are the DX changes, we have contacted them to get them ready | 16:31 |
| pitti | but https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus should be pretty accurate now in terms of what we'll do | 16:31 |
| pitti | in Karmic | 16:31 |
| slangasek | [LINK] https://blueprints.launchpad.net/ubuntu/karmic/+specs?searchtext=desktop-karmic- | 16:31 |
| MootBot | LINK received: https://blueprints.launchpad.net/ubuntu/karmic/+specs?searchtext=desktop-karmic- | 16:31 |
| slangasek | [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus | 16:32 |
| MootBot | LINK received: https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus | 16:32 |
| pitti | oops, ignore the "(specs in drafting, so don't take for granted yet):" from the wiki page | 16:32 |
| pitti | [removed now] | 16:32 |
| slangasek | looks good | 16:32 |
| pitti | wrt. your next question, | 16:33 |
| pitti | can't say yet whether _all_ of this will land in karmic by FF | 16:33 |
| slangasek | I'll have to spend some time fully absorbing that list later, and will get back to you with any concerns about individual specs | 16:33 |
| pitti | we were very aggressive wrt. feature goals this time, so it's likely that some low prio items won't make it | 16:33 |
| pitti | mostly because we'd rather break stuff now than in lazy lobster | 16:33 |
| slangasek | presumably those low-prio ones can get cut if they miss FF, being low-prio? | 16:34 |
| pitti | my goal is to have as few structural changes as possible in LL | 16:34 |
| pitti | right | 16:34 |
| pitti | essential/high -> must have | 16:34 |
| pitti | medium -> not the end of the world, but someone would get angry | 16:34 |
| pitti | low -> target of opportunity | 16:34 |
| pitti | that's roughly how we use them | 16:34 |
| * slangasek nods | 16:34 | |
| slangasek | and I see the bug status report is up-to-date there as well, ok | 16:35 |
| pitti | right | 16:35 |
| slangasek | anything you want to highlight/discuss further? | 16:35 |
| pitti | there hasn't been much progress on that this week unfortunately | 16:35 |
| pitti | we were mostly busy with blueprints | 16:35 |
| pitti | not from my side right now | 16:36 |
| slangasek | I continue to be concerned about bug #339313 in particular; I know the focus has been on spec writing, but this bug has been something of a debacle and I'd like to be able to see it fixed soon in the cycle | 16:37 |
| ubottu | Launchpad bug 339313 in ubuntu-release-notes "Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key" [Undecided,Fix released] https://launchpad.net/bugs/339313 | 16:37 |
| pitti | right, me too | 16:37 |
| pitti | we'll probably also SRU this | 16:37 |
| pitti | it can't get much worse in Karmic, so I was told | 16:37 |
| pitti | s/Karmic/Jaunty/, sorry | 16:37 |
| ScottK | Isn't that the NM update we have in -proposed already? | 16:38 |
| slangasek | is it? nothing indicates that on the bug | 16:38 |
| ScottK | It may be a different issue. | 16:38 |
| Riddell | yes it is | 16:38 |
| ScottK | OK | 16:38 |
| pitti | hm, then the changelog doesn't mention this bug | 16:38 |
| slangasek | mm, quite | 16:38 |
| slangasek | which means it's hard to track for SRU verification | 16:38 |
| Riddell | we should copy over the new version to -updates, it fixes it for some users and can't get any worse | 16:39 |
| pitti | hm, whoever processed that didn't update the bug very well | 16:39 |
| pitti | ok, let's sort this out out-of-band | 16:39 |
| rickspencer3 | I suppose we should see an update on this next week? with details about how it's been sorted? | 16:40 |
| slangasek | [ACTION] slangasek, pitti, Riddell, ScottK to sort out bug #339313 status | 16:40 |
| MootBot | ACTION received: slangasek, pitti, Riddell, ScottK to sort out bug #339313 status | 16:40 |
| ubottu | Launchpad bug 339313 in ubuntu-release-notes "Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key" [Undecided,Fix released] https://launchpad.net/bugs/339313 | 16:40 |
| rickspencer3 | tx | 16:40 |
| slangasek | rickspencer3: yes | 16:40 |
| slangasek | ok, shuffling the order here again; ScottK also has a schedule conflict and asked to be bumped up | 16:41 |
| slangasek | [TOPIC] MOTU | 16:41 |
| MootBot | New Topic: MOTU | 16:41 |
| slangasek | ScottK: hi | 16:42 |
| ScottK | Still sorting out Python 2.6 stuff. | 16:42 |
| ScottK | Nothing earthshattering there, but the pain isn't over. | 16:42 |
| * slangasek nods | 16:42 | |
| slangasek | (hmm, still need python2.5 dropped from python-defaults) | 16:42 |
| ScottK | Mostly merges and new package processing on REVU for now. | 16:43 |
| ScottK | There's also one or two Kubuntu related specs worth mentioning here. | 16:43 |
| ScottK | Specs are mostly sorted, but the Kubuntu - Ayatana one is getting approved a bit late because it's complex. | 16:44 |
| ScottK | https://blueprints.launchpad.net/ubuntu?searchtext=kubuntu+karmic is a decent list. | 16:44 |
| Riddell | I'll look at that later today | 16:44 |
| ScottK | https://blueprints.launchpad.net/ubuntu/+spec/kubuntu-karmic-netbook-edition will have some release management implications, but as it's meant to be mostly tech preview/proof of concept, I don't see it as a major issue. | 16:45 |
| ScottK | That's all I have. | 16:45 |
| rickspencer3 | ScottK: Riddell: would it be worth dropping a link to the Kubuntu TODO list? | 16:45 |
| ScottK | rickspencer3: Probably, if someone had it handy | 16:45 |
| Riddell | https://wiki.kubuntu.org/Kubuntu/Todo | 16:46 |
| Riddell | now burndown chat compatible I believe | 16:46 |
| Riddell | chart | 16:46 |
| rickspencer3 | yes | 16:46 |
| rickspencer3 | thanks to pitti and Riddell | 16:46 |
| ScottK | The good news is it looks like KDE4 integration for OOo is almost done and starting to land upstream (Go OOo) | 16:46 |
| ScottK | That took some serious heavy lifting and will benifit every KDE distro. | 16:47 |
| ScottK | That's all I've got. | 16:47 |
| slangasek | ScottK: probably old news to you having been around for a few of these, but please make sure (collectively) that any new netbook-edition images are ready to be tested well in advance of beta | 16:47 |
| ScottK | slangasek: Will do. | 16:47 |
| slangasek | [LINK] https://wiki.kubuntu.org/Kubuntu/Todo | 16:47 |
| MootBot | LINK received: https://wiki.kubuntu.org/Kubuntu/Todo | 16:47 |
| slangasek | ScottK: ok, thanks | 16:48 |
| slangasek | [TOPIC] Mobile team | 16:48 |
| MootBot | New Topic: Mobile team | 16:48 |
| lool | Our specs should be under review or pending approval and are tracked along with high prio bugs at: | 16:48 |
| slangasek | lool, davidm: hi | 16:48 |
| lool | [LINK] https://wiki.ubuntu.com/MobileTeam/Roadmap | 16:48 |
| lool | (I wish we'd have named all specs mobile-karmic-foo like the desktop ones) | 16:48 |
| MootBot | LINK received: https://wiki.ubuntu.com/MobileTeam/Roadmap | 16:48 |
| lool | Essential specs: | 16:48 |
| lool | - mobile-unr-karmic-seeds: cleanup seeds structure and seeds for UNR | 16:48 |
| lool | - mobile-qa-karmic-arm: Create testplans and testcases for Ubuntu on ARM Edit title and summary.. | 16:48 |
| lool | - mobile-unr-karmic-connman: switch UNR to connman | 16:49 |
| lool | High priority specs: | 16:49 |
| lool | - mobile-unr-karmic-applications: change in default apps in UNR | 16:49 |
| lool | - mobile-karmic-general-resolution-for-touchscreen-handling: provide tools to calibrate touchscreens | 16:49 |
| lool | - mobile-unr-karmic-application-res: improve support on low res for some apps under UNR | 16:49 |
| lool | Alpha 3 and overall release status: | 16:49 |
| lool | - all specs should be under review or approval (one is already implemented: moving UNR images to ISOs) | 16:49 |
| lool | - ARM images: | 16:49 |
| lool | - imx51: nothing new for now; Babbage 2 kernel should land for A3 (bjf? :-) and we got an early U-Boot drop which might supersede RedBoot altogether, so we'll evaluate this option after A3; we lack hardware (only 4 B2 boards available total for now) | 16:49 |
| lool | - we plan addition of a new architecture, but are waiting for bits from a partner and his permission to publish; we have early (unstable) hardware | 16:49 |
| lool | - ARM toolchain: we're getting late on this, we still want to build karmic with ARMv6 + VFP opts, and IS is currently benchmarking builds within qemu; we will get good ARMv7 buildd hardware, but presumably too late for that to be useful in karmic | 16:49 |
| lool | - UNR: moved from VFAT to ISO format; no large software update, still largely jaunty's stuff; some SRUs still TBD | 16:49 |
| lool | - 385325: I remilestoned this for beta; we continue researching this important bug, but it's not particularly a3-critical | 16:49 |
| lool | (done) | 16:49 |
| slangasek | mobile-unr-karmic-seeds> sounds like a good one to get done early, this time around - what still needs cleaned up? | 16:49 |
| bjf | look, yes, shooting babbage2 for A3 | 16:50 |
| pgraner | s/look/lool/ | 16:50 |
| slangasek | connman> so we'll have two different UIs to support for network connection management? | 16:50 |
| bjf | lool, issue could be when .31 drops and when we try to rebase to that | 16:50 |
| lool | Various things, and it's in progress already; I don't know all specifics, but I think we discussed using a separate live seed, using a common gtk-desktop seed and this kind of things | 16:50 |
| bjf | lool, still working on getting babbage 1 patches into Karmic, that's a struggle right now | 16:51 |
| lool | slangasek: StevenK does this spec and has started various changes already | 16:51 |
| ttx | slangasek: got to go now... ping dendrobates for any server-specific question. | 16:51 |
| lool | slangasek: Yes, apparently we will have to support connman for UNR | 16:51 |
| slangasek | ttx: no problem, thank you | 16:51 |
| lool | This is a request from sabdfl | 16:51 |
| lool | bjf: So the babbage 2 patches drop support for b1? | 16:52 |
| slangasek | hmm; last I heard, connman had no plans to support half the use cases covered by NM | 16:52 |
| bjf | lool, no, I need to get babbage 1 in before I start working on babbage 2 | 16:53 |
| lool | bjf: We don't strongly care about b1 support; if we can have it it's nice, otherwise we can continue running jaunty or just the jaunty redboot+kernel | 16:53 |
| lool | bjf: ok | 16:53 |
| bjf | lool, babbage 2 patches are build on-top-of babbage 1 patches, they have to go in first | 16:53 |
| lool | bjf: Ah there's a dependency, ok | 16:53 |
| bjf | lool, yes | 16:54 |
| lool | slangasek: During the connman session, upstream explained that connman doesn't attempt to cover everything and tries to be simpler | 16:54 |
| bjf | lool, this is a forward port of both the babbage 1 and babbage 2 patches | 16:54 |
| slangasek | lool: right, which sounds like a functionality regression to me :) | 16:54 |
| lool | slangasek: It will miss features, yes | 16:54 |
| pitti | is connman a replacement for the entire nm, or just for n-m-applet? | 16:55 |
| lool | For all of it | 16:55 |
| lool | davidm: If you have further comments on UNR connman integration, chime in | 16:56 |
| * ScottK runs off. Enjoy the rest of the meetnig. | 16:56 | |
| davidm | Pitti as I understand it it's a replacement for the entire nm stack | 16:56 |
| davidm | we will test with both | 16:57 |
| davidm | so choices can be made as appropriate. | 16:57 |
| slangasek | anyone have anything else for mobile? | 16:58 |
| lool | I think the hot things are images and toolchain | 16:58 |
| lool | But both will happen post a3, after updates from kernel, partner, and our IS | 16:59 |
| * slangasek nods | 16:59 | |
| slangasek | [TOPIC] Kernel team | 16:59 |
| MootBot | New Topic: Kernel team | 16:59 |
| slangasek | lool, davidm: thanks | 16:59 |
| pgraner | Hey everyone | 16:59 |
| pgraner | We have created a Release Status page for Karmic: | 16:59 |
| pgraner | https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic | 16:59 |
| pgraner | [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic | 16:59 |
| MootBot | LINK received: https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic | 16:59 |
| pgraner | This is a Red/Yellow/Green Status with links to the blueprints and specs. Its updated every Tues. in our team IRC meeting. You will also find all the bugs on your agenda on the == Release Meeting Bugs == section. | 17:00 |
| pgraner | On the same page | 17:00 |
| pgraner | All Specs are approved, and in some form of implementation | 17:00 |
| slangasek | is the next kernel upload scheduled? (seeing that half the bugs are 'fix committed') | 17:01 |
| pgraner | The only one that got deferred was the "Newer Kernels on LTS" | 17:01 |
| pgraner | slangasek: I don't know off hand rtg is scheduling it | 17:01 |
| rtg | slangasek: I'm still working with apw on the KMS/PAE issue | 17:01 |
| slangasek | ok | 17:01 |
| apw | what rtg said | 17:01 |
| pgraner | slangasek: what rtg said | 17:02 |
| apw | and there is also some interactons with the installer which need to be nailed down | 17:02 |
| apw | for the flavour names | 17:02 |
| rtg | slI think we should be OK to upload if the installer and the update manager cooperate | 17:02 |
| cjwatson | generic will just work | 17:02 |
| rtg | cjwatson: correct | 17:02 |
| cjwatson | I'll have time to do the pae stuff early next week | 17:03 |
| rtg | upgrades aren't an issue, its the initial install that might cause problems. | 17:03 |
| rtg | but I'll work with cjwatson on that | 17:03 |
| cjwatson | not *that* much of an issue. code to check cpuinfo flags is already there, just needs to be extended. | 17:03 |
| cjwatson | my main worry is that we *cannot* fit >1 kernel on the CD. | 17:03 |
| apw | then i guess most people will be staying on generic with the current mapping | 17:04 |
| cjwatson | my opinion at the moment is that we should have generic on the alternate/desktop CD and pae as a network option; for server, possibly pae on the cd | 17:04 |
| cjwatson | since that maps reasonably to what we're doing at the moment | 17:04 |
| apw | we can perhaps just recommend they consider it? | 17:04 |
| cjwatson | and I'm concerned about performance claims regarding pae | 17:04 |
| rtg | cjwatson: in the past the server booted an non-pae kernel, but installed a pae kernel. is that still gonna be the case? | 17:05 |
| cjwatson | (for general use) | 17:05 |
| lool | So enabling PAE at runtime is definitevely ruled out even in light of the space constraints? | 17:05 |
| cjwatson | lool: I asked ... | 17:05 |
| cjwatson | nobody has a working patch for PAE alternatives yet though. Kyle apparently started one a while back | 17:05 |
| apw | there is no working patches to do that at th emoment | 17:05 |
| cjwatson | rtg: that could be changed if you reckon it's important | 17:05 |
| rtg | cjwatson: it seems like you should boot the kernel you're gonna install | 17:06 |
| cjwatson | the problem with the server CD is not so much that as the fact that it installs a PAE kernel unconditionally and doesn't tell you that it won't work until you reboot | 17:06 |
| cjwatson | rtg: I can't make that a hard guarantee; I agree it's nice when possible | 17:06 |
| rtg | cjwatson: ok | 17:06 |
| rtg | slangasek: no more kernel topics from me. | 17:07 |
| cjwatson | I've generally tended to think that the installer should use a fairly permissive kernel in terms of CPU requirements, so that it can be flexible about what it installs if you're not up to scratch | 17:07 |
| cjwatson | not that I've extended this to using the 386 kernel across the board or anything :) | 17:07 |
| pgraner | slangasek: nothing else from kernel... | 17:09 |
| slangasek | anyone else have questions for the kernel team? | 17:09 |
| slangasek | [TOPIC] Foundations team | 17:09 |
| MootBot | New Topic: Foundations team | 17:09 |
| slangasek | cjwatson: heya | 17:09 |
| cjwatson | righto | 17:10 |
| cjwatson | we have the traditional big chart at https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Karmic | 17:10 |
| cjwatson | traffic light colours are pending resupply from the shop but should arrive soon | 17:10 |
| slangasek | [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Karmic | 17:11 |
| MootBot | LINK received: https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Karmic | 17:11 |
| cjwatson | https://blueprints.edge.launchpad.net/ubuntu/karmic/+specs?searchtext=foundations-karmic- is a not completely unreasonable list, but unfortunately we weren't entirely consistent about spec names so there are some things listed off that; the wiki page is more complete | 17:11 |
| cjwatson | s/listed/missing/ | 17:11 |
| cjwatson | as you can see, we have a few drafting stragglers, and a slightly greater number of reviewing stragglers | 17:11 |
| cjwatson | Robbie has gone through doing resource guesstimates and deferrals though, so at this point I believe we're reasonably happy with the combined workload | 17:12 |
| cjwatson | oh, the wiki page also includes some community-assigned specs | 17:12 |
| cjwatson | any questions based on those? | 17:13 |
| cjwatson | of the bugs you listed, one is going to be wrapped up as part of a spec currently targeted for alpha 4, and the other one I'll hoover up before EOD today | 17:13 |
| * slangasek finishes absorbing the prioritizations | 17:15 | |
| slangasek | looks good to me | 17:15 |
| cjwatson | slightly more Essentials than I'm truly happy with, but those are mostly from-above kind of things | 17:15 |
| slangasek | only 4 of which are distro feature things, anyway | 17:17 |
| cjwatson | yes | 17:17 |
| cjwatson | depending on how you count usb-creator for Windows | 17:17 |
| slangasek | :) | 17:17 |
| slangasek | thanks - no other questions here | 17:18 |
| cjwatson | .oO Architecture: mingw | 17:18 |
| slangasek | oh, we'll just make that spec depend on multiarch then | 17:18 |
| cjwatson | for great justifce | 17:18 |
| lool | Eh | 17:18 |
| cjwatson | -f | 17:18 |
| slangasek | [TOPIC] 8.04.3 | 17:18 |
| MootBot | New Topic: 8.04.3 | 17:18 |
| slangasek | wanted to talk just a bit about this today | 17:19 |
| slangasek | http://people.ubuntu.com/~ubuntu-archive/pending-sru.html has the list of packages that are still waiting SRU verification for hardy; we want this list down to zero before the point release to minimize the ISO mastering hassle | 17:19 |
| MootBot | LINK received: http://people.ubuntu.com/~ubuntu-archive/pending-sru.html has the list of packages that are still waiting SRU verification for hardy; we want this list down to zero before the point release to minimize the ISO mastering hassle | 17:19 |
| slangasek | dendrobates: there are a number of server packages on there that aren't getting love; can your team provide some support there? (samba, apache2, openldap2.3) | 17:20 |
| slangasek | (redhat-cluster) | 17:20 |
| dendrobates | slangasek: yes. | 17:20 |
| slangasek | there's also an open-iscsi upload I've done that I want to have kirkland or mathiaz review/validate for me; I'll prod them directly | 17:21 |
| dendrobates | slangasek: ok | 17:21 |
| kirkland | slangasek: on my todo list for today | 17:22 |
| slangasek | hal also needs hardware-specific SRU verification for a Sony Walkman USB device, anyone have one of those? :) | 17:22 |
| slangasek | (or, just general purpose regression testing of hal for hardy) | 17:22 |
| sbeattie | slangasek: the qa team is going to do a testing hug day on monday focusing on 8.04.3 SRU verifications: https://wiki.ubuntu.com/Testing/UbuntuTestingDay/20090622 | 17:23 |
| slangasek | oh, great :) | 17:23 |
| sbeattie | in part to tease out some of the hardware specific SRUs if we can. | 17:23 |
| slangasek | in that case, we probably want good test cases in all of the SRU bug reports | 17:23 |
| pitti | for many of those, regression testing actually is more important | 17:24 |
| slangasek | ...which we don't always have, today | 17:24 |
| pitti | it doesn't help if a bug is confirmed to fix hw on a particular system, but break another | 17:24 |
| slangasek | sure | 17:24 |
| pitti | right | 17:24 |
| pitti | I tried to say | 17:24 |
| pitti | testing new versions on any hw and telling us "yep, still working" helps a lot | 17:24 |
| heno | we'll also run install tests on all the cert hw as soon as we have test images | 17:25 |
| slangasek | I should have those up Monday | 17:26 |
| slangasek | (unless someone else has time to get them up before then) | 17:26 |
| heno | ok, great | 17:26 |
| sbeattie | fader: think we can get those going on monday, when they come up? | 17:26 |
| fader | sbeattie: Yes, we should be able to do that. If it doesn't get picked up automatically I can always start the tests by hand, so one way or the other we'll get them. | 17:27 |
| === ejat is now known as e-jat | ||
| sbeattie | fader: excellent, thanks. | 17:27 |
| slangasek | that's all I have on the 8.04.3 front; anything else? | 17:27 |
| slangasek | [TOPIC] AOB | 17:28 |
| MootBot | New Topic: AOB | 17:28 |
| slangasek | I'll take that as a no | 17:28 |
| slangasek | #endmeeting | 17:28 |
| MootBot | Meeting finished at 11:28. | 17:28 |
| slangasek | thanks, folks | 17:28 |
| pitti | thanks everyone | 17:29 |
| heno | thanks! | 17:29 |
| pitti | slangasek: just to confirm, I won't allow new hardy-proposed stuff without your explicit consent | 17:29 |
| slangasek | pitti: ok, thank you :) | 17:29 |
| pitti | slangasek: with hardy being out for more than a year, there can hardly be so urgent issues right now | 17:29 |
| === rickspencer3 is now known as rickspencer3-afk | ||
| === fader is now known as fader|lunch | ||
| === fader|lunch is now known as fader | ||
| === mikrox is now known as mikro | ||
| === Quintasan_ is now known as Quintasan | ||
| === kirkland` is now known as kirkland | ||
| === rickspencer3-afk is now known as rickspencer3 | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!