I can't speak for Mojang but at work several years ago we had a contest of sorts, who could properly fix and close the oldest bug. I won by closing a similar aged bug that I had actually opened some 12 years prior by me before I was on the team. It had been passed around and moved to so many backlogs, I had long since stopped caring about the issue. But damn was it great to have fixed it.
they switched away from big yearly updates to smaller, more frequent updates (or "drops", as they call them) some time ago, and they used the same versioning for those small updates and for hotfixes. so it was:
1.21.update-or-hotfix
now we have:
year.update.hotfix
i think it’s clear enough for what it is, even if it’s non standard it makes sense for minecraft’s new update schedule. 27.3.2 is the 2nd hotfix for the 3rd update of 2027
Classic Mojang, I guess it's probably in an attempt to make it easy for users to understand when a release was made.
I was going to say it wouldn't make much of a difference for mods given they only really have one major release a year, but I'm pretty sure they also announced that they wanted to do more small releases instead. So we'll see I guess, main fear I have is that we're going to end up with very weird version range constraints.
8 Comments
ephrin@sh.itjust.works · 8 pts · 211d
Wow, fixed the bug about shipwrecks generating with different wood types when they are on biome borders… 12 years later.
MimicJar@lemmy.world · 6 pts · 211d
I can't speak for Mojang but at work several years ago we had a contest of sorts, who could properly fix and close the oldest bug. I won by closing a similar aged bug that I had actually opened some 12 years prior by me before I was on the team. It had been passed around and moved to so many backlogs, I had long since stopped caring about the issue. But damn was it great to have fixed it.
ephrin@sh.itjust.works · 4 pts · 211d
That must have been soooooooo satisfying!
darkevilmac@lemmy.zip · 2 pts · 211d
Wait did I miss Mojang abandoning SemVer after like a decade? Did they do a Q&A or anything to explain the rationale?
carotte@lemmy.blahaj.zone · 4 pts · 211d
they switched away from big yearly updates to smaller, more frequent updates (or "drops", as they call them) some time ago, and they used the same versioning for those small updates and for hotfixes. so it was:
1.21.update-or-hotfix
now we have:
year.update.hotfix
i think it’s clear enough for what it is, even if it’s non standard it makes sense for minecraft’s new update schedule. 27.3.2 is the 2nd hotfix for the 3rd update of 2027
scottmeme@sh.itjust.works · 2 pts · 211d
They made the change in November or December, and they couldn't even properly use calver, just a bastardized version of it
darkevilmac@lemmy.zip · 2 pts · 211d
Classic Mojang, I guess it's probably in an attempt to make it easy for users to understand when a release was made.
I was going to say it wouldn't make much of a difference for mods given they only really have one major release a year, but I'm pretty sure they also announced that they wanted to do more small releases instead. So we'll see I guess, main fear I have is that we're going to end up with very weird version range constraints.
Kwdg@discuss.tchncs.de · 1 pts · 211d
They already did the small versions 'drops' in 1.21, so it's already been in production for a year or so