Re: Question about Bugs

I've found it to be a useful exception to this rule that if I know who maintains that code, I ask them if I can assign it to them. IE, I know that Thies is most likely going to have to handle Oracle bugs, so when I find one, I ask him if I can assign that to him. On Sat, 21 Jul 2001, Rasmus Lerdorf wrote the following to Andy : > Just add a comment to it indicating that you were able to reproduce the > bug and leave it open. If you figure you will fix it yourself you can > assign it to yourself, but don't assign it to other people. > > -Rasmus > > On Sat, 21 Jul 2001, Andy wrote: > > > I have a CVS account now and am starting to close/view > > bugs. > > > > If I find a bug, and I test it, and find that it > > really is a bug, what do I do? Should I put something > > on the bug like TODO:, and if I do that should I close > > it or leave it open? Should a assign it to somebody, > > is there a list of people who deal with specific > > problems? > > > > Thanks, > > Andy Lindeman > > > > __________________________________________________ > > Do You Yahoo!? > > Make international calls for as low as $.04/minute with Yahoo! Messenger > > http://phonecard.yahoo.com/ > > > > > > >