Our release cycle period

Normally we are releasing one product version for 3 months. 2 months for development and 1 month for testing and releasing. Why 3 and not 4 months or even monthly ?

• We are distributing products by the subscription. We have 1 year long subscriptions. We want to give as maximum releases for 1 year as possible.
• At each release cycle we are producing 1-2 beta versions. We have quality assurance which normally takes 3-4 days. So, for 1 beta and 1 release the QA will take about 6-8 days. If to have 1 month long release cycle, then QA will eat a lot of time.
• 2 months ... Well, OK. But for some cool features, like TADTable Live Data Window we need more time, if to substruct time for QA, technical support, etc. But we want to make our release cycles predictable for our customers.

So, 3 months by our experience is the gold middle.

Time for releases

We do release quarterly. The normal release dates are:

• End of February. The Spring release.
• End of May. The Summer release.
• End of August. The Fall release.
• End of November. The Winter release.

Our release version numbers

Our product version numbers consist of 4 parts:

• Main product version. Eg, 5;
• Intermediate product version. Normally 0;
• Minor product version. Eg, 3. Odd numbers are for stable releases. Even numbers are for beta versions;
• VCS commit number. It helps to distinguish source bases sent directly to the customers by the requests.

So, 5.0.3 is the release. And 5.0.4 is the beta version. To find exactly your sources version number, you can check uADStanConst.C_AD_Version constant.

Getting changed sources

Often in forum posts or in emails we are talking, that some issue is fixed and changes will be a part of the next release. But you may need to get changes ASAP. No problems ! If you have active product subscription, then write an email to This e-mail address is being protected from spam bots, you need JavaScript enabled to view it and ask to provide the product sources to you. Please include full name, license number and email of the license owner.

The current source base will be provided in 1-2 days, if it just passed the QA cycle. Or in 3-7 days, if we are not sure, that it is stable and need more testing / changing. In any case, the current source base must be considered as a beta version.

So, when ? 

Right now we have 5.0.3 as the latest stable release, produced in September (delayed). The 5.0.5 will be released at end of this month. And the 5.0.4 Beta will be released shortly. That is the story ...