1
FLAC / Re: FLAC-git Releases (Code Base v1.4.x)
Last post by ktf -Commits that make it to the official master source code are usually intended to correct code errors.No, they are not. I've been busy implementing a few new complex features (multithreaded encoding, decoding of chained Ogg FLAC) and I am still not done squashing bugs. So, these builds are NOT intended for general use.
Quote
Thus, I wouldn't hesitate to mention the code base in the IDs of builds to come.But I do. The current state of the code doesn't yet feel release-worthy to me, so I really don't want people to think that it is.
Quote
Furthermore, it would be easier to understand, which code base version was used.Please explain why.
Quote
Of course it's possible to look up the commit number and/or the its publication date, if the code base version doesn't show up in the file info[...]Please do NOT create files that are not instantly disposable with these development builds, or accept that hic sunt dracones.
Quote
[...] but it I'd prefer to able to see it directly.Please explain why.
Quote
And if your unsure about the stability you could call your builds "reference libFLAC 1.4.3 20241206 git-c786b1c (unstable)" for example.I could, but I haven't seen a compelling reason why I should. I keep hearing (from others in the past too) they'd like to see the number of the previous release somewhere, but never why, beyond "I'd like that" or "I don't want to look it up".