/srv/irclogs.ubuntu.com/2007/12/19/#ubuntu-meeting.txt

=== bigon is now known as bigon`
=== Mamarok is now known as markey
=== j_ack_ is now known as j_ack
=== asac_ is now known as asac
krautmoin07:36
=== ubotu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 19 Dec 19:00 UTC: QA Team meeting | 20 Dec 14:00 UTC: Desktop Team Development | 21 Dec 12:00 UTC: MOTU meeting
=== ubotu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 19 Dec 12:00 UTC: Edubuntu meeting | 19 Dec 19:00 UTC: QA Team meeting | 20 Dec 14:00 UTC: Desktop Team Development | 21 Dec 12:00 UTC: MOTU meeting | 02 Jan 12:00 UTC: Edubuntu meeting | 09 Jan 20:00 UTC: Edubuntu meeting
=== bigon` is now known as bigon
=== dholbach_ is now known as dholbach
=== ubotu changed the topic of #ubuntu-meeting to: Current meeting: Edubuntu meeting Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 19 Dec 19:00 UTC: QA Team meeting | 20 Dec 14:00 UTC: Desktop Team Development | 21 Dec 12:00 UTC: MOTU meeting | 02 Jan 12:00 UTC: Edubuntu meeting | 09 Jan 20:00 UTC: Edubuntu meeting
=== \sh_away is now known as \sh
zul@schedule now14:27
zul@schedule utc14:28
ubotuSchedule for Etc/UTC: Current meeting: Edubuntu meeting 19 Dec 19:00: QA Team meeting | 20 Dec 14:00: Desktop Team Development | 21 Dec 12:00: MOTU meeting | 02 Jan 12:00: Edubuntu meeting | 09 Jan 20:00: Edubuntu meeting14:28
zul@now14:28
ubotuCurrent time in Etc/UTC: December 19 2007, 14:28:35 - Current meeting: Edubuntu meeting14:28
zulsorry14:28
=== ubotu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 19 Dec 19:00 UTC: QA Team meeting | 20 Dec 14:00 UTC: Desktop Team Development | 21 Dec 12:00 UTC: MOTU meeting | 02 Jan 12:00 UTC: Edubuntu meeting | 09 Jan 20:00 UTC: Edubuntu meeting | 10 Jan 14:00 UTC: Desktop Team Development
=== cjwatson_ is now known as cjwatson
=== _czessi is now known as Czessi
=== \sh is now known as \sh_away
=== Keybuk_ is now known as Keybuk
=== ubotu changed the topic of #ubuntu-meeting to: Current meeting: QA Team meeting Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 20 Dec 14:00 UTC: Desktop Team Development | 21 Dec 12:00 UTC: MOTU meeting | 02 Jan 12:00 UTC: Edubuntu meeting | 09 Jan 20:00 UTC: Edubuntu meeting | 10 Jan 14:00 UTC: Desktop Team Development
* pedro_ waves18:59
* heno waves18:59
* liw waves18:59
* nand waves18:59
pedro_hi all :-)18:59
* somerville32 waves.18:59
* ogasawara waves19:00
* bdmurray tries to think of something other than waving to do19:00
* somerville32 jumps on top of bdmurray 19:00
* nand throws snowballs19:00
henobetter start before a fight breaks out19:00
henowelcome all!19:01
heno#startmeeting19:01
MootBotMeeting started at 19:01. The chair is heno.19:01
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]19:01
heno[TOPIC] Testing wiki cleanup day - suggestion from stgraber to follow up on Davmor2's new testing page19:01
MootBotNew Topic:  Testing wiki cleanup day - suggestion from stgraber to follow up on Davmor2's new testing page19:01
henoI don't think either of them are here19:01
nand<stgraber> nand: I won't be there :(19:02
bdmurrayIt sounded like a good idea to me19:02
henoyep, we just need to pick a day19:02
henoThurs. Jan 3rd?19:03
liwok by me19:04
heno(to not conflict with a bug day)19:04
henook, let's go with that19:04
heno[AGREED] QA Wiki cleanup day will be Jan 3rd 200819:05
MootBotAGREED received:  QA Wiki cleanup day will be Jan 3rd 200819:05
heno[TOPIC] qa-hardy-list discussion19:05
MootBotNew Topic:  qa-hardy-list discussion19:05
henothe list has about 120 bugs ATM19:05
henobtw, agenda with links: https://wiki.ubuntu.com/QATeam19:06
pedro_https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=qa-hardy-list19:06
henoThe purpose of this list is a recommendation from the Canonical QA team to the distro team for what they should focus on19:07
henoI would ask that community members not add items to that list directly, but please do make suggestions19:07
henoIt will to some degree determine the use of Canonical-paid time, so it makes sense to filter it in that way IMO19:08
henoAt the same time, it's not hidden in any way19:09
henoSo, with that out of the way, any comments on the contents?19:09
ogasawaraI assume we should go through and triage any which still need Importance/Status set19:09
henowe should19:10
liwimportance isn't enough to tell distro team what to work on first?19:10
henothere are just too many I think19:10
henoand importance mainly shows the severity of the bug19:11
bdmurrayAre they all verified in Hardy?19:11
ogasawarabdmurray: I don't think so.  it would be good to verify if the issue is still present with Alpha219:11
henowhile a Low bug with 100 subscribers that's been around for 2 years might be good to fix now19:11
henoeven if it's only a rendering glitch or something19:12
henoin fact devs should work on High priority bugs as well; this is a supliment to that lisy19:12
ogasawaraheno: the one hurdle I see there is that some of those reports that span many releases often grow wildly out of control and deviate from the original report19:12
henoraising other issues on the radar19:12
henoogasawara: what can we do about that? Distill the remaining issue in a new bug and dupe the old one to the new, cleaned up one?19:13
henoI have added some messy bugs to the list myself19:14
bdmurrayLooking at the list the 120 number isn't right19:15
ogasawaraheno: that might help and at least give us a fresh starting point19:15
bdmurraySome show up more than once19:15
pedro_yeah there's a few of them with more than one task.19:15
bdmurrayin regards to messy bugs I think it'd be better to clear up the description19:15
bdmurrayI think that is what it was designed for19:16
henothat list view is very annoying19:16
henoI don't have strong feelings about that19:16
henowhat bdmurray says is the traditional way of doing it though19:17
henoPerhaps we should use some markup to show that a description has been enhanced in that way19:17
stgraberhello19:18
stgraberI can sort of follow the meeting19:18
heno*** SUMMARY *** for example19:18
bdmurrayIs "This description was updated" not enough?19:18
stgraber(I managed to find an internet connection) :)19:18
bdmurrayheno: that makes sense similar to "TEST CASE" and "WORKAROUND"19:18
henostgraber: we decided on Jan 3rd for wiki day19:18
somerville32heno, sorry to interrupt, but I want to introduce you to sroberts. He is new to the community but he is interested in assisting pull up the slack with Xubuntu QA now that Jim is more busy IRL. :)19:19
henobdmurray: agreed. Just to catch they eye19:19
stgraberheno: ok19:19
henohello sroberts :)19:19
srobertshello :)19:19
somerville32:)19:19
jeromeghey sroberts19:19
bdmurraysroberts: I'd be happy to talk to you after the meeting in regards to bugs if you'd like19:20
srobertsbdmurray: sure19:20
henowe might get some CDs to test late tonight19:20
heno(if not tomorrow)19:20
henoabout the list -- I've gone through Gutsy and Hardy nominations and printing bugs19:21
jeromegsroberts: happy to have some help to triage xubuntu bugs19:21
henoI'm now looking at high dupe count bugs19:21
henoHigh subscriber and team reported are still up for grabs19:22
bdmurrayI'll take one of them19:22
henoliw: did you identify some bugs from testing we should add?19:22
liwheno, still working on the list -- but nothing so far, actually, all problems are minor (symlinks or files left behind after upgrades, mostly)19:23
henobdmurray: which one? :)19:23
henoliw: ok, perhaps you could look at bugs tagged as iso-testing as well then?19:24
jeromegbdmurray: i triage most bugs for xubuntu so I can explain everything to sroberts19:24
bdmurrayheno: subscribers19:24
henoThings that seem grave and widespread19:24
bdmurrayjeromeg: okay, cool.  well if you need anything let me know.19:24
jeromegbdmurray: or at least what i know19:24
jeromegbdmurray: time :)19:24
bdmurrayokay, well not that19:25
jeromeg:)19:25
liwheno, er, are we talking about the same thing? I'm going through the piuparts log files for failures and looking for problems there (but I can look at bugs in launchpad too, of course)19:25
bdmurrayHowever, there are some time saving tools like bughelper that might be useful to you19:25
henoliw: right, my suggestion was looking for high impact things in https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=iso-testing19:26
liwheno, right, I'll do that19:26
henoand the adding the qa-hardy-list tag19:26
henoliw: thanks. You've probably filed several of those in fact19:27
henoI'll look at the from-teams list19:27
henogreat, let's try to get those in some time tomorrow and I'll send the list of to the distro team19:28
heno[TOPIC] Alpha 2 image testing19:28
MootBotNew Topic:  Alpha 2 image testing19:28
henoSo we don't quite know when this will start, likely tomorrow morning19:29
bdmurrayheno: is that UTC?19:29
henoAgain, Alpha 2 mainly needs a sanity check on most images19:29
henobdmurray: yeah, sorry :)19:29
stgraberso, is it still planned for tomorrow or will more likely be released on friday ?19:29
henobefore bedtime tonight OR time would be my guess19:30
heno(as Steve the RM is in OR)19:30
henoMy guess is testing tomorrow, release on Friday19:31
henoI don't think we can arrange much testing on Friday itself19:32
stgraberindeed19:32
henolots of people will be away19:32
henoor working <not from home>19:32
pedro_when is the 2.6.24 hug day?19:32
pedro_is tomorrow also?19:32
henoafter alpha 219:32
pedro_ok ok19:33
henobdmurray: any details?19:33
henoogasawara: ^ ?19:33
bdmurrayThere is a list at https://wiki.ubuntu.com/UbuntuBugDay/2007121919:33
bdmurraythe tasks are in progress19:33
bdmurrayI queried based off 2.6.22 bugs with recent (past 4 weeks) comments19:34
ogasawarabut we'd like to wait with the hug day until Alpha2 is officially out19:34
pedro_totally19:34
henowhich will likely take us past the Holidays19:34
bdmurrayhrm19:34
henoor perhaps Friday19:35
ogasawaraI'm hoping for Friday19:35
henook, cool19:35
henogives reporters a chance to respond over the break19:35
henook, fingers crossed19:35
henonext19:35
heno[TOPIC] Bug Day - no package analysis19:36
MootBotNew Topic:  Bug Day - no package analysis19:36
henobdmurray: care to elaborate?19:36
bdmurrayI was wondering what packages the no package bug day bugs got assigned to19:37
bdmurray40 went to linux-source-2.6.2219:37
bdmurray34 stayed with ubuntu probably due to their not being enough information19:37
bdmurraythen 9 to xorg, and 7 to kdebase19:37
bdmurrayso the quantity dropped off pretty quickly19:38
henobdmurray: do you have a link to the current graph for no-pkg?19:38
bdmurrayhttp://people.ubuntu.com/~brian/testing_graphs/nopackage.html19:38
MootBotLINK received:  http://people.ubuntu.com/~brian/testing_graphs/nopackage.html19:38
henoI wonder if many of the no-pkg bugs are there because it was difficult to figure out where it should go?19:39
henohave the tricky ones been piling up?19:39
bdmurrayRight, that I was really curious how useful writing about "Help -> Report a Bug" would be19:39
henothat might well be over-represented by obscure packages19:39
bdmurrayand with 40 kernel bugs probably not much19:39
bdmurraybut it still couldn't hurt19:40
henolooks like we should revisit this bug day topic in a few weeks19:41
bdmurrayprobably19:41
henobdmurray: you mean that guide is not helpful for kernel bugs, but most other bugs?19:41
bdmurrayI meant that with the kernel, xorg, compiz there is no "Help" menu to go to in the application19:42
henooh, right19:43
henowe should make wishlist bugs to add that ;)19:44
bdmurrayAdditonally it seems like the no package bugs could be a blind spot for the kernel19:44
henoyet, 40 doesn't seem too bad19:44
henoout of 800 or whatever19:44
bdmurrayIt as 40 out of 23819:45
henooh, that is a fair bit19:45
liw17%19:45
bdmurrayactually 43 for those doing percentages19:45
heno16.8 ;p19:45
henomeh19:45
henoanyway, significant19:46
liw18.06722689075630252100% then, approximately :P19:46
henoand how many for related things like lrm, initramfs, etc?19:46
bdmurrayokay +4 with lrm19:47
bdmurrayregardless still a fair bit19:47
henodo many of the no-pkg bugs have dupes already on them?19:47
henoand how many were duped during this triage?19:48
bdmurrayonly 219:48
bdmurrayhttp://people.ubuntu.com/~brian/reports/gt2dups/no-package.html19:48
MootBotLINK received:  http://people.ubuntu.com/~brian/reports/gt2dups/no-package.html19:48
henook, so there is likely quite a bit of dupe material in there19:49
henobdmurray: do you want to write up some musings on this?19:50
bdmurrayWhat do you mean?  A lot of the no-package ones are likely duplicates?19:50
henobdmurray: right, of things that already have a package19:50
heno2 bugs with dupes from a pool of 2000 is tiny19:51
henoso if someone knows enough about a bug to link a dupe, they probably also know it's package19:52
henobtw, I wonder how many were genuine no-pk bugs?19:52
bdmurrayhrm, that report I linked to is old19:52
henoand should we tag them as such?19:52
bdmurrayI'll look into that after the meeting19:52
henook, cool19:53
henoI'm sure we can squeeze some metrics from this :)19:53
heno[TOPIC] Next meeting19:54
MootBotNew Topic:  Next meeting19:54
henoWe should do one the first week of Jan IMO, but when?19:54
liwI'm fine with Wed 2 Jan for a meeting, but I gather people might be on vacation still?19:54
ogasawaraJan 2 works for me as well19:55
pedro_I'd like to have it the 4th19:55
henowe likely won't have much to talk about then19:55
bdmurraywe would have anything new to report?19:55
pedro_so you have a couple of days to read your email19:55
heno:)19:55
pedro_and talk about some issue you'd find19:55
liwnothing to report -> wonderfully short a meeting :)19:55
stgraberI'll probably not be around on the 2nd19:55
ogasawaraJan 4th works too19:55
stgraber(looks like a LUG meeting date :))19:55
liwI'm also fine with Jan 419:55
pedro_or the 1 of January19:55
stgraber+1 for 4th19:55
pedro_a:-)19:55
henolooks like the 4th19:56
stgraberpedro_: yeah, what about the 1st at like 1:00 UTC ? :)19:56
henopedro_: I suspect a meeting the 1st would be rather empty :)19:56
pedro_stgraber: yeah! that's what i'm talking about!19:56
pedro_hey i can bring some champagne19:56
nand:)19:56
henoIf so we should do it by voice19:57
liwjan 4, at 18:00 UTC?19:57
henojust a social meeting19:57
henoworks for me19:58
henoany objections to 18.00 UTC?19:58
ogasawaranope19:58
stgraberfine for me19:58
* bdmurray is doing tz math19:58
bdmurraythat'l be fine19:58
pedro_fine for me  too19:59
liwbdmurray, should be 10:00 west coast time, right?19:59
nandgood19:59
bdmurrayliw: thanks, I got it worked out ;)19:59
heno[AGREED] Next meeting on Jan 4th at 18.00 UTC19:59
MootBotAGREED received:  Next meeting on Jan 4th at 18.00 UTC19:59
* liw successfully destroyed any plans to go to a party on Friday night :)19:59
pedro_haha19:59
heno#endmeeting20:00
MootBotMeeting finished at 20:00.20:00
henooh, on the dot!20:00
henothanks everyone!20:00
liwwe're getting good at this20:00
pedro_thanks you20:01
=== profoX_ is now known as profoX`
stgrabernow, let's hope the new l-r-m will build20:02
stgraberUpload was like an hour ago20:02
henoogasawara: what's the correct package name for lrm in LP now? linux-restricted-modules-2.6.24?20:04
=== bigon is now known as bigon`
henothere seem to be some *-2.6.24 bugs that cannot be closed or renamed20:05
henoLP bug it seems20:05
=== \sh_away is now known as \sh
=== bigon` is now known as bigon
=== bigon is now known as bigon`
=== bigon` is now known as bigon
=== ubotu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 20 Dec 14:00 UTC: Desktop Team Development | 21 Dec 12:00 UTC: MOTU meeting | 02 Jan 12:00 UTC: Edubuntu meeting | 09 Jan 20:00 UTC: Edubuntu meeting | 10 Jan 14:00 UTC: Desktop Team Development | 16 Jan 12:00 UTC: Edubuntu meeting
=== The-Kernel is now known as Tom|smokingkates
=== Tom|smokingkates is now known as Tom__
ogasawaraheno: yah, linux-restricted-modules-2.6.24 should be right21:04
=== Tom__ is now known as The-Kernel
* FisherGirl is looking for a smart person who can help her solve a problem...22:39
somerville32!support | FisherGirl22:41
ubotuFisherGirl: the official ubuntu support channel is #ubuntu. Also see http://ubuntu.com/support and http://ubuntuforums.org22:41
FisherGirlokay22:44
FisherGirlI just have a hard time finding my way22:44
FisherGirlI am not native English speaker22:44
pochuWhat's your language?22:44
FisherGirlswedish22:45
pochu!swedish | FisherGirl22:46
ubotuFisherGirl: Svensk Ubuntu- och Kubuntusupport hittar du pa #ubuntu-se resp. #kubuntu-se22:46
pochuYou can try there :)22:47
* FisherGirl can't afford it22:47
FisherGirlthey sell ubuntu to swedish ppl22:47
FisherGirlnot knowing they can download such stuff for free22:48
=== \sh is now known as \sh_away
=== Martinp24 is now known as Martinp23
=== asac_ is now known as asac

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!