[Sc-devel] bug tracker

[Julian Rohrhuber]

>Hi all,
>
>It is probably good to be a specific on how to do this.
>It sounds like the bug reporting process would be something like:
>
>step 1. post report to list(s)
>step 2. wait for replies and action
>step 3. if not resolved in some period of time (1 week?), post to bugtracker.
>
>Is that about right?


yes, this seems a good way to go about it. Maybe the bugtracker 
should send out a mail to the list automatically that a bug was 
committed.



>RJK
>
>>
>>I think that we should merge it with the way we handle things currently:
>>people post things to the emaillist (user or dev), when they think something
>>behaves strangely, and in the discussion following that, it is found out
>>whether or not it is a bug, and in most cases a developer fixes it
>>immediately.
>>The only problem we have right now, is that sometimes, the 
>>discussion does not
>>follow, and/or the bug is not fixed. In this case we need the bugtracker,
>>because when the message gets older, it gets forgotten, and no developer who
>>was not online as much in the time the bug was noticed, will find the bug,
>>unless there is an instance that records them.
>>
>>So my vote is, we start using the bugtracker, and send out a message to
>>sc-user how we use it (i.e. they can file a bug report, if they notice a bug
>>does not get resolved). And put a similar note on the webpage.
>>
>>sincerely,
>>Marije
>>_______________________________________________
>>Sc-devel mailing list
>>Sc-devel at create.ucsb.edu
>>http://www.create.ucsb.edu/mailman/listinfo/sc-devel
>
>_______________________________________________
>Sc-devel mailing list
>Sc-devel at create.ucsb.edu
>http://www.create.ucsb.edu/mailman/listinfo/sc-devel


-- 





.