On Monday, May 31, 2004, at 11:10:48 PM, 9Val jumped on the stage, took a mike and sang:
> I'm sorry, may be I'm not polite developer, but the code above says > that RELEASE should be done ONLY if number_of_bugs_found <> (not > equal) 0. Since bugs count shouldn't be negative, remains case of > number_of_bugs_found>0 Here, allow me to fix it. I wrote "==", while I meant ">". 1. code, code, code. 2. release BETA 3. test. 4. if number_of_bugs_found > 0 go to 1 else go to 5 5. RELEASE 6. go to 1 Now, please tell me, why isn't your team's development scheme like this? Why do you release versions after versions, even if you KNOW there are still KNOWN and REPORTED bugs in them, and it's usually the users who report the bugs, so they'll have to live with them even longer, seeing version after version, with the bugs they reported still unfixed? Do you think they will be happy with that? With many programs, it's common to see new versions every several months, but good versions, worthy of upgrading to. Why does The Bat have a new version every several weeks, with more and more bugs - okay, some get fixed, but more get added, along with new features? > :) Our cycle is correct! :)) Jokes aside, please, I think this is serious matter. -- |\ /| \~~~/ \~~~/ | \/ | /\ > < \~/ > < ICQ# 3146019 |____| /__\ /___\ /_\ /___\ IQ# 3.14159 Famous last words: "A 25th level CE mage/cleric? Sheesh. I pinch her butt!" Flyin' high with The Bat! v2.11 Beta/6 over the swamps of Windows 2000 5.0 build 2195 Service Pack 4 ________________________________________________________ Current beta is 2.11 Beta/RC1 | '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/
