Hello All,
I've read thread sub-thread started with
mid:[EMAIL PROTECTED] and it made me sad.
Both reporters are the best in their area. And they both can confirm
that often I ask them privately about list of 'must fix' bugs.
But both make a simple wrong move in their logical path - they think
bug-tracking is one-level system. It is completely wrong, that makes
their opposition useless. The bugs are different like people. And
like in a company there is differentiation between top
manager/middle-tier manager/simple workers and so on (I'm not
powerfull enough in termins :) ). Every worker needs to be paid, so
book-keeper needs to know all of them. That's why bugtrack is
needed. But salary will differ depending of the worker level, that's
why always 'most-important bug list' is needed. As another analogy
you can use is HDD controller work - it firstly tries to use cache,
and only if it fails it uses direct access to hardware.
So... Both in bugtrack and in TBBETA list there are a lot of
duplicates and not confirmed/not reproducible bugs. Here at the
stage appears person, who selects bugs from 'must-fix' category and
assigns them to developers. At the current moment it is me. I read
*most* of TBBETA messages (yes, I'm still skip some offtop messages
or threads, where I know the problem was fixed). I really appreciate
Peter/Boris bug-list, it helps me a lot and saves time. I often
print it and use as todo list - bugtrack simply doesn't allow that
usefull posibility. And I make responsible for fixing those bugs
firstly. After that team member can work with bugtrack all time he
wants.
I hope my point was clear enough, but here is a little resume:
1. first of all we should respect each others opinion
2. bugtracking is done in different levels
3. bugs of current beta-serie automatically have higher priority
4. bugs will be fixed faster with detailed reports
5. less information to analyse = more productive work (both for
bugtrack, where is a lot of "dead" bugs and for list, 3
confirmations is enough)
My suggestion is quite simple - if the bug will be not fixed in
next 3 betas, it *must* be added to bugtrack.
Need to go, but I'll think about other bug-reporting rules for
making our life easier and publish them ASAP. Any comments and
suggestions are appreciated (list/PM/...)
--
9Val
________________________________________________________
Current beta is 3.0.9.17 Return | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
IMPORTANT: To register as a Beta tester, use this link first -
http://www.ritlabs.com/en/partners/testers/
