"Allen Bauer" <✉spicedham.codegear.com> wrote in message 
news:✉forums.codegear.com...

> reverse be the case. We try and balance the level of detail we give
> about future plans with our need to keep current sales as strong as
> possible. In many ways, we try and only divulge enough information to
> make sure we can *support* the sales of the curent release and not have
> the opposite effect.

Allen, your other post is exactly the kind of info I think helps the most. 
It shows a) there's active development and  b) the rationale about why 
you're doing what we already know you're doing.  You dont have to 
necessarily spill the beans about secrets... just provide insight so that 
people get a feeling for whats going on with the development tool their 
business depends on.


It might be somewhat different when targeting developers... but our company 
has always given a good deal of info about the releases in development.  If 
its far enough off, it doesnt affect sales, and if its close enough to 
release, we give a free upgrade to the new version when its released. 
Thats always worked for us, and truth be told, 90% of our customers arent 
paying attention and wont notice a new release until they get the email 
notice.  Honestly, preventing people from buying previous releases, not 
knowing there's a newer one, has traditionally been a bigger problem.