2022-03-10 04:04:28 OK, I can see a BUILD number in the latest version, thanks :-) Now, what's the meaning of the number? The latest.tar.gz file has a source directory named RETRO12_2022-03-07_134627_d4a3633768 ... but my BUILD seems to be '3841' ... 2022-03-10 04:05:07 the 'd4a3633768' seems to be the fossil checkin ID 2022-03-10 04:08:42 It might make sense for BUILD to be a string matching the fossil checkin instead? 2022-03-10 15:22:18 I guess I should clarify that comment a little ... we already have a Version that communicates what the API is, what the features are. The BUILD is useful mostly for people using the repositories directly, or relying on the latest.tar.gz ... so BUILD doesn't have to increase in order to represent time passing, it just has to unambiguously associate 2022-03-10 15:22:19 the binary with the exact source that created it, and as fossil is your primary version that's why I think it might be useful to use the fossil checkin value that you're already using in your filenames. 2022-03-10 15:27:40 I'm not sure how to do that and have the committed copy of the source be in sync with the repository. E.g.m 2022-03-10 15:28:24 I make changes, test, commit. The build id at commit time would be for the prior commit, not the new one, as I can't see the future id until after the commit is made. 2022-03-10 15:29:21 The snapshot directory naming is done entirely by fossil 2022-03-10 23:46:28 hah