I’m not sure ‘future ship dates’ or ‘no news’ are binary.
Case in point, this one about the wiki module. The sensible user (not all of us are) is delighted to hear what the developers are up to, including stories about the weird stuff that happens en route to ship. Including anniversary celebrations. We connect up with our far more modest deadline experiences and go, yeah.
I have a view that developers should share far more information/lore/bloggy experiential goodness about the trip to a version (excluding competitive confidentiality stuff) and less about ship dates.
For instance, I ‘guess’ that the ecommerce module will ship sometime in the next three to six months based on EE’s past history, business exigencies but, most of all, what you guys have said about current status (e.g., it’s not in beta but has reached ‘x’ level of table, template staging). I would love even more info on discoveries made, challenges faced, boundaries encountered, light bulbs that have exploded in your brains ... dates not needed. I’m content to guess. If it ships in 2007, well, life goes on. If I need another product before then, no need to bash you guys about that, but just get it and use it.
(Though I have been very interested in an EE wiki module for two years and have consulted for bucks to some wiki vendors, it says something about EE’s quality that I have partly waited on some development ideas to see how EE integrates wiki with everything else. My choice. Not EE’s responsibility.)
Granted, I’m set free from many years of corporate behaviors which incline towards “if you guys don’t tell me what date the module is shipping, we’re going with Microsoft.” But there is a polite answer for that .... this is a micro-brand with a proven track record and public evidence of a commitment to the future; plus, you can always take the code and jack with it yourselves. If that isn’t sufficient, you will be much happier with Microsoft anyway. Go for it.
By contrast, total (or near-total) radio silence is scary. Worse, it is boring. Never bore your users.