> 1. Package early and often. Unless you don't feel your codebase is ready for users that don't know their way around gdb and a C++ compiler.
> 2. Test your program on different distros. Unless your only hope of making money is selling prebuilt h/w with your own custom kernel/user-space config and with you installing the s/w, and you intend to leave it to others to make sure it all works with various distros. > 3. Use stable libraries. Unless there only ones that do what you need are at 0.2.3. > 4. Keep your documentation up-to-date. Unless the codebase is changing more rapidly than you can type. > 5. Watch non-programmers try to use it. No argument there. --p
