New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Versioning #20

Open

LordBenjamin opened this issue Jun 7, 2019 · 0 comments

Assignees

Milestone

Owner

LordBenjamin commented Jun 7, 2019

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?

The text was updated successfully, but these errors were encountered:

LordBenjamin added this to the 4.3.9 milestone

LordBenjamin self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment