Hi Harold,
Thank you very much for your question. The way our updates currently work is as follows:
* After every new update, we receive a lot of feature requests an we implement most of them on a first come first serve basis.
* After each new feature is implemented, we send a minor update to the customer who requested the feature. This update is usually tested by us, but is still considered in beta state, and thus we don't distribute it to everyone until it's further tested. This process is usually very fast paced (some new features are developed in a few days time).
* After enough updates have been implemented and tested, we group them together in a new release that we announce on our
Announcements page. The announcement usually contains a highlight of all the notable new features along with a complete change log of all the additions/changes/fixes.
What we are currently trying to do is have the latest stable and beta versions accessible to everyone via a secure code repository. We're pushing to have this ready for our next release, but we're currently torn between satisfying the huge number of feature requests we get everyday and between doing our own internal house keeping
Edit: Thanks a lot for the documentation suggestion, we really appreciate your input.