Hello Alexander,  

ASK> You have to admit that a large number of these bugfixes is actually
ASK> "getting things back to work how they used to" because you're working on
ASK> internal changes with unicode support and whatnot. But, sorry Val, these
ASK> don't qualify as bug fixes for me.

Anyway  it  is  part  of  work  MUST be done and it will take the same
time/efforts now or later.

ASK> I repeat my proposal that there should be a more intensive dialogue between
ASK> Ritlabs and the users, at least the beta testers. Just like it has been
ASK> proposed that beta testers are asked if they think the planned release
ASK> version (RC1) is OK on NUMEROUS occasions. Everyone knows that "fix all
ASK> bugs" is an utopic claim, but being entirely ignored is no way to deal with
ASK> the people that do so much for you in their spare time.

Agree  with  you,  but, as you can see in this list, the latest .61.14
beta  has  positive  feedback  until  reporting  the bug with openning
scheduler.  So, it was a little fix in the chain of fixes, when one of
programmers has lost control... All problems in .62 versions were just
different appereances of one bug, which had to be eliminated soon, but
unfortunately,  took  too  much  time  and nerves (both your and our).
Agree,  that  it  would be much better if I described my confidence in
fast bug-fix *before* than *after* and I'll try to avoid such problems
in future.

-- 

                                                                  9Val


________________________________________________________
 Current beta is 3.62.05 | '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/

Reply via email to