It has been a little more than 4.5 months since v2.2 release. I would prefer updates released more often, especially critical bug fixes pushed out at least every 2 months. Some software changes might be more risky to push out sooner, but still I'm sure that some bug fixes have almost no risk and should be pushed out ASAP. I don't mind waiting for new features, but I don't like waiting for bug fixes. I'm willing to bet that most customers feel the same way.

We release updates quite often and they have all bug fixes. The first release was 2.2.0.1, the latest one is 2.2.0.9 at the moment. At the same time we are working on version 2.3 but these two flows have different source codes.

Please add minor release information to this web page, or some new web pages that we can easily find.

http://www.diptrace.com/releases.php

We will consider the suggestion. But I think that will do release information complicated and confused.

The way I look at it is....any time a company releases software without a change description then I wonder what the heck are they trying to sneak out the door without telling anyone.

We consider ticket system for support requests and bug reports. Each bug may get unique number. In release history, we may publish bug numbers that were fixed. If one wants detailed info he can find description on the system. Other users just download the latest version.
This is only idea for the future.