I notice the version #'s have jumped up from 171 - 174 - 179 - 182 - 187 - 189 - 199 - 205 any particular reason why it's non linear ? No big deal, just wondered
As myself experienced, if some bug is fixed during a remote session you get new build. I have had a couple of sessions with PrevxHelp and he always issued new build for every resolved bug. However these builds are not usually deployed to public. I think that they (at Prevx) are collecting those builds internally and they issue new release candidate (which contains a few builds) later. Just my two cents but Joe may shed more light on.
Exactly true as there are many Alphas before they release the Beta and when we test the Beta for a time without Issues then they make it an Official Release! TH
We have a number of internal releases as well as releases to different partners, other organizations that require specific changes, releases to Enterprise/Business which are managed differently, and, as TH said, releases for alpha testing as well. In many other companies, version numbers end up getting unsynchronized (which is the more "conventional" way of doing it - incrementing by one for each public release) but we tend to keep them all synchronized, and synchronized between all components, to save confusing anyone... including ourselves
As others have said, there'll be internal builds which we don't get to test, but when they think one is ready for public use, it is released either as a beta or a final release. Other vendors do pretty much the same thing; it's just not always apparent.
