[00:01] <hggdh> micahg: regression-release
[00:01] <hggdh> and open a task for lucid
[00:01] <micahg> hggdh: k, well, we're making a new package so that won't work
[00:01] <micahg> I'll add a lucid-backports task once it's in maverick (if accepted)
[00:02] <micahg> or actually file a new bug for that
[00:02] <hggdh> micahg: you will probably need a new bug for the new package
[00:03] <hggdh> oh boy, the paths we take to adjust to LP...
[00:05] <micahg> hggdh: ?
[00:09] <hggdh> I wish we had something like the depends on from bugzilla
[00:09] <hggdh> er, blocks
[00:09] <micahg> hggdh: agreed
[00:24] <hggdh> oooooohhh
[00:24] <hggdh> micahg: LP will add "record dependencies between bugs" for next fix/improvement
[00:24] <micahg> hggdh: \o/
[00:24] <hggdh> micahg: bug 95419
[00:24] <ubot2> Launchpad bug 95419 in malone "Record dependencies between bugs (affects: 10) (dups: 4) (heat: 69)" [Medium,Triaged] https://launchpad.net/bugs/95419
[00:25] <hggdh> \o/ indeed!
[03:20]  * devildante will go to sleep... good night everyone ;)
[03:58] <bcurtiswx_> g'nite all
[04:34] <Muscovy> Hi, I'm considering joining the bug control team, but I'm not sure if I meet the requirements/experience in https://wiki.ubuntu.com/UbuntuBugControl. I know it's a vague question, but how much "experience" is recommended?
[04:37] <micahg> Muscovy: when you're comfortable deciding importance and your mentor is comfortable as well
[04:43] <Muscovy> micahg: I think that could be an issue, I don't have a mentor.
[04:45] <micahg> Muscovy: heh, well are there triagers familiar with your work, enough to know how well you respond to bugs
[04:45] <micahg> !mentoring | Muscovy
[04:45] <ubot2> Factoid 'mentoring' not found
[04:45] <micahg> ugh
[04:45] <micahg> !mentors | Muscovy
[04:45] <ubot2> Factoid 'mentors' not found
[04:46] <micahg> !mentor | Muscovy
[04:46] <ubot2> Muscovy: Looking for a helping hand with bug triage? Read the wiki for information about requesting a bugsquad mentor: https://wiki.ubuntu.com/BugSquad/Mentors
[04:46] <micahg> there we go :)
[04:46] <Muscovy> Thanks.
[08:18] <vish> micahg: hehe! we tried to keep that factoid short, but seems to backfire a lot of times! ;p
[08:58] <vish> jpds: hmm , just remembered about 'an' or 'a' mv-o  > http://www.colorado.edu/Publications/styleguide/abbrev.html#articles :D
[09:00]  * vish was writing a comment and was reminded of jpds' mention, so looked it up :)
[10:28] <abhijit> hi
[10:30] <elv> hi! I don't understand if there is anything to do or to check before marking a bug report as public.
[10:31] <persia> elv, OK.  So, there's probably a wiki page about it, but I forget the URL.
[10:31] <persia> The general idea is that we don't want to expose bugs if they meet the following criteria:
[10:32] <persia> 1) they represent a not-yet-public security vulernability (needs to be made public the same day as everyone else)
[10:32] <persia> 2) the bug report contains private information (credit card numbers, passwords, etc.)
[10:33] <persia> So, the first group is easy: you will only be able to un-private them if you already have all the security training.
[10:34] <persia> The second group is harder: you need to review and analyse all the available information (including digging through any attachments) to ensure that no information is available.
[10:35] <elv> mmm, ok exactly i read something about the point 2. But i don't understand if i have to remove the coredump file always.
[10:36] <persia> Generally if there's a coredump file, you want to get the apport-retracer to retrace it.
[10:37] <elv> ok thanks.
[13:02] <bcurtiswx_> good morning
[14:54] <devildante> hi all ;)
[14:54] <pedro_> good day devildante
[14:55] <pedro_> how are you today?
[14:55] <devildante> pedro_: hi pedro_, all is fine :)
[14:57] <pedro_> vish, so jibel is working with us in the mentoring program ;-)
[14:57] <pedro_> vish, we can assign him all the remaining students!
[14:59] <bcurtiswx> seb128, is it in or out :P
[15:00] <jibel> \o/
[15:02] <vish> pedro_: oh wow! it reminds me of "Universal Soldiers!" , we would have a huge army! Jibel's Army! :D
[15:02] <vish> yay! Bugs will have no chance now!
[15:02] <bcurtiswx> I would go more with jibel the exterminator!
[15:03] <vish> bcurtiswx: have you seen jibel's wiki?  i read his bug squashing comment and my jaw dropped in awe! :)
[15:04] <bcurtiswx> No, link?
[15:05] <vish> bcurtiswx: https://wiki.ubuntu.com/JeanBaptisteLallement  >  "I'm in the top 3 contributors for bug management activity: karma (reaching apport will be hard though "
[15:07] <vish> pedro_: you loose to jibel ;p
[15:07] <vish> pedro_ is third now!
[15:08] <bcurtiswx> If only I had that amount of free time.. Lol
[15:09] <devildante> I hope I get in this top 20 some time...
[15:09] <bcurtiswx> I will be triaging much more once I take my qualifying exams
[15:11] <bcurtiswx> Computational sciences and informatics with a concentration in space sciences and astrophysics.... And I have to repeat that when people ask what I do...
[15:11] <bcurtiswx> That's what my phd will be in if I get there
[15:12] <devildante> Can someone update the "nominate for" part in bug 502610?
[15:12] <ubot2> Launchpad bug 502610 in webkit (Ubuntu) (and 3 other projects) "Chinese characters unexpectedly switch fonts in WebKit-GTK (affects: 3) (dups: 1) (heat: 28)" [Undecided,Incomplete] https://launchpad.net/bugs/502610
[15:13] <devildante> Lucid must be declined
[15:29] <thekorn_> "[...]with an average speed of 1K bugs per month[...]" what an amazing definitin of speed!
[16:14] <chrisccoulson> hi pedro_
[16:15] <pedro_> hello chrisccoulson
[16:15] <chrisccoulson> about the firefox crash reports with failed retrace - we've actually blacklisted firefox in apport now
[16:15] <chrisccoulson> crash reports go directly to mozilla instead (for maverick)
[16:15] <pedro_> chrisccoulson nice!, i've been looking into the ones left at lp
[16:16] <chrisccoulson> cool, thanks. it's probably best to just close the unuseful ones from maverick now
[16:16] <pedro_> chrisccoulson ok will do that
[16:16] <chrisccoulson> thanks
[16:18] <pedro_> you're welcome :-)
[16:19] <pedro_> devildante, really?
[16:19] <pedro_> Ubuntu BugSquad: devildante is an addict.
[16:19] <devildante> pedro_, ?
[16:19] <pedro_> he's even working on old bug days!!
[16:19]  * pedro_ hugs devildante
[16:19]  * devildante hugs back pedro_
[16:19] <pedro_> devildante, can i clone you?
[16:19] <devildante> pedro_: okay, go ahead :p
[16:20] <pedro_> ;-)
[16:21] <devildante> pedro_: maybe someone should add more bugs to the translations bug day, I finished them all and I wouldn't like the bugday to be cancelled
[16:21] <devildante> we need to motivate :p
[16:22] <devildante> I need to correct: I almost finished them, kamusin took care of the rest :p
[16:25] <pedro_> devildante, we can add some more confirmed , because there's no more New reports :-P
[16:25] <devildante> haha
[16:25] <pedro_> let me do the query and i'll add those
[16:25] <devildante> okay :)
[16:26]  * devildante will go take care of old bug day ;)
[16:32] <ashams> simar: hi
[16:33] <simar> ashams: hi
[16:33] <simar> ashams: done same work ..
[16:34] <ashams> simar: not yet. studying more!
[16:34] <simar> ashams: k, keep going
[16:34] <simar> ashams: i wonder why you set the status of the bug i told you to triage again.. to new
[16:35] <ashams> simar: the reporter provided the needed info!
[16:36] <ashams> simar: but only one reported it, so I could not confirm
[16:36] <ashams> simar: is that wrong?
[16:36] <simar> ashams: i think you are not on right track
[16:37] <simar> ashams: please note the following points
[16:37] <simar> ashams: wait ... point me to that bug first .. get the link
[16:37] <ashams> simar: gust a sec!
[16:38] <simar> ashams: ya
[16:40] <ashams> simar: here it is: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/611992
[16:40] <ubot2> Launchpad bug 611992 in xserver-xorg-input-synaptics (Ubuntu) "Synaptics TouchPad: no supported touchpad found (affects: 1) (heat: 10)" [Undecided,New]
[16:42] <simar> ashams: wait
[16:43] <ashams> simar: k
[16:45] <simar> ashams: triaging means following the bug until it is fixed.. you have to set the status to triaged when there is enough information for a developer to work on it
[16:47] <ashams> simar: yes, but can be with only one Affected, and can't reproduce?
[16:49] <ashams> simar: :) ?
[17:28] <simar> ashams: there??
[17:28] <simar> ashams: my internet broke
[17:31] <simar> ashams: you can't reproduce every bug in your own system ..
[17:32] <simar> ashams: in that case, you should ask for logs from affected users .. that way looking on the logs you can confirm the bug
[17:40] <simar> ashams: heya .... .. .. .. .
[17:44] <KE1HA> Off-Topic I know, but I finished a perfect HP Mini-2133 install w/10.04.1 even BCM4312 wifi nic drivers worked out of the box, Well done all !!
[17:48] <marjo> QA Team Meeting 1700 UTC in #ubuntu-quality
[17:48] <holstein> KE1HA: dood
[17:49] <holstein> i got a 2133
[17:49] <holstein> quite a pain
[17:49] <holstein> im still using the openchrome driver
[17:50] <holstein> hggdh: ping
[17:50] <holstein> i didnt make it on here yesterday morning
[17:51] <holstein> maybe we can schedule something?
[17:51] <hggdh> holstein: I noticed ;-)
[17:51]  * holstein opens calendar
[17:51] <holstein> hggdh: how about tomorrow?
[17:51] <holstein> 11?
[17:51] <hggdh> holstein: deal
[17:52] <hggdh> holstein: 11:00 on what TZ?
[17:52] <holstein> your in my timezone right?
[17:52] <holstein> its almost 1 for you too?
[17:52] <hggdh> I do not know... I am US CDT
[17:52] <hggdh> oh, you are EDT
[17:52] <holstein> yeah
[17:52] <hggdh> hold on, let me check
[17:52] <holstein> hggdh: im open all day tomorrow
[17:53] <hggdh> holstein: any time from 12:00 EDT -- 13:00 is good, for example
[17:54] <holstein> even better
[17:54] <holstein> lets say my noon then
[17:54] <hggdh> holstein: 12:00 EDT it is
[17:55] <KE1HA> holstein:  it picked the STA wifi Driver, and I used the ALT install ISO (debian-installer) to avoid any VID issues on boot / install start. Other than that, was perfect.
[17:55] <nigelb> can someone on gnome look at bug 250664 (i'm on xfce)
[17:55] <ubot2> Launchpad bug 250664 in gnome-device-manager (Ubuntu) ""Device Manager" entry not appearing in System -> Administration (faulty gnome-device-manager.desktop) (heat: 5)" [Undecided,New] https://launchpad.net/bugs/250664
[17:56] <holstein> KE1HA: via released a driver recently
[17:56] <hggdh> nigelb: so such entry under Maverick Gnome
[17:57] <nigelb> hggdh: 'no'?
[17:57] <KE1HA> holstein:  the STA specifically called out 4 versions, 4312 and a couple others where as the BCM diver seemed generic. Hope this fixes some BCM issues as there's allot of folks having trouble with them.
[17:57] <nigelb> hggdh: also, is there such an app?
[17:58] <holstein> KE1HA: check out this screenshot http://imagebin.org/111345 ;)
[17:59] <KE1HA> holstein:  Nastey :-) .. not having that problem at all.
[17:59] <holstein> yeah, that was my first try installing that VIA driver
[17:59] <holstein> i manually put the files where they go
[18:00] <holstein> and got it working
[18:00] <holstein> but no 3D
[18:00] <hggdh> nigelb: nowadays, I do not think so, but pedro_ is the expert on Gnome...
[18:00] <holstein> and the openchrome one seemed 'less hot'
[18:00] <KE1HA> holstein:  check your BIOS as well, on the 2133 wiki page it mentions FM 04 with newer FW causing issues.
[18:00] <holstein> KE1HA: i got 04
[18:00] <KE1HA> Hmm
[18:00] <KE1HA> Let me boot and will see what I ahve
[18:01] <hggdh> nigelb: and it is indeed 'no' such appl in Maverick
[18:01] <holstein> i think i tried them all...
[18:01] <holstein> KE1HA: if you didnt do anything special
[18:01] <holstein> you got openchrome
[18:01] <holstein> AFAIK
[18:01] <nigelb> hggdh: aha, I was afraid of that.
[18:01] <KE1HA> Nope, just out of the box install, apart form picking the boxed restricted driver.
[18:01] <holstein> and it works fine really
[18:01] <holstein> no 3D
[18:01] <holstein> but the display sleeps with it now
[18:02] <holstein> that was always my problem with the openchrome driver and this GPU
[18:03] <KE1HA> holstein:  FM-03
[18:03]  * holstein would like to have some 3D though
[18:03] <holstein> KE1HA: maybe i got 3
[18:03] <holstein> i got the one that the wiki suggested
[18:03] <KE1HA> :-) on a mini well, that's a bit of a stretch for that little box.
[18:03] <holstein> my asus eee 900
[18:03] <holstein> 3D
[18:04] <holstein> no problem
[18:04] <holstein> everything out of the box
[18:04] <ashams> simar: alright :)
[18:04] <KE1HA> how can I test the 3D ?
[18:04] <simar> ashams: ah!
[18:04] <holstein> KE1HA: you can try to enable desktop effects
[18:04] <holstein> right click on the desktop
[18:04] <simar> ashams: let me see what was going on..
[18:05] <holstein> change desktop background
[18:05] <holstein> go to visual effects tab
[18:05] <holstein> and try one of the options
[18:05] <KE1HA> Got, having a play now
[18:05] <holstein> mine goes and looks for a driver
[18:05] <simar> ashams: what you say after my last comments ..
[18:05] <holstein> and says 'no dice'
[18:06] <holstein> desktop effects could not be enabled :/
[18:06] <holstein> i did get 3D with 9.10
[18:06] <KE1HA> Yep, same same.
[18:06] <holstein> had to get the driver
[18:06] <holstein> install it
[18:06] <holstein> say some encantations
[18:06] <holstein> get the right firmware
[18:06] <holstein> and an older kernel
[18:07] <KE1HA> That's ok, this one doesn't need 3D .. can't hardly see the screen anyways :-)
[18:07] <holstein> i only stated working on it to get the display to sleep
[18:07] <holstein> and now it does
[18:07] <holstein> so its not a big deal
[18:07] <holstein> somethings are funky though
[18:08] <KE1HA> Yeah, this one dont need 3D fer it' intended purpose. Can use a full Laptop is I need that.
[18:08] <holstein> video playback is *not* always smooth
[18:08] <holstein> and sometimes i think its going to sleep
[18:08] <holstein> and it doesnt
[18:08] <holstein> and the sound dies
[18:08] <KE1HA> I tested that with the example's and went to utube and watched a few vids there, seemed ok.
[18:09] <holstein> occasionally
[18:09] <holstein> hasnt done it with the latest few kernels though
[18:09] <KE1HA> on the wiki it talks about sound levels not sticking, tested that, did not ahve to use alsamixer to stick them.
[18:09] <holstein> KE1HA: used to be
[18:10] <holstein> if i opened sound preferences
[18:10] <holstein> the device died
[18:10] <holstein> and i could restart it with a script
[18:10] <holstein> yeah
[18:10] <holstein> now 'sound preferences' just crashes
[18:11] <holstein> sudo /sbin/alsa force-reload
[18:11] <holstein> i got a shortcut on my desktop to that ^^ ;)
[18:12] <simar> ashams: what you have to say?
[18:12] <holstein> KE1HA: i havent really been filing bugs either
[18:12] <holstein> im not sure what the devs are suppose to do
[18:13] <holstein> VIA doesnt really share
[18:13] <KE1HA> holstein:  i've not ran nto any bugs yet, other than that 3d business, but then it's not really powerfull enough fer 3d i dont tink.
[18:14] <KE1HA> I was just happy WiFi worked OUB
[18:14] <simar> vish: i think i have found you a papercut. i hope :-|
[18:14] <simar> vish: https://bugs.edge.launchpad.net/ubuntu/+source/xchat/+bug/623066
[18:14] <ubot2> Launchpad bug 623066 in xchat (Ubuntu) "XChat does not remember favourite channels set from the right-click menu (affects: 1) (heat: 8)" [Undecided,Confirmed]
[18:14] <holstein> KE1HA: open sound preferences
[18:14] <holstein> maybe you got the other 2133
[18:15] <holstein> i think there is a few different ones
[18:15] <holstein> but when i open sound preferences
[18:15] <KE1HA> sound pref's doesn't crash
[18:15] <holstein> and go to a few tabs
[18:15] <vish> simar: oh noes! we have enough bugs! ;p
[18:15] <holstein> KE1HA: can you navigate through it?
[18:15] <simar> vish: you can escape ;-))
[18:15] <holstein> is that the one that came with SUSE?
[18:15] <vish> simar: but that wouldnt be a papercut, we dont install xchat by default :)
[18:15] <KE1HA> this is an older box though, probably 2x or there abouts maybe a little more.
[18:16] <simar> vish: ok,  i c
[18:16] <simar> vish: so you will happier ;-))
[18:16] <KE1HA> holstein:  this one came with Slug-Vista, that's why we put UB on it.
[18:16] <vish> simar: hehe, one of these days, we should probably tag Ubuntu itself as a papercut ;p
[18:16] <vish> everywhere there is a bug!
[18:17] <holstein> p/n KX869AT#ABA
[18:17] <holstein> KE1HA: well, dont belive its too slow for 3D
[18:17] <KE1HA> holstein:  the Sound card is VT1708/A is that helps.
[18:17] <holstein> my eee runs compiz great
[18:17] <holstein> its the VIA chips
[18:18] <holstein> my EEE is 900mhz ;)
[18:18] <KE1HA> Over all, im pretty happy with it thus far.
[18:18] <simar> vish: this make users to think... there is none because people like you work tirelessly to identify and fix them ... great soul .
[18:18] <holstein> im always about to break this one
[18:18] <simar> ashams: there ??
[18:19] <KE1HA> well, iv'e got plenty of 3D boxs, dual 9800GT's GTX 280's no need here fer a little mini 3D box :-)
[18:19] <holstein> 80:01.0 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10)
[18:20] <holstein> KE1HA: you can open sound preferences?
[18:20] <holstein> and navigate through it?
[18:20] <holstein> HEY
[18:20] <holstein> now i can :)
[18:20] <simar> vish: I have not been able to contact stanley_robertso till now here in IRC.
[18:21] <KE1HA> same model chip, yes I can open SP, and mess around, no crach, but did notice the Sound Vol goes away on the bar is I change it.
[18:21] <vish> simar: odd, though, you two often dont meet at the same time! can you try sending him an email?
[18:21] <holstein> yeah, its *way* better
[18:21] <holstein> just a couple months ago
[18:21] <holstein> i would open sound preferences
[18:22] <holstein> and the device would disappear
[18:22] <holstein> w00t :)
[18:22] <vish> simar: irc contact is not a requirement, though it helps..  :)
[18:22] <simar> vish: ok .. i note it
[18:22] <holstein> KE1HA: last time i opened it, when the sound vol went away, it crashed
[18:22] <KE1HA> holstein:  yep, your right, it does vanish, guess that's why the vol selector goes away.
[18:23] <holstein> but i was able to get through it once
[18:23] <holstein> thats improvement
[18:23] <KE1HA> It doesn't crash so to speak, jsut disappears.
[18:23] <KE1HA> Guess tha's a bug :-(
[18:23] <holstein> yeah, but what do we do?
[18:24] <holstein> VIA dont care
[18:24] <holstein> KE1HA: you want to file it?
[18:24] <KE1HA> Solution = Dont mess with the preferences :-)
[18:24] <holstein> hehe
[18:25] <KE1HA> Ok, time fer a coffe :-)
[18:25] <holstein> KE1HA: :)
[18:25] <holstein> glad to find a fellow 2133'er
[18:37] <ashams> simar: hey!
[18:39] <simar> ashams: i think you should set the status to incomplete again..
[18:39] <simar> ashams: and read about the statuses again
[18:39] <ashams> simar: he had already included the Xorg.0.log in the report
[18:40] <simar> ashams: so what .. after setting the incomplete status, you should set it to triage if you think it is fit to be worked upon by  developer
[18:41] <simar> ashams: just set the status and then i will tell you whta to do
[18:43] <ashams> simar: here's the Xorg.log, please use your browser to find "Synaptics", I think this is a problem with the Xorg module???
[18:43] <ashams> simar: http://launchpadlibrarian.net/52774134/XorgLog.txt
[18:45] <ashams> simar: there? :-)
[18:45] <simar> ashams: what do you find fishy in it?
[18:49] <ashams> simar: the Synaptics couldn't be Identified!
[18:49] <ashams> simar: it says: "[    33.312] (EE) SynPS/2 Synaptics TouchPad Unable to query/initialize Synaptics hardware."
[18:49] <simar> ashams: good work..
[18:50] <ashams> simar: so, set to incomplete???
[18:51] <simar> ashams: sure
[18:51] <ashams> simar: why, everything is right there?
[18:53] <ashams> simar: and it became clear that the Xorg-Module has been Unloaded, due to Fail to Identification?! :---)
[18:54] <simar> ashams: but why the identification failed ..
[18:55] <simar> ashams: the linux kernel wrongly reported the touchpad .. so synaptics module loading failed
[18:55] <simar> ashams: there
[18:56] <simar> ashams: to confirm this thing we have a command that reports all input devices that kernel reports to x.
[18:56] <simar> ask that from the user
[18:56] <ashams> simar: here's my best guess, it had been mistakenly associated to Driver 1.2.2, which is not the correct one for that version!
[18:57] <ashams> simar: ok
[18:57] <ashams> simar: sorry have to go now, ill do it and confirm through mail, bye for now>
[18:58] <simar> ashams: wild guess!! higher driver version should not stop support for some touchpads
[18:58] <simar> ashams: wait
[18:58] <simar> ashams: a sec
[18:59] <simar> ashams: https://wiki.ubuntu.com/DebuggingTouchpadDetection
[18:59] <hggdh> pedro_, jibel: I am wondering about regression-potential. I read it as "not having confirmed a regression", but this is not how it is being used now
[18:59] <ashams> simar: im still working on that doc?
[18:59] <simar> ashams: see this In case your touchpad features like scrolling, tapping, etc does not work at all.
[19:00] <simar> ashams: in particular
[19:00] <ashams> simar: well!
[19:00] <simar> ashams: NOTE SOME POINTS
[19:00] <jibel> hggdh, today it is used as a regression in a development release.
[19:00] <hggdh> pedro_, jibel: what do you think of having a 'regression-devel' (or the likes) for the current development version of Ubuntu, and using 'regression-potential' as above?
[19:00] <simar> ashams: always comment if you will change the bug status in future atleast for some 1 month ...
[19:00] <ashams> simar: you say that i need to ask him for the /proc/bus/input/devices file
[19:01] <simar> ashams: you are absolutely right ..
[19:01] <jibel> hggdh, but that means that once the dev become a release you'll have to change all the remaining -potential to -release.
[19:01] <simar> ashams: you are getting the stuff
[19:01] <hggdh> jibel: don't we need to do it now, anyway?
[19:01] <jibel> hggdh, there is currently no status to say 'this is maybe a regression but needs confirmation'
[19:01] <ashams> simar: I really have to go NOW :)
[19:01] <hggdh> jibel: yes, I agree. This is why I am proposing it
[19:02] <simar> ashams: make sure you comment
[19:02] <simar> ashams: you can leave .. have a nice day
[19:02] <jibel> we could use a regression-release even in devel because after all this is a development release.
[19:03] <hggdh> yes, we could. My issue is I do not think current usage is intuitive
[19:03] <jibel> hggdh, what is a regression in maverick. This is an opened report or a task targeted to maverick and tagged with regression-release.
[19:04] <hggdh> jibel: this is another issue: we may have multiple nominations
[19:04] <hggdh> and we cannot stick the tag to a tassk
[19:04] <jibel> hggdh, I think that too. And that's why regression- reports  are sometimes messy
[19:05] <jibel> hggdh, you have to open 1 bug per regression. If the regression affects several releases, then open several tasks.
[19:05] <hggdh> yep. I have seen 'regression-<version> used (like 'regression-lucid'). Perhaps this is a way out
[19:06] <hggdh> jibel: but opening one bug per identified version is much more work
[19:06] <jibel> hggdh, I mean one bug per regression with 1 task per release affected by this regression
[19:07] <hggdh> oh, OK, yes. But, then, which tag to use?
[19:07] <jibel> hggdh, regression-potential until the regression is confirmed.
[19:07] <jibel> once confirmed set it to regression-release or -update
[19:08] <hggdh> jibel: then we agree that current usage is not ideal
[19:08] <jibel> hggdh, this for all the releases even the dev release.
[19:08] <hggdh> jibel: no, currently we set regression-potential *only* for the devel release (at least how it is documented)
[19:09] <jibel> if there is a regression in the dev release and it's not fix before the release it become a regression in the stable release.
[19:09] <hggdh> https://wiki.ubuntu.com/Bugs/Tags#Regression%20specific
[19:09] <jibel> hggdh, Yes and I think that's the point that needs to be addressed.
[19:09] <hggdh> cool!
[19:10] <hggdh> let's get pedro_ 's input when he is back
[19:10] <jibel> hggdh, the workflow is no clear because you don't at which step of the regression you are.
[19:10] <hggdh> jibel: indeed
[19:10] <hggdh> and clarifying the workflow may help us
[19:10] <jibel> hggdh, we would have regression-* to track the regression and the bug/task statuses to track the fix of the regression.
[19:11] <jibel> No change in the development process and no specific management for the developers.
[19:11] <hggdh> jibel: so we keep on using -potential as it is, and extend it *also* for current published releases?
[19:12] <jibel> hggdh, this way the regression workflow is quite linear. All the release are handled in the same way, we know which regression are really regressions
[19:12] <jibel> which release is affected
[19:12] <jibel> and which step we at fixing it.
[19:13] <jibel> s/we/we are/
[19:13] <jibel> hggdh, yes we extend the use of  -potential to the stable releases and -release to the devel release.
[19:14] <hggdh> jibel: ack
[19:14] <hggdh> we will have to propose/publish the changes to -devel also
[19:14] <jibel> hggdh, Do you know who designed the process initially ?
[19:15] <jibel> hggdh, It would be good to know the historical issues they encountered.
[19:15] <hggdh> jibel: I do not remember, I think it was started by bdmurray -- but not sure
[19:15] <hggdh> who, BTW, might also want to comment here ;-)
[19:17] <jibel> hggdh, I'm out for diner. See you tomorrow.
[19:21] <hggdh> jibel: bonne soiree
[19:27] <abhijit> bye
[19:34] <njin> pedro_: aound ?
[19:35] <njin> pedro_: around?
[19:38]  * bcurtiswx tries translating hggdh
[19:41] <hggdh> bcurtiswx: good evening, with syntax errors (should have been 'bonne soirée'
[19:42] <bcurtiswx> Ah, muchas gracias
[19:42] <hggdh> bcurtiswx: er, French, not Spanish ;-)
[19:42] <hggdh> merci beaucoup
[19:43] <bcurtiswx> Lol, I know
[20:41] <njin> pedro_: around?
[20:42] <pedro_> njin, yes
[21:11] <kamusin> don't tell to devildante,  pedro_
[21:11] <pedro_> !
[21:11] <devildante> dammit a secret
[21:11] <pedro_> secret?!
 don't tell to devildante,  pedro_
[21:11] <pedro_> oooh!
[21:11] <nigelb> heh
[21:12] <pedro_> i won't tell you
[21:12] <pedro_> and neither to hggdh
[21:12]  * nigelb neither
[21:12] <nigelb> pedro_: did we ever tell hggdh
[21:12] <pedro_> nigelb, of course not! what are you thinking?
[21:13] <nigelb> pedro_: hahah
[21:13] <hggdh> oh, so now there are two of us...
[21:13] <pedro_> we can tell him another clue at the next BugSquad meeting
[21:13] <pedro_> or at UDS
[21:13] <pedro_> !
[21:13] <hggdh> pedro_: grrrrr
[21:14] <nigelb> pedro_: and next one in natty sprint.  Good idea.
[21:14] <kamusin> muahah
[21:16] <devildante> hey, I just discovered the secret!
[21:16] <pedro_> oh oh oh oh
[21:16] <pedro_> !
[21:16] <pedro_> hggdh, ^
[21:20]  * hggdh adds devildante to the list
[21:20]  * vish consoles hggdh :)
[21:20]  * devildante hides
[21:20] <hggdh> LOL
[21:21] <pedro_> hahahaa