=== swoody_ is now known as swoody === Raidsong is now known as Gyro_gearloose === lukjad007 is now known as ShadowChild === ShadowChild is now known as lukjad007 === Gyro_gearloose is now known as Raidsong === lukjad007 is now known as lukjadOO7 === lukjadOO7 is now known as lukjad007 === swoody_ is now known as swoody === dous__ is now known as suodla === asac_ is now known as asac === Zic_ is now known as Guest23819 === juliux_hsv is now known as juliux === dholbach_ is now known as dholbach === Guest23819 is now known as Zic === marjomercado is now known as marjo === fader|away is now known as fader_ === robbiew-afk is now known as robbiew [15:59] * marjo waves [16:00] o/ [16:00] * apw zones in [16:01] * kees waves [16:01] anyone got a copy of the agenda, mine seems to be missing [16:01] * robbiew does the robot [16:01] (I dont have much network and wont stay long anyway) [16:01] * slangasek waves [16:01] * asac__ waves [16:01] * apw asks slangasek for a copy of the agenda [16:01] \o [16:01] sorry, beta work precluded me being able to prepare an agenda in advance [16:02] yo [16:02] oh [16:02] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-10-02 [16:02] oh hey [16:02] hey [16:02] #startmeeting [16:02] Meeting started at 10:02. The chair is slangasek. [16:02] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [16:02] [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-10-02 [16:02] LINK received: https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-10-02 [16:02] robbiew: thank you :) [16:04] [TOPIC] actions from previous meetings [16:04] New Topic: actions from previous meetings [16:04] * cr3 to ensure that the QA team collects and processes feedback about the filebug redirect change [16:04] * cr3, marjo to follow through on netbooks missing from the hw certification lab [16:04] * davmor2 to work with ttx on creating a test plan for eucalyptus [16:05] * pitti to ensure that we have test plans/release notes for all specs [16:05] * lool to ask humanity upstream to prepare a colour revert for bug #430277 ('''Update Below''') [16:05] Launchpad bug 430277 in unr-meta "random icons are colorful while some other notification-area icons are dark" [High,Invalid] https://launchpad.net/bugs/430277 [16:05] * Design team requested that we try to include the work from latest Humanity upstream tree which consists of: [16:05] * updated notification area icons, darker, so that they display nicely on the desktop [16:05] * new Humanity-Dark theme which is Humanity with lighter black and white notification area icons to display nicely under UNR [16:05] If we want this (release team and desktop team should decide too), Loic plans to put the new theme in the same binary package and update the UNR gconf settings in desktop-switcher and unr-default-settings. This is still tracked in LP #430277. The Humanity-Dark theme should "Inherit:" the Humanity theme so the new icons should make a minor difference in binary package size / CD size. [16:05] * slangasek to get linux-ec2 into main for beta ('''Done''') [16:05] * zul to get new ec2-init sorted today [16:05] * smoser to test vmbuilder patch to use germinate ('''Done''') [16:05] * slangasek to follow up with the kernel team wrt ARM, EC2 kernel [16:05] refreshes for beta (done, uploaded over the weekend) [16:05] marjo: cr3 mentioned to me yesterday that there was only one netbook still missing from the cert lab? [16:05] Several changes have been made to the wiki page which users are [16:05] slangasek: I worked with ttx and will again on monday to update [16:05] redirected to in an effort to address issues raised. The QA team is [16:05] also actively monitoring the internet for feedback and issues regarding [16:05] the redirect. We have also been monitoring newly reported bugs to see [16:05] the effect redirection has had. [16:06] slangasek: the netbook has arrived yesterday afternoon and it's been successfully tested [16:06] slangasek: i was going to cover that later [16:06] but, what cr3 said. [16:06] cr3: that's the one mathiaz had to hand though, right? So we've had a test of the hardware, but that unit's not staying in the cert lab? [16:07] pitti not here to comment on test plans [16:07] slangasek: pitti said he followed up by mail on his spec/work-item action ... so thats done. [16:07] slangasek: that was the original plan, but the permanent netbook arrived when mathiaz was actually in the office handing over his own netbook :) [16:07] asac__: ok, thanks [16:07] cr3: ah, heh [16:08] zul: ec2-init is "sorted", I guess? I don't remember the details of that - was that about main inclusion? [16:08] slangasek: yes [16:09] that was about sponsoring changes [16:09] lool: if you don't have much time, should we take up the Humanity discussion later? [16:09] ttx: ok, good [16:09] [TOPIC] QA Team [16:09] New Topic: QA Team [16:10] Karmic Beta Test Report [16:10] 2009-10-02 [16:10] == Test Coverage == [16:10] Image Test Coverage = 100% [16:10] Test Case Test Coverage = 99% [16:10] Alpha 6 Test Coverage = 58% [16:10] === Untested test cases === [16:10] Kubuntu DVD i386 - Ubiquity OEM [16:10] Kubuntu Netbook i386 - Wubi [16:10] === Test Failure Analysis === [16:10] 15 Test Failures [16:10] Failure Rate = 15/194 = 8% [16:10] Alpha 6 Test Failure Rate = 15% [16:11] Testers ran out of time on two untested, otherwise we would have hit 100%! [16:11] == Bugs summary == [16:11] === Summary of Unfixed Issues === [16:11] 38 bugs unfixed [16:11] Critical - 0 [16:11] High - 11 [16:11] Medium - 8 [16:11] Low - 4 [16:11] Undecided - 15 [16:11] === Summary of Fixed Issues === [16:11] 11 bugs fixed [16:11] Critical - 1 [16:11] High - 7 [16:11] Low - 1 [16:11] Undecided - 2 [16:12] BTW, a detailed test report will be available by email [16:12] any questions, so far? [16:13] will we still be able to get coverage of those 2 remaining test cases? even though beta is out, it would be good to get the feedback in advance of final [16:13] slangasek: yes, will work w/ davmor2 & jdridell [16:13] ok, great [16:14] I can kill em [16:14] wubi will most likely fail [16:14] anything else, otherwise the emailed test report will be very detailed [16:14] * slangasek notes that the "failure rate" is a bit misleading, since for most of those tests we also had (sometimes multiple) successful test results [16:15] marjo: I think that's good, thanks [16:15] Particularly in the case of the Kubuntu Netbook Wubi test, since that's never worked. [16:15] scottk: point taken [16:15] ScottK, juet because you didnt try it on armel yet :P [16:15] ScottK: should wubi be removed from the KNE image for final? [16:15] *just [16:16] slangasek: I suspect it will work now. [16:16] It just needs to be tested. [16:16] oh [16:16] well, as well as the rest of wubi anyway [16:16] ok [16:16] Exactly. [16:16] AFAIK this is the first milestone where we got wubi to work at all. [16:17] There were some Alpha 3 KNE specific issues, that I think got resolved and it'd be nice to know for sure. [16:17] given the difficulties in getting wubi working this cycle, I think we need to not wait until the RC to re-test it [16:17] Agreed. [16:17] Unfortunately, I can't test it, so someone else will need to volunteer. [16:17] marjo, cjwatson, davmor2: would it be possible for you guys to coordinate some ongoing testing of wubi with the dailies between now and RC? [16:18] I was going to [16:18] slangasek: yes, will work with them and ara, too [16:18] [ACTION] marjo, davmor2 to coordinate ongoing testing of wubi with the dailies between now and RC [16:18] ACTION received: marjo, davmor2 to coordinate ongoing testing of wubi with the dailies between now and RC [16:18] yep [16:18] some possible fixes were in the post-beta queue that just got flushed [16:18] * slangasek nods [16:19] shall we move on to hw testing? [16:19] slangasek: i didn't see that on the agenda [16:20] [LINK] http://people.canonical.com/~fader/hw-testing/current.html [16:20] LINK received: http://people.canonical.com/~fader/hw-testing/current.html [16:20] let me look quickly [16:20] marjo: true... it ought to be a standing item, but in any case the status looks pretty good [16:20] Laptops: [16:20] passed: 26 (84%) failed: 1 ( 3%) untested: 4 (13%) [16:20] Servers: [16:20] passed: 42 (88%) failed: 0 ( 0%) untested: 6 (12%) [16:20] Desktops: [16:20] passed: 10 (100%) failed: 0 ( 0%) untested: 0 ( 0%) [16:20] slangasek: Sorry dropped off the net [16:20] there's the summary [16:21] yes, it's looking good [16:21] that failure also predates beta (2009-09-17) [16:21] slangasek: My bad -- I retested with the beta but forgot to update the date [16:21] all have bugs and/or RT tickets associated with them [16:21] I'll fix that now [16:21] fader_: still a failure? [16:21] It's the same bug though [16:21] Yep [16:21] fader is tracking all [16:22] marjo, fader_: thanks for staying on top of this [16:22] slangasek: welcome [16:23] marjo: any other concerns from you guys regarding QA for release? [16:23] need to keep on top of outstanding unfixed bugs [16:23] as detailed in the Beta Test Report [16:23] marjo: how are we doing on regressions? [16:24] mdz: last time brian and I ran report, [16:24] it looks like there were over 115 regression potentials vs. same time last release [16:25] http://qa.ubuntu.com/reports/regression/regression_tracker.html [16:25] LINK received: http://qa.ubuntu.com/reports/regression/regression_tracker.html [16:25] marjo: 115 /more/ compared to last time? [16:25] we seem to have quite a few bugs marked as regressions but not triaged [16:25] there are 117 now, can't believe we only had 2 this time last release :) [16:26] slangasek: no, 50+ vs. 115+, therefore more than doubled [16:26] ok [16:26] need to do more analysis; not obvious why [16:27] yes, some more triaging of that list is needed; I'll do some today / next week, is there someone on QA who can help with this? [16:27] perhaps we have more testers [16:27] I wonder if it isn't partly more widespread adoption of the tags [16:27] slangasek: yes, bdmurray can help out [16:27] (I know /I/ tagged more regressions this cycle than last [16:27] [ACTION] slangasek and bdmurray to garden the regression-potential bugs [16:27] ACTION received: slangasek and bdmurray to garden the regression-potential bugs [16:28] i think it's a combination of more testing & more diligent bug reporting, but don't want to jump to conclusions [16:28] thanks for the action item [16:29] slangasek: I can run trough them in my smoke testing and see if they are still valid for you too. [16:31] davmor2: the regressions? I think those are going to be spread out, so would be best handled by dedicated testing [16:31] np's [16:31] anything else on QA? [16:32] [TOPIC] Desktop Team [16:32] New Topic: Desktop Team [16:32] marjo, cr3, fader_: thanks [16:32] so pitti is not here, but he prepared a report [16:32] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus [16:32] [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus [16:32] LINK received: https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus [16:32] on the RC bug front it look ok from what i see [16:33] for triaged ones the modem-manager PUK one is currently in progress upstream [16:33] empathy bug is making progress according to kenvandine [16:33] for the needs understanding bugs kenvandine also said he had some ideas on the empathy crash [16:34] i will remove the firefox XID one from release team radar [16:35] the critical battery action not triggered bug is assigned to pitti, so i think it will make progress soon [16:35] on the networking one i have something about ath9k that scares me a bit. [16:35] bug 439723 [16:35] Launchpad bug 439723 in linux "ath9k - nm-applet don't connect to any network after 2 hours (+-)" [Undecided,Confirmed] https://launchpad.net/bugs/439723 [16:35] For 438445, we've decided to go back to the upstream approach. The current patch (even if it was working consitently OK) is socially very problematic with upstream (we asked, they said don't do it that way, and then we did anyway). [16:36] do you think bug 428920 might be a desktop issue? it looks like an X failure to me [16:36] Launchpad bug 428920 in Ubuntu Karmic "Karmic boot hangs before login" [Critical,Incomplete] https://launchpad.net/bugs/428920 [16:36] seems like we are having regressions for old ath9k chips ... but i am currently trying to understand how common those are [16:37] cjwatson: hmmm ... not sure. i will check with tseliot [16:37] thanks [16:37] Kubuntu? [16:38] it wasn't clear from the log, there's just "Backtrace:" at the end but no actual backtrace :) [16:38] Riddell: yes. please comment on the kubuntu status [16:38] but that made me suspicious [16:38] Kubuntu Beta was in reasonable beta quality shape [16:38] the issues on my radar for final are.. [16:38] * Some kcontrol modules missing translations [16:38] * KDM/ksmserver hangs on logout [16:38] * KPacakgeKit broken probably due to policykit crash [16:38] * "tech-preview" warning to be added to kubuntu netbook ubiquity [16:38] * microblog applet broken [16:38] I need to find the bugs for those and make sure they're milestoned [16:39] but I'm optimistic it's all do-able for final [16:39] [ACTION] Riddell to find bugs for kubuntu release issues and make sure they're milestoned [16:39] ACTION received: Riddell to find bugs for kubuntu release issues and make sure they're milestoned [16:39] :) [16:40] oh and upgrade from hardy [16:40] mvo needs to do something to make that possible [16:40] which he says should be fine [16:42] * Riddell done [16:42] probably not critical for karmic, as long as the upgrade path is sorted in time for Lucid? [16:42] slangasek: It is critical for karmic [16:42] (otherwise, folks can go hardy->jaunty->karmic) [16:42] oh? [16:42] ok then [16:42] well Kubuntu Hardy is just about to lose support [16:42] Hardy Kubuntu is EOL [16:42] I thought there was a working upgrade path already via jaunty [16:43] there is that but well, karmic is infinately better than jaunty, it connects to networks for one thing [16:43] [ACTION] slangasek to look at possible Kubuntu-only EOL announcement for 8.04 [16:43] ACTION received: slangasek to look at possible Kubuntu-only EOL announcement for 8.04 [16:43] Riddell: mm, right [16:43] ok [16:43] anything else on the desktop? [16:43] DX? [16:44] go ahead [16:44] [TOPIC] DX Tem [16:44] New Topic: DX Tem [16:44] [TOPIC] DX Team [16:44] New Topic: DX Team [16:44] The summary is at: https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicReleaseStatus [16:44] [LINK] https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicReleaseStatus [16:44] LINK received: https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicReleaseStatus [16:44] in particular for the detail of the updated packages, see https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicWeeklyReleases (thanks kenvandine) [16:44] of note this week [16:44] notify-osd 0.9.23 bug fix release; warning: that release triggers a temporary regression with a gpm patch that is still queued for karmic [16:45] # bug fix releases of libindicate, indicator-messages and indicator-session (crasher - #436181 in particular) [16:45] # dbusmenu: nasty ordering bug (#430904) in the works, planned for next week [16:45] reverted indicator-session to not show the user list sub-menu because of a regression in gdm (#438720) [16:45] new xsplash fixing a release blocker (#439059) (thanks robbiew and all those who helped narrow down the issue) [16:46] * ogra noticed also a commit that fixes the horribly distroted graphics on 16bpp for xsplash :) [16:47] we have a couple of milestoned bugs that we're on; still some crashers [16:47] and yes, a fix for the 16bpp bug ;) [16:48] questions? [16:49] none here [16:49] davidbarth: do you need help on the gpm patch that is still queued? does that need some work or sponsoring? [16:49] anyone else? [16:50] asac__: yes, if you can speed that up, that will limit the temp. regression; that's really minor though [16:50] ok. lets talk after meeting in -desktop [16:50] asac__: ok [16:50] [ACTION] asac__ to follow up on notify-osd/gpm regression [16:50] ACTION received: asac__ to follow up on notify-osd/gpm regression [16:51] [TOPIC] Mobile Team [16:51] New Topic: Mobile Team [16:51] asac__, davidbarth: thanks [16:51] [link] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Karmic [16:51] - [16:51] * UNR: icons were discussed with upstream, upstream wants some additional changes to the themes (more details in the report above and in Loïcs mail exchange with release and desktop team) [16:51] * moblin: still unstable, work going on, more merges [16:51] * armel: [16:51] LINK received: https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Karmic [16:51] - various new kernel bugs showed up on imx51 during beta testing [16:51] - dove images went through beta fine [16:51] - openoffice breakage seems to be actually toolchain breakage, being fixed by doko atm [16:53] icons> I understand that lool is under some significant pressure to accept a new upstream drop of the humanity package [16:53] right, thats how i understood his mail [16:53] just as a reminder, the artwork freeze is in effect - we should not be taking batch drops of new themes that aren't related to specific bugfixes at this point in the cycle [16:54] ogra: I still doubt it ... but the upcoming upload works around it [16:54] yeah, i should have written "being worked on" :) instead of "fixed" [16:54] The new icons are also needed to have a good experience with the Dust theme (which is currently broken because it tries to use Human) [16:55] even the suggestion of bundling the new dark theme in the existing binary package is problematic, given that the existing theme is a 1.6MB package [16:55] yeah, its graphics ... [16:55] usually not small [16:56] Amaranth: I understand, but we need to find a solution that's consistent with where we are in the release cycle and doesn't introduce significant risk of regressing for release [16:56] (new icons are 30K when compressed with bzip2) [16:57] it replaces all notification area icons as i understand it [16:57] I'll follow up with lool about this on Monday, but I just wanted to make sure the release manager's position on this was clear that this needs to go through the proper freeze procedures, since lool seems to be quite uncomfortable with what's being proposed [16:57] Right, it replaces the current monochrome notification area icons with lighter versions [16:58] slangasek, he also asked to possibly note opinions on the bug [16:59] ogra: as for armel - a number of kernel bugs that had been milestoned to beta for armel got deferred to final; I wasn't overly bothered at doing this given our current target audience for armel, but is there anything blocking us on getting these fixed with time to spare for final? [17:00] kernel freeze is coming soon [17:00] slangasek: I may be able to free 1.7MB (gzip compressed) on the CDs [17:00] well, some have patches that arent getting ,merged and a package upload for imx51 is pending i was told ... as well that amit is on holiday next week [17:01] doko_: thanks - as usual, will take everything we can get :) [17:01] slangasek, i agree, its very close and i'd really like to see more progress especially for imx51 ... [17:01] Amaranth: uncompressed size also matters in the case of liveCDs, btw - but it's good to know these shouldn't have a serious impact on ISO size; if you could add that information to the bug, that would be helpful [17:01] ogra: "aren't getting merged" - why not? [17:02] Will do [17:02] pleanty of these bugs are open since quite some time [17:02] disagreements about correctness? lack of time? [17:02] the latter is my suspicion [17:02] the fix for missing sound support is there since two weeks or so [17:02] that's bug #420447? [17:02] ogra, if you can summarise what is pending that would help, we have a heap of bugs over hear [17:02] Launchpad bug 420447 in linux-fsl-imx51 "no sound devices on babbage board with linux-image-2.6.31-100-imx51" [Medium,Triaged] https://launchpad.net/bugs/420447 [17:03] apw, thats what my report does :) [17:03] right, this one definately has a patch ... not sexy but will at least give us sound support [17:04] my prob is that i couldnt test a single audio app for the whole release yet [17:04] which very likely will produce subsequent bugs once i can [17:05] sounds like kernel and ogra need to interlock more directly, as 'in my report' isn't getting them onto my radar [17:05] ogra: could I ask you to send apw a summary by email of the items you believe currently have merges outstanding for kernel? [17:05] yeah that would help me a lot [17:05] yes [17:06] apw, i'll contact you on monday [17:06] ogra, probabally to the kernel-team list would be good, cc: me too so i don't miss it [17:06] sounds good [17:06] [ACTION] ogra to email apw the list of armel kernel bugs for which merges are outstanding [17:06] ACTION received: ogra to email apw the list of armel kernel bugs for which merges are outstanding [17:06] apw, also, is there someone taking amits role wrt imx51 during his holiday ? [17:06] given the freeze is so near and we have so many opens ? [17:07] ogra, i am not sure who, but someone must be looking over it [17:07] after it ... get the info to the list and i'll bounce on people to find out who is going to look after it [17:07] i dont mean outstanding merges but the open bugs [17:08] apw: separately, https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.searchtext=linux-fsl-imx51&milestone=12698 should be on the radar of someone on the kernel team for final [17:08] ogra, how big is the audience for this platform? imx51 ? [17:09] apw, no idea, how does that matter ? [17:09] its an arch we commited to [17:09] and i expect that it is supported as well as the others [17:09] for prioritising reasons, we arn't likely to close every bug, so we need to know where to put our effort [17:10] out of 19 bugs being tagged armel atm 10 are imx51 kernel bugs [17:10] indeed, i dont expect all bugs to get closed [17:10] as i dont expect all bugs being closed on my i386 laptop [17:10] so knowng how big a slice of our affected userbase they are helps us prioritise them in with our others [17:11] apw: I think at this point you should have all the information needed to track the outstanding issues, correct? So informed decisions about delivery/deferral can be made offline? [17:11] right, no need to exted the meeting with this [17:11] indeed so [17:11] *extend [17:12] [TOPIC] Kernel Team [17:12] New Topic: Kernel Team [17:13] .. [17:13] Overall kernel team status is summarised at the URL below, including the bugs called out in the agenda. We seem to be seeing the start of the flow of bugs resulting from wider beta testing: [17:13] [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic [17:13] LINK received: https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic [17:13] We have started receiving and integrating 2.6.31.x stable updates, some 90 patches in the first batch with another 120 or so in .2 due around now. Futher work has been committed to work round some recurring brightness issues. As have a number of i915 updates for new hardware. [17:13] All of the items which impact the distro release schedule remain basically complete, the arm branches are now up to date and basically working, bugs being worked as normal, integration is deemed complete there. We continue to focus on regression-potential bugs, including focusing this weeks bug day on new bugs. [17:13] (modulo the discussion here on imx51 status) [17:14] .. === asac_ is now known as asac [17:16] slangasek: 1 test left [17:16] 395358> fwiw, that summary is wrong, the hotkey should not be handled by the kernel as a "hw kill" at all... [17:18] slangasek, though the key is connected to the HW at the acpi level and is making your bluetooth appear and dissappear at the hardware level, right? [17:18] apw: "another 120 or so" - how well do these things seem to be converging? [17:18] apw: no, it's connected to the HW *by the kernel* [17:18] apw: this hotkey never does *anything* in ACPI; this is entirely a kernel regression that it's now toggling everything [17:18] sorry if that wasn't clear [17:19] i thought it was toggling everything by toggling the sw rfkill and in parallel the hw rfkill was toggling in the right sequence at least as evidenced for bluetooth [17:19] leading to bad overall semantics [17:19] that's entirely new behavior in karmic [17:20] right as sw kill didn't exist at all [17:20] before karmic ... [17:20] I believe the kernel is force-detaching the device; it's not done by ACPI [17:20] anyway, we can discuss that offline [17:20] ack [17:20] now, as for merging the stable patches [17:20] 120 patches - how soon are these going to land in karmic? [17:20] kernel freeze is 2 weeks away [17:21] and we'll want to leave room for fixing regressions that turn up... [17:21] i am expecting them by weds next week, as they have appeared in the commit emails for stable [17:21] they could be sooner. it is l ikley that is the last of the stable updates we can get in before freeze [17:22] ok; if they slip past next Wednesday, I think we'll want to discuss whether it makes sense to upload them before release, or defer .2 as an SRU [17:22] slangasek, ACK [17:22] anyone have anything else to discuss on kernel? [17:23] [TOPIC] Server Team [17:23] New Topic: Server Team [17:23] apw: thanks [17:23] ttx: hi [17:23] hey [17:24] updated status at: https://wiki.ubuntu.com/ServerTeam/ReleaseStatus [17:24] [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus [17:24] LINK received: https://wiki.ubuntu.com/ServerTeam/ReleaseStatus [17:24] We are also looking at the packages /other/ than Eucalyptus [17:24] to see if there wouldn't be good candidates that we missed sight of === Keybuk_ is now known as Keybuk [17:25] that's good :) [17:25] we also expect more people to test server now that it's beta [17:25] even if traditionally server doesn't get tested that much before release [17:25] * slangasek nods [17:26] we should push some public calls to encourage people to do testing server now [17:26] is there a particular forum where you think that will be effective, other than the places where beta has already been announced? [17:26] or do you think an explicit call for server testing to the same channels is what's needed? [17:26] I think we (team) need to blog about it, so that it shows on server aggregators [17:27] ok [17:27] On the release management front... [17:27] beta still showed some weakness on the UEC/EC2 release automation [17:27] that smoser will work to cover. [17:28] we might need to do some dry runs [17:28] with the release team cooperation [17:28] yes, I would like to work with smoser to get publishing integrated as much as possible with the existing cdimage script suite [17:29] now that we ahve a reasonably working UEC stack we'll also call for testers on that side [17:29] "test it, its easier than it sounds" [17:29] the hardware requirement is the major blocker to that. [17:29] that should help us avoid any fat-fingering at publishing time, as well as getting us prettiness like file descriptions in the index [17:29] yes. Beta should have been the opportunity to do that, but we were late [17:29] slangasek, ttx we've got lots of work to do there. the uec stuff shouldn't be hard, but the ec2 just needs some work. [17:30] it was ec2 that i fat fingered [17:30] that's why I suggest some dry runs now. [17:30] [ACTION] slangasek and smoser to coordinate dry-runs of UEC/EC2 publishing next week, in advance of RC [17:30] ACTION received: slangasek and smoser to coordinate dry-runs of UEC/EC2 publishing next week, in advance of RC [17:31] That's about it on our side... questions, comments, additions ? [17:31] not from me [17:31] https://blueprints.launchpad.net/ubuntu/+spec/server-karmic-ec2-release-process needs to be retargeted [17:32] but I don't have the power to do so [17:32] it should be considered completed when automation is ready. [17:33] that's all from me. [17:33] retargeted [17:33]