Hello, MaXxX.
M> Hence, the developing cycle should be:
M> 1. code, code, code.
M> 2. release BETA
M> 3. test.
M> 4. if number_of_bugs_found == 0 go to 1 else go to 5
M> 5. RELEASE
M> 6. go to 1
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
:) Our cycle is correct! :))
Just could not stay even know that will be beaten by you, testers and
team.
M> I wonder what would the authors of competitive mailers say, if I
M> posted your above comment on their boards. I think they'd simply throw
M> a party! "Hey, our competitors, those who write The Bat!, officially
M> admit that their releases have known unfixed little buggies - and
M> perhaps big bugs too! We win, hands down!"
M> You guys either need to change your management, or drop the project,
M> or whatever...
M> Sorry, but I've NEVER heard such a hopeless answer from a program
M> developer.
Now seriosly. It becomes a flame. And I'm afraid of misunderstangings.
If you want to discuss this - it would be better to do it in private
form, since in such conversations I explain my opinion, which can be
significantly differ from team. I'm not enough polite to present
developers.
--
9Val
________________________________________________________
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/
