Boris, I work for a large networking company and deal with customers on a daily basis. You are right that you never commit to a firm date, but our developers are on an 8 week cycle for maintenance releases. So, from a support perspective, I always say that a maintenance release is due out in X weeks, but I cannot guarantee that your specific fix will be included as it depends on when code freeze is put in place and the QA cycle has to begin. So far, we've been pretty lucky with our releases and only slip by a few days if something drastic is discovered in QA or if a high priority bug is reported that doesn't need a hotfix, but can be pushed into the maintenance release.

I would be happy with a rough time line..like early Q3 or late Q2 for a release. That way, I don't keep asking nagging questions about when when when...

Just like doctors make bad patients, tech support guys make bad customers

Thanks for you thoughts and insights.

Craig