blaze version macros vs git version tags

[Russell Hewett]

I’m just getting started with blaze and have been exploring the package.

While reading the documentation and exploring the package, I was surprised to find that the version 3.5 release (tagged cac64f2b35002) and the current bleeding edge of the master branch, which are 4 months apart, are both labeled version 3.5.

For stability i have no problem installing and working from the tagged v3.5 commit, but it took me a moment to sort that out. Perhaps the bleeding edge should retain a devpatch string or something to indicate that all subsequent commits are not the 3.5 branch.

‌

Unless they are, in which case feel free to close and ignore this.

[Klaus Iglberger]

Hi Russel!

Thanks for pointing out this omission. You are correct, the BLAZE_VERSION_MINOR tag should have been bumped to 6 right after the release of Blaze 3.5. In the next push we will include a commit to update this tag. Thanks again,

Best regards,

Klaus!

[Klaus Iglberger]

Commit 4dd955a updates the version number to 3.6. The change is immediately available via cloning the Blaze repository and will be officially released in Blaze 3.6.