On Tue, 2002-09-03 at 18:18, Vincent Danen wrote: > On Tue, 2002-09-03 at 14:54, Dave Sherman wrote:
> > My guess would be that Vince is referring to the various "bug reports" > > we've been seeing come in. Bug reports should, of course, be reported on > > the cooker list so the developers can see and respond to them -- > > hopefully by fixing them :-) > > > > Support requests, unofficial workarounds, et cetera, should come here. > > Exactly... if it's a matter of running cooker or a beta and saying "hey, > how do I do this?" then yes, it is suitable for this list. Buy to write > and say "app XX is broken" is not productive because chances are, that > developer does not read this list and will never know about this bug, > unless someone else reports it to cooker or bugzilla. > > -- > MandrakeSoft Security; http://www.mandrakesecure.net/ > "lynx -source http://linsec.ca/vdanen.asc | gpg --import" > {FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD} Well, I'm coming into this late, but it sure does seem to make sense to me to try to get development related problem reports to the place where the developers are at. As a developer I wouldn't be reading stuff that was not germaine to what I was trying to accomplish during the course of the workday; time is too valuable. I'd be concentrating on my, eh, development mailing lists. LX -- 같같같같같같같같같같같같같같같같같같같같같같같같같� Kernel 2.4.18-6mdk Mandrake Linux 8.2 Enlightenment 0.16.5-11mdk Evolution 1.0.2-5mdk Registered Linux User #268899 http://counter.li.org/ 같같같같같같같같같같같같같같같같같같같같같같같같같�
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
