Checklist for getting an app ready for distribution?

[xbury.cs at clearstream.com]

I use the explicit variables in MC which find probably 80% of all 
bugs due to misnamed variables, send messages not formated
correctly... Again, this is a great feature I praise for solid scripts...

Check every menu feature from left to right... Or from feature priority
down... Up to you...

Then I give my stack to my mom and she'll do the weirdest things a user 
can
do trying to figure it out and show me about another 50% of errors or 
unclear
features.... ;))

Another way is to write down the feature list before doing the stack and 
then
checking each one after... Keep a log and check continually. Most 
important
is to recheck after the stack is finished to make sure any last mod doesnt 
affect
previously working scripts... This is lengthier but it's very solid...

On 29/01/2004 11:00:19 use-revolution-bounces wrote:
>Hi,
>
>Does anyone have a handy list of things they do before they get a
>product ready for distribution?  Or maybe even a little stack that
>checks a bunch of stuff automatically?  For example, check that fields
>don't have a font and font size set by mistake.  That the stack has a
>font and font size set.  Get a list of which items have colors set
>(could have been set mistakenly for example).  Those types of little
>things as well as any bigger things one should be aware of (such as
>cross-platform issues).
>
>Thanks in advance,
>-- Frank
>
>_______________________________________________
>use-revolution mailing list
>use-revolution at lists.runrev.com
>http://lists.runrev.com/mailman/listinfo/use-revolution


Visit us at http://www.clearstream.com
                                                          
IMPORTANT MESSAGE

Internet communications are not secure and therefore Clearstream International does not accept legal responsibility for the contents of this message.

The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any views expressed in this e-mail are those of the individual sender, except where the sender specifically states them to be the views of Clearstream International or of any of its affiliates or subsidiaries.

END OF DISCLAIMER