From: Till S. <til...@tu...> - 2014-08-20 13:27:55
|
Hi, i added one more open state: - needs-review: If you have fixed a bug / implemented a feature, but you want somebody else to review it before closing the bug, this is the right state. You should go for this if you have changed a larger part and want to be sure you have not introduced new bugs. This is also a good way to tell the reporter of a bug, that he should test, if the bug is also resolved for him. In the later case you should also write a comment with the request to retest and specify the version / branch he should use. For a general review you might want to add a hint, what parts should be reviewed more precisely than others. Regards, Till Am Mittwoch, 20. August 2014, 14:52:42 schrieb Till Schäfer: > Hi, > i have changed the bug tracker to accept different states of a bug / feature request. > > States until now: open, unread, open-accepted, pending, closed, wont-fix > > This states did not really follow our workflow and we only used: open, close, wont-fix and very rarely pending. > > Now i have changed the Tracker to the following states: > Open States: > - open: the default state for new bugs / feature requests > - in-progress: somebody is currently working on the bug / feature. In this state nobody else should grab the bug without contacting its owner! We can save some mails like "on which features / bugs are you currently working" with this state. > - needs-info: the bug / feature is stalled, because further information are needed from the reporter to fix it. Is similar to the old state pending (but it describes better what our use case is) > Closed States: > - closed: the bug / feature > - wont-fix: we decided to not fix the bug / not implement the feature > - invalid: The bug report doe not follow some minimal conditions (e.g. The bug reported is no bug but a feature ;-), Spam, unclear description). May be used after a needs-info request is not responded for a longer time > - duplicate: The bug was already reported. Please add a reference to the duplicate bug in this case. > > Please follow the new states in feature or discuss them if they don't fit your needs. > > Regards, > Till > > -- Dipl.-Inf. Till Schäfer TU Dortmund University Chair 11 - Algorithm Engineering Otto-Hahn-Str. 14 / Room 237 44227 Dortmund, Germany e-mail: til...@cs... phone: +49(231)755-7706 fax: +49(231)755-7740 web: http://ls11-www.cs.uni-dortmund.de/staff/schaefer pgp: https://keyserver2.pgp.com/vkd/SubmitSearch.event?&&SearchCriteria=0xD84DED79 |