5 ms·
I remember it was briefly discussed but I cant search it on Google. If it isn't a feature release schedule, why they don't have have the Year as Version number
by ksec 8y ago
I remember it was briefly discussed but I cant search it on Google.
If it isn't a feature release schedule, why they don't have have the Year as Version number? So Linux 2019.1 or Linux 19.1 , The First Release of 2019.
- igravious 8y agoPossibly because lots of software out there expects n.n(n) and not 20nn.n(n) ?
- btgeekboy 8y agoWasn’t part of the reason behind the 2.6->3.0 change to help shatter some of those preconceived notions about version numbers?
- Daviey 8y agoProviding each year is a higher number than last year, why does it make it incompatible?
- morganvachon 8y agoWe had a turn of the century during Linux's life span, 1999-2000, which coincidentally was going to be a problem because so many computer systems used a two digit year.
- blixt 8y agoSo we have 80 years to solve the issue of supporting the version going from 99.X to 2100.1 :)
- ehnto 8y agoNow double that estimate, add some padding, and I am looking forward to the release of 2230.1
- giancarlostoro 8y agoThrow in Windows XP becoming sentient and recreating the Windows Subsystem for Linux equivalent for Linux itself.
- thruhiker 8y agoGood god man. What dark beasts lie in you.
- giancarlostoro 8y agoI find it ridiculous people still cling to XP and IE, just wanted to poke fun. :)
- _shadi 8y agospoken like a true project manager
- Daviey 8y agoBut a 4 digit year as a version is ok, right?
- majewsky 8y agoIt just breaks existing regexes. When the kernel switched from 2.6.x.y to 3.x.y, it broke a lot of shoddy scripts that expected the version number to match e.g. /^\d\.\d\.\d\.\d$/
- justaj 8y agoAre kernel maintainers responsible for shoddy scripts though?
- syntheticcdo 8y agoLinus has the (imho: valid) expectation that kernel changes should not break userspace (for detailed explanation see: https://unix.stackexchange.com/a/235532 https://unix.stackexchange.com/a/235532). Even if the version numbering is not an explicit API like say, file system drivers, the versioning of the kernel is an implicit guarantee that the kernel has made to userspace.
- azeirah 8y agoAt some point, I think so. It's similar to a discussion I saw on here about Chrome adding a feature that you could use with a certain html attribute iirc, ie <div newattribute> or something. Supposedly, nobody should have an attribute called 'newattribute' anywhere in their application, but that doesn't mean that there are is a non-zero amount of applications out there that do. The problem is not so much that you can point and laugh at the crappy regexes, or crappy html-devs, the problem is that some scripts on some server, or some sites somewhere don't really have a maintainer anymore. For tiny, tiny projects, you don't really have to take this into account, but if you're Chrome or the Linux kernel, you definitely should take it into account.
- benj111 8y ago19.1, 20.1 We can safely assume that for the next 80 or so years that the year will begin '20'. That leaves 80+ years to patch the software that expects a certain version number format. Plenty of time.
- jcadam 8y agoPlenty of time, I suppose. But if history is anything to go by, you can be sure we'll wait until the last minute to start fixing old software.
- benj111 8y agoYes I was wondering whether to add a /s tag to that last sentence. Hopefully they'll future proof it, or they'll be cursing us come 9999.
- rancid_coon 8y agoWho will stop us going from 99.nn to 100.nn?
- benj111 8y agoAs I said we have 80 years to patch the software. The scheme was suggested to avoid a 20nn.n scheme that the parent identified. Theres nothing to stop us from going from 99.nn to 100.nn and I wont be there to stop it. I'll remind my kids to point it out though :)
- h1d 8y agoCausing year 2119 problem for Linux?
- jsight 8y agoI'm not sure that it would be less confusing to do that. Old kernels are still maintained too, so you'd have new releases like 2018.42 still happening in late 2019. And then people would wonder why some server is running a "year old kernel" when exploits came out less than six months ago. What's wrong with simple monotonically increasing digits?
- thanatropism 8y agoDot numbers are supposed to signify something. Were. Of course, modern software outside shrink-wrap context is evermore incremental and pushed to the customer in small deltas. Even Windows now tells me it's a "service and regular updates are normal procedure". But look at Chrome is on like version 70 in the few years it has been hanging around. If there aren't going to be major discontinuous versions this is the way to go.
- Someone1234 8y agoExactly. For a real world example, Ubuntu's current LTS release 18.04 is running Linux Kernel 4.15 (released Jan-2018). Using a year version format it would be Linux 2015.15. A lot of less technical people and fake security "experts" are going to freak out about a "2015" kernel. In general people seem less interested in how something is, than how something appears. That's why most companies still insist on password complexity rules and disable pasting to password fields, because it FEELS safer.
- Max_aaa 8y agoWhat about using a format like: [Year of Initial Release].[Year of incremental release].[week of incremental release].[Incremental Number] So: 2017.2018.39.332
- MR4D 8y agoMy guess is because Linus has less than 2,019 fingers and toes... << ducks >>