Versioning

[LordBenjamin]

Consider a versioning strategy that separate managed library (i.e. FreeImage.Standard) changes from those in the native library (i.e. FreeImage).

Motivation:

• FreeImage 3.18 has not yet arrived on Raspian
• FreeImage.Standard 4.3.8 was linked against FreeImage 3.18, but also contains changes unrelated to the FreeImage native library version

Options:

• Increment major version when FreeImage gets updated (i.e. instead of 4.3.8, the version would have become 5.0.0) - this would be semver friendly since FreeImage 3.18 broke the API surface (removed some deprecated methods)
• Encode FreeImage version into the version number, e.g. 4.318.0 - this makes it obvious what native version the .NET library is linked against. Harder to fit versioning semantics (e.g. breaking changes) in though.
• Other?