It’s complicated, but basically it was a installer issue not a code bug and the way we build things bumping the version didn’t make sense.
Besides, anyone stuck with the issue couldn’t actually be notified that there was an update so wouldn’t know to download it.
We very much try not to just replace the installer with the same version but sometimes it’s what makes the most sense.
Hi Adam,
I just discovered the problem with 1.5.01 and I only discovered it when I found out there was an update to v. 1.5.02.
My guess as to the reason you didn’t want to update the release number is related to product licensing, however,
If you release a package to the public In my opinion you really should issue the new release a new build number at the very least and here is why.
You now have 2 different versions of 1.5.01 out in the public. One has a known bug and one doesn’t.
There were two versions of 1.5.01 not 1.5.02 - we just released the latter the other day.
We didn’t bump the version number because we didn’t actually rebuild the code. We just rebuilt the installer.
my apologies, that was a typo. Was referring to 1.5.01.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.