Scott- I'll cast my vote for this approach.
Just a simple beta-only html page on your website. Contents: What's in each interim release, a one-line explanation, and a .config file and/or .junkmail file example would be fine with me. Once we know what's in the release, we can search this list for details. That would have the added benefit of getting the users hooked into earlier-adopters' experiences with each test before they try it on their own. Even niftier, a huge convenience, and no big deal to execute: A link from the test's name to the list archive search page. -d ----- Original Message ----- From: "Mike K" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 23, 2004 3:36 PM Subject: Re: [Declude.JunkMail] Manual > Scott: > > Your abilities as a writer are fine. I have seem many of your explanations > on use of features and for most I think they would suffice. They just need > to be put in the online manual at the same time you post a message to the > list. > > I agree that beta features should not be in the main manual but could be > listed in a separate change.log file or in a beta/interim release file. > > Mike --- [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.
