BigFix version numbers

(imported topic written by BenKus)

Hi everybody,

We are looking to use more MSI installers for Windows (rather than our InstallScript based installers), but to be completely compatible with MSI product versions, we need to make slight adjustments to our version scheme. This change won’t really affect anyone, but we thought we would make a quick note just-in-case people were curious:

We have been using a version scheme that looked like:

major.minor.patch.build (such as 7.2.5.22)

And in most cases the third “patch” number was relatively small (less than 20). The new scheme will require us to use the third number as the build number and so it will be a bigger number than before. The new scheme will be:

major.minor.build.xx (such as 8.0.480.0)

We still haven’t fully figured out what we will do with the last “xx” number, but generally won’t be very important.

Again, we don’t expect any issues or anyone to care much, but we wanted to make this note in case anyone had any comments/objections.

Thanks,

Ben

(imported comment written by SystemAdmin)

Hi Ben,

Is this just for the Agent installations? If it is, will the non-windows agent versions (RHEL, Solaris, etc) still be kept, roughly, in sync?

(imported comment written by BenKus)

The same versioning scheme will be applied to the Unix/Linux agents… We try to build them all at the same time, but sometimes they are built at different times so they will have different versions… For instance, you might see a BigFix Server/Console/Windows Agent at 8.0.135 and the Unix agents at 8.0.140…

Usually you will see them the same version, but hopefully it isn’t an issue either way…

Ben