I feel the need to come out some what in defense of Scott on this issue. 1. From the readme.txt file on the interim version site dated 4/12/04: "We do not keep detailed release notes for interim releases, so we may not be able to tell you whether or not a specific interim release has a specific feature or fix."
2. Interim version numbers can increase dramatically quickly, as per the nature of them. An interim is available, some one tests, reports back this or that, it is changed and an 30 minutes later a new one is available, it is tested and reports back, etc. etc. I remember last year when Scott was working with me on preparing AutoWhite for Declude, he had 4 interim versions in one day just on one single issue. Therefore, just because the version went from xi1 to xi10 in a matter of a day or 2 or 3 does not mean other functions were added. 3. Interim versions should only be used to 1) test a fix for a bug and 2) to test a new function. Either way, it is temporary, and not meant for a true production environment. The fact that many of us do run with Interim versions in production is a sole credit to the relative simplicity of Declude. 4. Once an interim version has included new functions/features, a new beta version should be created within a month. Limit the amount of new functions/features in a beta to 2 or 3 to keep it simple. 5. Once a beta version has come out, limit the introduction of new functions/features to one or two until a new released version is out. 6. Once a beta version has come out, within a month, either a new beta should be out, or a released version should be out. Just my thoughts, your thoughts may and should differ. John Tolmachoff Engineer/Consultant/Owner eServices For You --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
