You're going to have to get a lot meaner for me to take any of this
personally.  :)

If what you have is a bug, then file it as a bug.  There is no problem
with that.

Since we have recently been growing the QA team from 1 (me) to slightly
larger (me +3), what's now happening is after a bug comes in, it will be
assigned to one of the QA staff and the user will be notified when that
happens.  If it's useful, we can also post a message to the bug at that
time that says 'I'm now reviewing this bug.'

It's my goal to have every bug get a response (at least a notification
that it's been assigned to a QA person) within a few of business days. 
It would be a major change for us to promise a response within 24
hours.

Bugzilla has controls for what types of users are allowed to change
what fields.  If a user can edit a field, I have no problem with them
correcting a bug.  If they can't edit a field, they should feel free to
post saying 'This happens on all platforms, not just solaris' or
whatever correction needs to be made.

With regards to our bug process, basically our existing process is
exactly as erland described with small differences.  The primary
difference is I haven't had enough resources to actually implement it. 
Now  we do, and we're trying to make sure those steps are actually
followed.

To summarize:

1) Bugs come in
2) They get assigned to a QA person (notification is sent)
3) The QA person makes corrections, makes sure fields are filled out
correctly, searches for duplicates or related bugs, and checks that
there's enough information to try to reproduce.
4) The QA person tries to reproduce
5) The bug gets assigned to a developer or back to me if there's some
kind of problem.


-- 
ChrisOwens

Christopher Owens
QA Manager
[EMAIL PROTECTED]
(650) 210-9400 x717
------------------------------------------------------------------------
ChrisOwens's Profile: http://forums.slimdevices.com/member.php?userid=4240
View this thread: http://forums.slimdevices.com/showthread.php?t=33033

_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to