Skip to content

Improve version number handling. - #92

Open
vaillancourt wants to merge 1 commit into
odedevs:masterfrom
Simlog-Inc:formal-version
Open

Improve version number handling.#92
vaillancourt wants to merge 1 commit into
odedevs:masterfrom
Simlog-Inc:formal-version

Conversation

@vaillancourt

Copy link
Copy Markdown
Contributor
  • Add more formal distinct numbers for the version, allowing better comparison when building against multiple versions of the library.
  • Add the "next version" as a "patch" value to make this useful (when comparing version 0.16.X against "master")
    • This value needs to be updated once a new version has been produced.

@vaillancourt

Copy link
Copy Markdown
Contributor Author

The reason I've created this is that we're currently at 0.16.2, and I noticed a specific change in behaviour in our software when "just moving" to 0.16.6. To help diagnose things and adapt some behaviour (in our case, something related to multi-threading), better handling of the version would help a lot.

I've applied the same change to all the versions until 0.16.2 (see my branches), but I don't think anything within the current project's infrastructure that allow to apply such a thing.

So I suppose this is essentially to help "future us".

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant