=== asac_ is now known as asac === beuno_ is now known as beuno === ianmcorvidae|alt is now known as ianmcorvidae === Saj0577 is now known as saj0577 === saj0577 is now known as Saj0577 [09:35] Is the REVU meeting on now? === fader|away is now known as fader_ === dyfet__ is now known as dyfet [14:00] Meeting? [14:00] * ogra twiddles thumbs [14:00] if you insist. [14:00] hi [14:00] hi [14:01] hi [14:01] * ogra tries to not burn his fingers on the hot kbd ... laptop still building mono [14:02] plars, dyfet: ping [14:02] here [14:03] #startmeeting [14:03] Meeting started at 08:03. The chair is lool. [14:03] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [14:03] [link] https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20090721 [14:03] LINK received: https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20090721 [14:04] [topic] Action Items from July 14th, 2009 [14:04] * plars is here [14:04] I'll skip over # [14:04] NCommander to investigate https://bugs.launchpad.net/ubuntu/+source/vnc4/+bug/338148 (co) [14:04] Ubuntu bug 338148 in vnc4 "Needs new version from Debian: fails to build with removal of mesa-swx11-source" [High,Triaged] [14:04] for now as NCommander isn't around [14:04] GrueMaster: GrueMaster to retest on i386 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/337809 [14:04] Ubuntu bug 337809 in linux "APIC error on CPU 0" [Medium,Triaged] [14:04] co [14:05] New Topic: Action Items from July 14th, 2009 [14:05] [action] (2nd co) NCommander to investigate https://bugs.launchpad.net/ubuntu/+source/vnc4/+bug/338148 [14:05] ACTION received: (2nd co) NCommander to investigate https://bugs.launchpad.net/ubuntu/+source/vnc4/+bug/338148 [14:05] Ubuntu bug 338148 in vnc4 "Needs new version from Debian: fails to build with removal of mesa-swx11-source" [High,Triaged] [14:05] [action] (2nd co) GrueMaster to retest on i386 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/337809 [14:05] ACTION received: (2nd co) GrueMaster to retest on i386 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/337809 [14:05] [topic] changing the form of the meeting: everybody would update its spec's status in the whiteboard and we'd review a page summarizing status [14:05] New Topic: changing the form of the meeting: everybody would update its spec's status in the whiteboard and we'd review a page summarizing status [14:06] I'm voluntarily skipping over Specification Review as it is impacted by this proposal :) [14:06] So I've sent this proposal to the mailing list [14:06] yep [14:06] The idea is basically for everybody to edit the whiteboard of their specs to reflect status [14:06] * ogra gave comments via IRC, sorry for not putting them in mail yet [14:06] Just like for Work items, we'd have a one line summary or couple of lines summary of status [14:07] This would allow generation of an overview page which we would all review during the meeting and then we'd have an open floor for questions [14:07] The goal is to have always available information (not buried in a meeting log) and to skip over the long blueprint pingpong [14:07] ++ [14:08] Opinions? Comments? Reactions? :) [14:08] lool: I didn't see ogra's comments, have there been any objections to this idea raised by him, or anyone else? [14:08] ogra: ^ [14:08] i didnt really understand the purpose when we started discussing it [14:08] the more i thought bout it the more i liked it [14:09] Cool [14:09] I like the idea, personally [14:09] plars: I'm not 100% sure but I think it's the only critic I received [14:09] my initial proposal was to have at least per person status reports only on the items that block you thought [14:09] Which was IIRC "it sounds like additional work and I don't see the point" [14:09] but i think these are not needed [14:09] s/thought/though/ [14:10] right, it's basically just a one line update on a wiki page, similar to what you'd be doing on irc if we still did it in-meeting right? [14:10] lool's proposal as it stands is fine [14:10] So if there are no objections, I propose we add a "Status:" entry to whiteboards; I'll send a mail about that [14:10] though it requires that we actually prapare a bit more [14:10] I like it [14:10] *pre [14:10] [action] lool to send email about Status: in whiteboards [14:10] ACTION received: lool to send email about Status: in whiteboards [14:10] [action] lool to implement script to dump blueprints' statuses [14:11] ACTION received: lool to implement script to dump blueprints' statuses [14:11] As a related topic [14:11] plars, it an entry on the blueprint whiteboard not a wiki page [14:11] [topic] adding work items to all specs which we work on [14:11] New Topic: adding work items to all specs which we work on [14:11] plars, from that a wiki status page can be generated [14:11] davidm: I see now, from lool's later comments :) [14:12] lool, shouldnt that be an action instead of topic ? :) [14:12] plars: Right, sorry, I went a bit fast; it's like Work items: on https://blueprints.launchpad.net/ubuntu/+spec/mobile-karmic-armel-toolchain [14:12] So on this new topic, I'd like to ask everyone to please update or add Work items: to their specs [14:13] Currently the burndown chart isn't terribly useful because it only works with a subset of the specs/work items which we really want to track [14:13] These are the errors I currently get from the cron http://paste.ubuntu.com/223547/ [14:14] Some specs should be clarified and are not really ours (e.g. hw-emablement or mid-karmic-use-mer) in which case I'll drop them from the list [14:15] mobile-arm-karmic-offline-installer-gui has workitems [14:15] * ogra sonders what he did wrong [14:15] So you have an empty line [14:15] ah, right [14:15] fix your script :P [14:15] The format should be "Work items:" and then one work item per line directly afterwards [14:16] ogra: No, it could be anything after the Work items [14:16] Also format of work items should be "Froble with foobar: TODO" or DONE or DEFERRED [14:16] fixed for this spec [14:17] lool: For future reference it would be nice to have a document specifying the format you would like to have, instead of coming back and saying we need to fix the specs after we have already written them. [14:17] lool: perhaps, if your email about stus updates could include the format for the rest of it as well, that would be helpful [14:17] s/stus/status [14:17] GrueMaster: that's fair [14:17] GrueMaster: Would you mind picking this up? [14:17] plars: it will; thanks for the suggestion [14:17] No, because I don't know the exact format that your script is looking for. [14:17] It's pitti's script actually [14:18] The format is the one I documented above [14:18] is that script available in bzr somewhere? [14:18] lool: OK. I'll document it. [14:18] it's available publicly [14:18] plars, GrueMaster: http://piware.de/bzr/bin/workitems.py [14:19] the chart generator albeit unrelated is at lp:~rick-rickspencer3/+junk/py-burndown-chart [14:19] The script is called like: [14:19] 03 3 * * * bzr update -q $HOME/bin; $HOME/bin/workitems.py -d data/desktop-workitems.db -r karmic -p 'desktop-karmic-' -m 'https://wiki.ubuntu.com/Kubuntu/Todo/Karmic?action=raw'; $HOME/bin/workitems.py -d data/desktop-workitems.db --csv --to 2009-10-01 | python ubuntu/py-burndown-chart/burndown.py --output=www/www/tmp/desktopteam-burndown-karmic.png -s 300 --height=450 --title='Desktop Team Karmic Burndown' - [14:19] BTW this is the current burndown chart URL http://piware.de/tmp/mobileteam-burndown-karmic.png [14:20] This is hosted on pitti's server for now due to lack of deps on people.ubuntu.com or people.canonical.com [14:20] Any question? [14:20] Ok moving to Specification Review [14:20] [topic] Specification Review [14:20] New Topic: Specification Review [14:21] So hopefully our last pingpong week [14:21] [link] https://blueprints.launchpad.net/~canonical-mobile?show=all [14:21] LINK received: https://blueprints.launchpad.net/~canonical-mobile?show=all [14:21] ogra: Mind updating us on your specs? [14:22] paulliu, plars: I'll give an update on my specs next and then it will be your turn [14:22] subarches in debian cd ... i started fiddling with the renaming on the weekend ... [14:22] but am not done yet, the buildd issues are way to pressing to do any spec work this week until we have sorted that [14:22] so my full focus is on that [14:22] (mesa building atm here in chroot) [14:23] No update on freescale-desktopm easy-rb-mgmt offline-installer-gui and general-resolution-touchscreens? [14:23] i fiddled with a qemu static build that if it enters karmic will speed up rootstock massively [14:23] (this is for offlibe installer gui) [14:23] touchscreens are still not started [14:24] freescale desktop is waiting for HW which i'm supposed to recive soon [14:24] ogra: How's A3 looking WRT freescale/mx51? [14:24] (and indeed for the renaming changes in cdimage/debian-cd) [14:24] well [14:25] given that compiz FTBFS thanks to the 40 KDE packages being stuck on the buildd i'D say very bad [14:25] beyond not having mesa [14:25] It's uninstallable? [14:25] how would it be installable without kernel ? [14:25] I'm speaking of compiz and mesa [14:25] well, the wrong version will be installed [14:26] livefs'es build, images build [14:26] That's better than nothing [14:26] http://cdimage.ubuntu.com/ports/daily-live/20090721/ looks good so far but isnt of much use [14:26] LINK received: http://cdimage.ubuntu.com/ports/daily-live/20090721/ looks good so far but isnt of much use [14:26] ogra: Is it reasonnable to target these two specs for a4? [14:26] yeah [14:26] looks like we will have a working kernel by A4 [14:27] done [14:27] the changes for imx51 arent hard, uboot scripts will be a bit [14:27] but easier if i have HW [14:27] done [14:27] On my own specs, I didn't do any progress on the cloud stuff which I considered lower priority; I want to get something decent started before our sprint [14:28] Concerning the toolchain bits, it's stuck on hardware for buildds as qemu isn't a serious option anymore, sadly [14:28] As soon as v7 buildds are deployed we can bump the toolchain reqs and move on [14:28] qemu-system-arm is way to slow [14:28] paulliu: Could you update us on your specs' status? [14:28] GrueMaster: You're next after plars [14:29] (which is why i went down the -static/binfmt road as well with rootstock) [14:29] Yes. I've request to enable compatible mode in connman packaging. [14:29] So the rest is to add it into our seed and start debugging. [14:29] For app-resolutions sorry I still don't have time to look on that. [14:30] paulliu: Could you add work items to your specs? [14:30] lool: yes. [14:30] paulliu: What do you think are reasonnable delivery milestones for each spec? [14:31] lool: before karmic? [14:31] lool: What do you mean milestones? [14:31] paulliu: alpha 4, 5, 6, beta, rc etc. [14:32] (I just changed the implementation of mobile-unr-karmic-connman to "Started" since you mentionned work on it) [14:32] For connman alpha 5 is good. [14:32] paulliu: I think connman should land before FF [14:32] Ok, let's go for A5 [14:32] lool: yes, the early the better. [14:32] Agreed [14:32] lool: And app-resolution for beta. [14:32] Ok [14:32] Specs updated with milestones [14:33] paulliu: Anything you're blocked on? Need help with? [14:33] lool: it's ok. I'll push the maintainer and/or the upstream. [14:34] paulliu: Thanks [14:34] plars: How are specs going for you? [14:34] mobile-qa-karmic-arm and mobile-qa-karmic-unr now have testplans linked on testcases.qa.ubuntu.com [14:34] have good progress writing checkbox testcases [14:34] * StevenK appears, having lost track of time :-( [14:34] Hi StevenK we're reviewing specs status ATM; could you prepare a couple of lines of summary on the ones you're assigned to? thanks [14:34] some manual (guided) and some automated [14:35] will be syncing up with cgregan and other soon on testcases to see what can be leveraged for each others' benefits [14:35] mobile-unr-karmic-compliance-autotesting is unblocked now, kinda [14:35] The only left is -wubi, which requires me to have more time [14:35] plars: Should some implementation statuses say "Good progress"? Do you have an ETA for delivery of these specs? [14:36] StevenK: After GrueMaster if you don't mind [14:36] Tell me when [14:36] * ogra hands StevenK a bag with some minutes in it :) [14:36] there, time :) [14:36] UNR one is coming along more quickly than arm one, I'd like to have them with something available for use by alpha4, though I fully expect the set of tests to continue to grow after that [14:36] on the compliance autotesting one [14:37] that's the one for application screensize/resolution testsuite [14:37] The bug affecting LDTP that was blocking me on that is not fixed yet, but I've narrowed it down to the changeset [14:37] plars: Ok changed it to good progress and targeted to A5, there's no rush to have it in A4, if we do that's nice [14:37] ok [14:37] this one is lower priority than the other two though [14:38] but the testing benefits the UNR testing overall [14:38] so it's really nice to have [14:38] plars: Do you think beta is a good target for the testcases specs? [14:38] yes, hopefully... I'll have *something* at beta, but I may not have coverage for all apps by that time [14:39] ok updated [14:39] thanks [14:39] GrueMaster: Hola [14:39] GrueMaster: I updated mobile-karmic-lsb-compliance-testing slightly last week; any issue wit hit? [14:39] *it [14:40] morning. I have updated the mobile-karmic-lsb-compliance-testing even more since then. I have added a new work item to move the lsb test results to wiki.ubuntu.com [14:41] GrueMaster: I just merged the two Work items: sections into one [14:41] I will also be testing alpha3 this week as soon as they hit iso.qa [14:41] GrueMaster: Given the nature of it, I'm targetting it for final since you'll effectively deliver the final work items after final [14:42] No, I am targeting moving the test results for this week. [14:42] GrueMaster: Anything else you'd like to raise on the topic of specs? [14:42] GrueMaster: I mean I targetted the *spec* for delivery with final [14:42] Ok, [14:42] Since one work item is to test final [14:43] GrueMaster: Ok thanks [14:43] StevenK: Now would be a good time to update us on your specs :) [14:43] dyfet__: You're next [14:43] he's growing underscores since he joined ... [14:43] on the mobile-unr-karmic-applications, davidm and I had decided to abandon it due to lack of communication from the other players. Since then, I have seen an update on the blueprint (still no email) from Pete asking why. [14:43] assuming i survive connectivity issues... [14:44] Right, -wubi requires more time, which I'll be doing next week [14:44] GrueMaster: Actually repete offered clarifications on this spec; I'm happy to participate in a phone call to help rescue the UNR apps spec [14:44] -translations requiring reviewing and also more time [14:44] Can anyone see a theme? [14:44] StevenK: So you're doing translations after all? [14:44] Pete has also updated the spec wiki to include a new list of applications, which I have been reviewing since last week. [14:45] lool: I did the first step, by moving them to main. [14:45] ok, guess I'm done. sigh. [14:45] I'll be discussing the next steps with dpm tomorrow. [14:45] StevenK: Is there a spec about UNR updates for karmic? [14:45] If you have a phone call about UNR apps, please invite me. [14:45] lool: UNR updates? Why? [14:45] GrueMaster: Sorry, I thought you were done two minutes ago [14:46] I can't type as fast as some of you guys. Especially without coffee. [14:46] StevenK: Because we'll get some UNR drops to push to karmic [14:46] lool: And? They get uploaded as normal, they don't require that much paperwork [14:47] StevenK: Ok; so there are no plans to track karmic's UNR as a spec; I would have found such a spec a better place to document the MIR work for UNR for instance [14:47] I don't mind if you think it can simply happen immediately [14:47] Er, it didn't ... ? [14:47] I'm confused [14:48] StevenK: I'm not tracking UNR plans for karmic closely; I can't comment on the scale of the task [14:48] btw, wasnt there some discussion about the name ? [14:48] does it stay ? [14:48] That's not our call [14:48] (just a question out of interest) [14:48] StevenK: Anything else you'd like to discuss with your specs? [14:49] I can't think of any, I'm not really trying to drive -translations, just prod it to get started. [14:49] StevenK: Could you please update status of poulsbo-packaging and mobile-hildon-input-methods to reflect their current status? (Implemented/deferred/obsolete etc.) [14:50] And having UNR in main was a goal of mine, irrspectively of specs [14:50] (These are not targeted at karmic, but would be nice to get them cleared of your list) === dyfet__ is now known as dyfet [14:50] And translations, etc, etc, handwave [14:50] StevenK: That's alright [14:50] StevenK: What's the expected delivery milestone for mobile-unr-karmic-wubi? [14:51] lool: It was supposed to be alpha 3, but I suck [14:51] Now alpha 4 [14:51] * ogra doesnt ask for armel support this week :) [14:51] I made it Alpha 4 thanks [14:51] GrueMaster: Getting back to you, since I skipped too fast to StevenK [14:51] GrueMaster: Anything else you'd like to discuss WRT specs? [14:51] What more can I add? I only have the two, and one has been silently killed off. [14:51] GrueMaster: I'm available if you'd like help clarifying/resucing the UNR apps/seed spec with repete [14:52] I think it's unfair to call it silently killed off [14:52] I really don't even know what I am supposed to do with that spec. I only offered to help stevenk with the writeup after UDS. I'm not sure what direction it is supposed to go in. [14:53] I think it was trying to cover too many things at once and was a bit of an undocumented/unclear list of changes as a result [14:53] It was silently killed off because no one was responding to my email inquiries. [14:53] If you or StevenK have some genuine interest in getting some of this stuff in karmic, let us work with repete to clarify it [14:54] I think we could have an efficient phone meeting to kick it off again [14:54] GrueMaster: Ok; let's chat about this off meeting if you don't mind [14:55] dyfet: How are you doing with specs? [14:55] we are almost out of time [14:55] well...with the lxde spec, we had community elections for packages to have in the lubuntu seed... [14:56] dyfet: So you have a clear plan? [14:56] yes [14:56] dyfet: What the expected delivery milestone? [14:57] dyfet: alpha 6? [14:57] It's the latest we can add flavours IMO [14:57] well, it was a low priority spec, but we could target before a6 :) [14:57] Ok I made it alpha 5 [14:57] lool, it wont be a flavout [14:57] but please add work items to the spec [14:57] *r [14:57] only a seed and metapackage [14:57] Ok [14:57] dyfet: anything else? [14:57] yes, I kept your notes from earlier on work item comments :) [14:58] not related to specs...waiting for hw today though [14:58] Ok done with specs then [14:58] [topic] ihgh prio bugs [14:58] New Topic: ihgh prio bugs [14:58] Depends if you want things like CD builds [14:58] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-unr [14:58] StevenK: That one would be for you [14:58] And before FF is MUCH better [14:58] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-armel [14:58] [link] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-unr [14:58] LINK received: https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-unr [14:59] StevenK: Can you push the new webfav soon? [14:59] * StevenK waves his arms furiously [14:59] We're running out of time; if people have other commitments they are welcome to go attend; I think we will be done in 5 to 10 mns [14:59] I only have so much time :-( [14:59] lool: I'm trying [15:00] StevenK: I don't need it next week, but ff3.5 is a karmic goal [15:00] bfiller said it was a one line change though :) [15:00] lool: I'm well aware, but there are other things wrong with webfav, which need addressing [15:00] StevenK: Ok; I'm noting that you don't have much time but will look into it in a near guture [15:01] *future [15:01] StevenK: ack [15:01] [link] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-armel [15:01] LINK received: https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-armel [15:01] dyfet: What about banshee? This bug has been open in a long while [15:01] dyfet: It would be nice to get some debug action :) [15:01] I know...I had not been able to get banshee to run far enough to hit that failure on arm [15:02] what HW do you have atm ? [15:02] I just assigned myself to the ffmpeg ARM opts bugs 383240 [15:02] Launchpad bug 383240 in ffmpeg "Integrate and enable ARMv5TE/v6/VFP and NEON optimisations from ffmpeg trunk for armel" [Undecided,New] https://launchpad.net/bugs/383240 [15:02] well, there is the b1....and the marvell board I cannot run X on and that has an ancient kernel... [15:03] ffmpeg looks like it will only work if we compile with --cpu=armv7-a [15:03] dyfet: What's wrong with the B1? [15:05] when I try it on the b1, I get a failure in dbus init in banshee long before it gets to anything else... [15:05] you try to run it remotely ? [15:05] that wont work [15:05] banshee checks for a local session dbus [15:05] ogra: Could you help dyfet get moving on this bug? [15:06] yes [15:06] dyfet: Please bring up such issues before we discover them in the meeting; you could document them in the bug or raise them to us on IRC any time :) [15:06] I think it is something simple...and I was expecting to get new hw today also [15:06] Ok; moving to low prio bugs [15:06] There are way too many bugs to review [15:07] plars, GrueMaster: Could you guys help us deal with the now larger lists of bugs? [15:07] [link] https://bugs.launchpad.net/~canonical-mobile [15:07] LINK received: https://bugs.launchpad.net/~canonical-mobile [15:07] * ogra notices thats a reoccuring sentence lool emits every release cycle [15:07] I wish these be triaged into armel / UNR / other bugs [15:07] lool: I plan to spend some omre time triaging today [15:07] [link] https://bugs.launchpad.net/~ubuntu-unr [15:07] LINK received: https://bugs.launchpad.net/~ubuntu-unr [15:07] and [15:07] lool: I could use some help on it [15:07] [link] https://bugs.launchpad.net/~ubuntu-armel [15:07] LINK received: https://bugs.launchpad.net/~ubuntu-armel [15:08] GrueMaster: Could you help plars triaging these? [15:08] Looking now. [15:08] GrueMaster: As well as New bugs against UNR packages [15:08] lool, hmm, your list has fix released bugs in it [15:08] it's not hard, just can be tedious... but the main thing at the moment is to get bugs figured out whether they are specific to ARM/UNR or not, and if so, subscribe them to the appropriate team... if not, remove the tag [15:08] How do you want me to go about armel bugs without a working image? [15:08] bug 390591 is surely not affecting karmic [15:08] Launchpad bug 390591 in mono "mono segfaults on ARM" [Medium,Confirmed] https://launchpad.net/bugs/390591 [15:08] GrueMaster: you don't need a working image for the most part on this, and UNR is the one that needs the most attention [15:09] plars, GrueMaster: What I'd love for the other lists would be bugs without any Undecided/Unknown prio and in state Confirmed or Triaged [15:09] general triaging would be useful too of course, but getting the bugs identified correctly is a big part of that [15:09] ogra: it's targetted at jaunty, which we still support [15:09] right [15:09] Ok; we had a long meeting already [15:10] i thought NCommander wanted to make a backport request [15:10] GrueMaster: I'll get with you about it later [15:10] Bug #345126 has been release-noted [15:10] I think a week wont be enough to triage all these but we should revisit next week [15:10] Launchpad bug 345126 in ubuntu-release-notes "Installer on UNR image creates too small swap partition" [Undecided,Fix released] https://launchpad.net/bugs/345126 [15:10] [topic] AOB [15:10] New Topic: AOB [15:10] This is a chance to discuss any other important business? [15:10] none, close .... [15:11] Crap there was something I wanted to mention but I forgot about [15:11] Lucky you [15:11] Ok thanks a lot folks [15:11] #endmeeting [15:11] Meeting finished at 09:11. [15:12] heh [16:00] o/ [16:00] o/ [16:00] yo [16:00] * mathiaz waves [16:01] let's get the Ubuntu Server team meeting started [16:01] #startmeeting [16:01] Meeting started at 10:01. The chair is mathiaz. [16:01] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [16:01] o/ [16:01] Today's agenda: https://wiki.ubuntu.com/ServerTeam/Meeting [16:02] thanks ttx for running the meeting last week [16:02] ttx: and publishing the minutes [16:02] * stgraber waves [16:02] you're welcome. [16:02] Last week minutes: https://wiki.ubuntu.com/MeetingLogs/Server/20090714 [16:02] [TOPIC] # [16:02] SRU tracking on server-related packages. [16:02] New Topic: # [16:03] [TOPIC] SRU tracking on server-related packages. [16:03] New Topic: SRU tracking on server-related packages. [16:03] ttx: what's you proposal on this subject? [16:04] We need to better track Server-related SRU candidates. Basically monitor the development release updates for changes that could make sense in previous releases [16:04] to define where we want to use our resources to push them to completion. [16:05] So someone could monitor the list, look up the changes and list relevant ones on a wikipage. They would get discussed at the team meeting [16:05] I would be willing to help in that effort. [16:05] once approved, we would assign them to the ubuntu-server team and make sure they pass the process. [16:05] ttx: in my experience SRU candidates are mainly coming from bugs [16:05] I currently look through the SRU list for updates relevant to servers, mainly for LTS releases though as we mainly use LTS builds. [16:05] mathiaz: yes. [16:06] ttx: I'm not sure that monitoring karmic-changes would help [16:06] ttx: the problem we're trying to solve is to get more SRU completed or to identify more candidates for SRU? [16:07] mathiaz: I would say, to make sure we SRU all relevant bugs [16:07] and give a forum where their appropriateness would get discussed [16:07] ttx: right - so I'd rather focus on the ubuntu-server-bugs mailing list then [16:07] but you're right that -changes monitoring is not enough. [16:07] ttx: it seems that karmic-changes is to noisy [16:07] * kirkland cheers ttx on [16:07] We need to catch all FixReleased. [16:08] ttx: agreed - for a specific list of packages (relevant to the server team) [16:08] Does a list of packages relevant to the server team exist? [16:09] (Or is it just common sense?) [16:09] Omahn: https://bugs.launchpad.net/~ubuntu-server/+packagebugs [16:09] sbeattie: how do yo track relevant SRU bugs? [16:10] sbeattie: is there a process in the bug team to track which bugs are currently under an SRU process? [16:10] That doesn't mean we'll do a lot more SRUs, just give some confidence that we are not missing anything important. [16:10] ttx: ok - so there is already a list of bugs that are targeted for SRU [16:10] ttx: what's we're trying to achieve here is to get more relevant bugs on that list? [16:11] mathiaz: you mean the bugs nominated for a release ? [16:11] ttx: yes [16:12] ttx: if someone thinks a bug should be fixed in a stable release, one of the first step is to nominate that bug for the target release [16:12] Basically I want to find a way to have a team discussion on what nominated bugs should be approved. [16:13]