Hi FluidSynth community,
I too have been a little confused by version numbering. A few weeks ago I downloaded what I understood to be v2.2 (possibly beta) of the 32bit Windows build. This introduces a fix for tempo changes in the scheduler and I can now schedule them, and it works perfectly – for which my heartfelt thanks! I’m impressed! The package I downloaded came with 7 DLLs, and I assume I need all of them. But checking that I had upgraded consistently from v2.1 was a little difficult. Apart from a change in name of one of the libraries I have now using versions intl.dll 0.18.1.0 [0.18.1] libfluidsynth-3.dll 2.1.7.0 [2.1.7.0] libglib-2.0-0.dll 2.28.8.0 [2.28.8] libgobject-2.0-0.dll 2.28.8.0 [2.28.8] libgthread-2.0-0.dll 2.28.8.0 [2.28.8] libinstpatch-2.dll no version info libsndfile-1.dll 1.0.28.0 [1.0.28.0] where the first number is the file version and the second, in [ ], is the product version. It all works fine, but it isn’t obvious from the version numbers, or the file names, that I have a consistent set with version 2.2! Would it be possible to rationalise all this (file names and version numbering) for us confused (but enthusiastic) users? And echoing Pascal… Thanks a lot for this beautiful piece of software! Dave From: fluid-dev <fluid-dev-bounces+dave=mozart.co...@nongnu.org> On Behalf Of Tom M. via fluid-dev Sent: 17 March 2021 21:44 To: midi-pascal <midi-pas...@videotron.ca> Cc: Tom M. <tom.m...@googlemail.com>; FluidSynth mailing list <fluid-dev@nongnu.org> Subject: Re: [fluid-dev] Curiosity about release numbers 2.1.8 is the version of the project, that any maintainer is free to choose as he pleases. 2.3.8 is the version of the library-interface. It tells you about API/ABI stability because follows the strict semantic versioning rules originally implemented by libtool. See the comment here: https://github.com/FluidSynth/fluidsynth/blob/005719628aef0bd48dc7b2f860c7e4ca16b81044/CMakeLists.txt#L36-L44 And libtool docs here: https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html Sometimes we have bugfix releases that add new public functions. In this case, we must increment the minor version of the library-interface. Whereas for the "project"-version we would just increment the micro level (as those are just bug-fixes). In any case, those are two completely different versions, that coincidentally look very similar at the moment :) Tom
_______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
