Howdy, couldn't join the discussion earlier. I think bugzilla doesn't really ofter any other useful solution than simply to keep new bugs in a state of NEW. That is the best way for any user to easily see what bugs he/she could try to tackle.
It was with good intentions but somewhat unfortunate to have all initial qooxdoo bugs being assigned by default and it was not meant to have them reserved or blocked. Thanks for your feedback here. Bugzilla is a fine, feature-rich and well-known solution. Hey, we even made it look nice. ;-) What bugzilla doesn't (and most other systems don't) allow, though, is the ability to set individual bug states on a per-user basis (like the read/unread for messages in a mail reader). Clearly, it only supports global states. Anyway, that should be ok for anyone's workflow. If reported bugs are put into a state of ASSIGNED, one has to trust the assignee that he/she either has already started to resolve the issue or will start in the near future. Doing an assignment by default may work fine in a well-defined corporate organization, but doesn't quite fit into an open source project with so many developers involved. For bugs suggesting major reorganization of code (e.g. layout engine reworks) this could also mean that the assignee will tackle it in the not-too-near future. Additional comments may be helpful to make this fact clear. C'mon everybody, lets get to work now and fix all open qooxdoo bugs! :-) Please, have a look at http://qooxdoo.org/community/bugs Happy bug fixing, Andreas 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
