David,
I've always had problems with this definition in the past (with software vendors at my work, even).
I think to avoid problems, there needs to be a very clear definition of what constitutes a new version, in terms of program changes and added functionality, not in terms of a version number alone.
There is a common practice amongst some developers to make a few incremental changes, bundle them together as a 1.0->2.0 upgrade, and then charge for an upgrade fee. That is because their definition of a major upgrade is not clear or simply vague and subjective.
Also, might be a good idea to put together some workding around the support for older versions. (ex.: previous major versions will be supported for a period of up to 6 months after being superseded, etc.)
Because CF is in $100 plus range, there will be quite high expectations around support, fixes, upgrades, etc. Stacked up against all the real big companies that sell software in this price range. For shareware stuff, people normally don't care much, but those are usually $15-$40.
So, not trying to preach... just want to avoid a situation in the future where you release v 2.0 and have to deal with an unavoidable overload of rage, simply because no one was clear what the upgrade path or licensing terms were. I've lived through that on the customer side twice already. It was not fun for anyone.
Quote: Originally Posted by
veetid 
There is no annual fee, this is a one time software purchase with free upgrades as long as it's not a major version change...