>And, as we can see from the just added email notification feature, new features introduce new bugs ....
Yes, new features are bringing new bugs - ~ one big bug per 1000 lines of code (V2 is now at 34500 lines - 1.5 MB). The bug, that came back, was not related to this new feature. It was simply a wrong logic in my thinking, while I was redesigning a (quick made) bug fix in the resendmail feature. Sorry, but some time such things are happen - nobody is perfect. Yes, you are right, we should not implement new features, if we want to get a stabil version. But - this feature was realy wanted by me, and as long I think I need it - I'll do it (and fix it if needed)! This feature makes it realy easy to watch events in ASSP without waiting to see the event on screen. Thomas <[email protected]> 30.04.2009 11:45 Bitte antworten an ASSP development mailing list <[email protected]> An <[email protected]> Kopie Thema [Assp-test] New features - new bugs Just went from 1.5.1.2 (1.1.09) to 1.5.1.2 (1.2.0) and got SMTP local configuration error message. I have IO::Socket::INET6 2.55 installed, so INET6 support was not available in the past and therefore made no problems at all. With 1.2.0 I got "451 4.7.1 Local configuration error, please try again later". I investigated that and found if ($VerIOSocketINET6 < 2.55) { $CommentIOSocketINET6 = "IPv6 support not available"; mlog( 0, "IO::Socket::INET6 module >= 2.56 required - IPv6 support not available" ); $CanUseIOSocketINET6 = 0; } else {...... Is 2.55 supported now???? I manually patched that small bug. And, as we can see from the just added email notification feature, new features introduce new bugs. This is no news in software development. Shouldn't 1.5.1.1/2 be bugfix releases? I think we definitely cannot get a stable version - and I mean a "really stable version" - if there are always new features added. I don't want to say that the email notification option isn't a welcome and useful addition, but please leave new features to an ASSP version 1.6..../2.1 or whatever version schema you want to use. Just my own opinion tk ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test DISCLAIMER: ******************************************************* This email and any files transmitted with it may be confidential, legally privileged and protected in law and are intended solely for the use of the individual to whom it is addressed. This email was multiple times scanned for viruses. There should be no known virus in this email! ******************************************************* ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
