3 ms·
This makes sense, but then why have a version number that looks like semantic versioning? If they are randomly jumping major versions (2.6 -> 3, now to 4) they
by lucb1e 12y ago
This makes sense, but then why have a version number that looks like semantic versioning? If they are randomly jumping major versions (2.6 -> 3, now to 4) they might as well drop the major version altogether.
Why not go for a release number (e.g. r85) and a patch number for hotfixes (e.g. r85.2)?
- pas 12y agoThere are no hotfixes (from Linus, the stable branches are a different matter). And basically the release is just a snapshot of updates that happen to build together with some nudging and silly letters from Linus. Best would be to just go and use a year.month number. 2014.12, 2014.02, 2015.04. But ultimately, it's just a semi-unique identifier with a lot of context that one should be aware of. (And it's not like you can go and buy a Linuks 4 in stores right now, or just put it into your requirements.txt. So confusion is very minimal, it's just a "tag".)
- NeutronBoy 12y agoI actually thought that, but you'd still end up with things like 2014.12-r7 because you end up creating different versions when you backport fixes.
- 4ad 12y agoBecause the semantic versioning meme appeared tens of years (!!) after people started using x.y.z versions for software (including Linux).