Update CHANGELOG for pydarshan 3.4.7.1 release

[orcunyildiz]

No description provided.

[wkliao]

Version 3.4.7.1 has been taken. Check the list of all Darshan tags.

I suggest to avoid using the fourth digit, as it is not a standard practice.
See the guide line for setting the version number in https://semver.org
Even if Darshan did not follow it in the past, we can start doing so now.

[carns]

Version 3.4.7.1 has been taken. Check the list of all Darshan tags.

I suggest to avoid using the fourth digit, as it is not a standard practice. See the guide line for setting the version number in https://semver.org Even if Darshan did not follow it in the past, we can start doing so now.

Ok. Let's pause and discuss more today. I also don't like the idea of PyDarshan running ahead to 3.4.8 without the other portions of Darshan, since we would want that version number for the next release of the runtime and tools. We either need to find an acceptable way to differentiate pydarshan or else release them all together.

[tylerjereddy]

If you really need to get the release out and don't want to lose synchronization between the runtime and Python tooling, you could consider doing a post-release per: https://packaging.python.org/en/latest/discussions/versioning/#valid-version-numbers

You're not really supposed to do that for bug fixes in your source (usually just for i.e., small typos), but I think it works just fine as far as the PyPI/PyPA/pip infrastructure making the right decision to prefer it when installing, as long as you don't mind violating the purist view on the usage of post-releases.