On Sun, 13 Feb 2005 12:37:12 +0200, Costas Papadopoulos wrote:
> Hello 9Val,
> Sunday, February 13, 2005, 12:32:47 PM, you wrote (possibly edited):
>
> > Therefore the next beta will be available when we'll have no (or at
> > least minimum number) of known issues.
>
> If I may jump in here, I'm very pleased to see that you are taking
> this approach. As a beta tester, I feel that it becomes tiring to see
> that known issues are not dealt with, but new features keep being
> added, some of which create new issues.
I'll second that. I can well appreciate the distinction between a
known issue and a bug.
So, 9val, just a few questions:
o When can we expect this next beta release with a minimum of known issues?
o Is there some reason why you chose to combine this cleaning up
of known issues with the introduction of a major GUI change? Offhand,
this seems like a risky strategy, and not necessarily user-friendly.
For one thing, some users might like the old GUI. For another thing,
many users might prefer to see the known issues cleaned up as a higher
priority than the introduction of a new GUI. This could irritate those
who feel that the new GUI is slowing down what they view as a higher
priority task.
o Is there some reason why you want to clean up all of the known
issues with just one beta release rather than in stages, e.g. several
beta releases all focusing on cleaning up the known issues? A
stage-wise approach would seem to be a more efficient use of your
beta-tester time.
--
Avi Yashar
Windows XP Pro SP2 and The Bat! Pro 3.0.2.10
________________________________________________________
Current beta is 3.0.2.10 | '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/
