[EMAIL PROTECTED] schrieb: > Sebastian Werner <[EMAIL PROTECTED]> writes: > >> The problem is how to tell the reporter that his bug was read and was marked >> as TODO. I really like assigned because it tells the reporter that I've seen >> the report. Also it doesn't look really supportive to just to not react on >> new bugs. With the STATUS change to ASSIGNED the reporter get some positive >> feedback. Or I could even directly close it as INVALID. But just do nothing >> looks a bit lame in my opinion. > > Although "It's always been done that way" is a lousy reason for continuing to > do something, in this case, "It's always been done that way" and it seems to > work. My experience with other open source projects is that bugs are left as > NEW until someone is ready to work on one. As long as it doesn't take months > to get to working on bugs, leaving them as NEW for a few days or even weeks > shouldn't be a problem.
Mhh, I haven't written this: "It's always been done that way". Also it was not meant this way, if you think so. I just want to say, that if I would like to have a STATUS change to show the reporter that we have seen the report. > >> ASSIGN in my opinion just means that this guy is responsible for this >> component and could help to solve it. ASSIGN isn't equal to ACTIVE in my >> opinion. > > If you add an ACTIVE state to bugzilla (should be doable) Yes? And how? I don't have seen any place for this yet. > then I have no > problem with you setting the state to ASSIGNED. Then again, as this project > grows and more and more developers are willing to accept and fix bugs, you > shouldn't be taking responsibility for every bug or assigning it to yourself. IMHO assigned doesn't mean that I have the responsibility for this bug. It just means that I'm currently the person who is assigned to fix this bug sometimes. It doesn't mean that you couldn't reassign it. > >> Maybe a comment to the bug could help to say "Hey I will start working on >> this now". Would this help you? > > The problem with this is that it requires looking at the long listing of bugs, > not just the summary. That's very tedious. > > Either my original suggestion (leave new bugs as NEW) or adding a new status > ACTIVE work for me. I don't think it's really appropriate for you to accept > all bugs unless you're planning on working on them soon, but that's really up > to you. I'd like to help fix stuff, and if it's easy enough for me to find > things to work on, I'll likely do so. I don't see, why the current way is obstructive for you. You can select and search for any open bug. Take a look at them. Reassign them. Whatever you like. I will discuss this further with Andreas. Maybe we leave new bugs as NEW. Cheers, Sebastian > > Cheers, > > Derrell > > All the advantages of Linux Managed Hosting--Without the Cost and Risk! > Fully trained technicians. The highest number of Red Hat certifications in > the hosting industry. Fanatical Support. Click to learn more > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
