Changelog not Up-2-Date

Xandrian

Hi,

I check the Changelog daily but it isn't up-to-date. So is the 2.0.402.250 completly missing but I found it here in the forum and I was able to download it via the website. It was a important version because it fixed a the MS Office problem and replaced a pre-build which I got form the support.

Today the chancelog was changes and I found the 2.0.402.252. This file is available since friday but on friday I installed the .250 on a machine.

Auto Update does not work (maybe not in the 252 if the changelog is correct) but it's imo not ok to publis new versions and tell nobody about it.

Regards, Tobias

Robert

Hello Tobias,

Our version scheme follows the convention major.minor.revision.build. That means, the last number is the build number which is automatically increased by our build system every time the code is compiled and a new installer is created.

An increase in the build number does not necessarily imply that the code has changed. E.g. it is possible that two builds have the exactly same code but different build numbers (e.g. .250 and .252). Whenever we release new versions with code changes we update the changelog accordingly.

Best regards,
Robert

Xandrian

Hi Robiert,

yes I unterstand the build number and of course not every version should be in the change log. But every version which can be downloaded from the website should be there and the .250 was available via your website in the last week but is not in the Change-Log.

If you make a new build this is not available for us. Or do you deploy every build directly to the website? I don't think so.

And from 2.0.401.229 to 2.0.402.250 there were a lot of changes. But only the newer .252 is in the Change-Log. Maybe nothing has changed in the .252 against the .250 but I cannot see that but I have installed the .250 on two machines an have downloaded this version directly from your website.

cu tb