13:20:29 hello Monero dev community :).  I am in the process of building monero on Alpine and packaging it as a container image. I'm curious about Monero's versioning scheme.  Why are there 4 components?  Are they major, minor, patch, build? Or does the 4th number indicate a batch and the first number indicate something else? 13:20:48 batch=patch 13:21:12 it's major.minor.patch, and you can ignore the "0." 13:21:23 because it's always been "0." 13:22:06 ok, just curious if I can label my images with a semver style, like v18.3.1 instead of something like v0.18.3+1 13:22:28 if that first number ever changes then my scheme would fall apart if using v18.3.1 13:25:53 I don't think it will ever change 13:26:34 "0." was supposed to mean that Monero is not in its final release stage yet and there's some new features coming. It's been 10 years now 13:27:54 right, that's what I would think. But I wonder why they never incremented it past 0 since it's clearly not in some kind of a pre-release state 13:30:41 IIRC it was a fashion established by Bitcoin: https://bitcoin.org/en/version-history 13:30:53 btw they switched from 0.21 to 22.0, lol 13:31:24 the great leap forward 13:32:34 so if Monero ever switches, it will probably just remove the "0." part, so you're safe to use "v18.3.1" 13:33:09 i see, so future versions would be v19 and on 14:17:34 Beware of gratuitous changes. Reminds me of MSDOS. Oh, we don't have directories, so we can use / for options. Later: Oh. Alright, we'll use \ then, close enough. People use C on DOS. Oh shit. To their credit, MSVC doesn't use, I dunno, % to escape characters on C. I guess someone worked out they had better stop digging... But it goes to show, unless you've got a really good reason not to, keeping 14:17:40 things as is is best to avoid getting kicked in the butt by your change later. 14:20:19 Closer to some, some idiot started misnumbering cryptonight variants, confusing people, because they confused variants with the fork they started being used in, 14:20:40 to home*. 18:37:31 Bitcoin Core going from 0.x to 20.x looks like an attempt to cover stagnation. Version number goes brrr