The jump from 7.x right to 24.x had me thinking this was an AI generated article at first, but the main LibreOffice website does indeed show that the new version number is 24.
EDIT: The article literally talks about this and I missed it. Twice. I would like to claim to be on drugs, but sadly(?) this is not the case.
The choice of 24 makes me think they’ve decided to switch to using the last two digits of the current year as the main version number, rather than the previous arbitrary increases, but I can’t find anything obvious about this on the site.
Their current release schedule is every six months, and as long as they don’t accelerate the way web browser releases do, this probably wouldn’t come back to bite them.
The sub-version being .2 and it being February soon makes me wonder if that’s intentional as well.
As for commentary on LibreOffice itself: I use it every once in a while, so I don’t dig deep into its feature set(s) at all. In a previous update I noticed a few things had been moved around in Calc (the spreadsheet) which I’m still getting used to, but by and large all I can do is appreciate those working on it and, for whatever it’s worth, thank them for their efforts.
To use the trash as an analogy, I even picked up the bag and walked around with it a bit (the tab was open. I know I looked at it and scrolled down), but did it make it to where it was supposed to go? (information can into brain?) Doesn’t look like it.
Honestly, it’ll be 2100, so they could just keep incrementing… it won’t be two digits, but v100.2 would be fine and consistent. It’s y3k they need to watch out for.
Edit: though I guess then it’ll just be off… v1000.1 in 3000ad. Maybe we’ll just switch to stardate or something by then… or more likely be extinct.
The jump from 7.x right to 24.x had me thinking this was an AI generated article at first, but the main LibreOffice website does indeed show that the new version number is 24.
EDIT: The article literally talks about this and I missed it. Twice. I would like to claim to be on drugs, but sadly(?) this is not the case.
The choice of 24 makes me think they’ve decided to switch to using the last two digits of the current year as the main version number, rather than the previous arbitrary increases, but I can’t find anything obvious about this on the site.
Their current release schedule is every six months, and as long as they don’t accelerate the way web browser releases do, this probably wouldn’t come back to bite them.
The sub-version being .2 and it being February soon makes me wonder if that’s intentional as well.
As for commentary on LibreOffice itself: I use it every once in a while, so I don’t dig deep into its feature set(s) at all. In a previous update I noticed a few things had been moved around in Calc (the spreadsheet) which I’m still getting used to, but by and large all I can do is appreciate those working on it and, for whatever it’s worth, thank them for their efforts.
So… you didn’t read the article?
All of your speculation about versioning is correct. The subtitle of the article says:
The second paragraph begins with:
Clearly I did not. And now I am concerned because I thought I did.
Oh. That happens to me all the time. Like my wife will ask “did you take out the trash?” And I’ll be all, “I thought I did.” But clearly, I did not.
To use the trash as an analogy, I even picked up the bag and walked around with it a bit (the tab was open. I know I looked at it and scrolled down), but did it make it to where it was supposed to go? (information can into brain?) Doesn’t look like it.
So where is the trash now? At the door? Or in a different room?
No one learned from Y2K 🤦♂️
In under 80 years they’ll have to change the system again smh
Honestly, it’ll be 2100, so they could just keep incrementing… it won’t be two digits, but v100.2 would be fine and consistent. It’s y3k they need to watch out for.
Edit: though I guess then it’ll just be off… v1000.1 in 3000ad. Maybe we’ll just switch to stardate or something by then… or more likely be extinct.
y2k38 will be even funnier than y2k and y3k I guess.
Just wait till y10k then the bug returns