People who did upgrade would have found regressions in several of those versions.
We’re on 0.19.8 so just one version behind that I need to get around to updating, but before that there were a string of versions with known issues.
Lemmy is not even version 1 yet, it’s risky to update to a new version straight away.
I’d imagine it’s because it’s a hobby project for the admin. It can be a pita to keep on top of stuff like this.
also who cares
Everyone should care?
Unless there is a compelling feature, or security issue, there is no rush to upgrade. Let the bugs get ironed out
in general, the user population is not very well concerned over the sub version of the instance they are using. that is an admin function and worry.
What do you mean?
If I remember right, there was a pretty big change in how pictrs(photo management) worked with lemmy after 0.19.3. There were a few breaking changes and Postgres updates that would take an instance down for a while as well. Not sure if that’s the reason why but it made my instance stay on 0.19.3 for longer than it should have.
Beehaw still on 0.18.3 (they just announced they are going to upgrade though)
I thought they said they were moving to a different platform?
They plan to move to sublinks, but it’s still in development. So they said they will update to the latest version and also planning to update to 1.0 when released (planned for later this year) because their members are having trouble with apps etc after breaking changes.
There’s an update post here: https://beehaw.org/post/18771220
Yeah I gave up on them because of that and the realization that I don’t want my content censored
0.18.3? That got released at 2023-07-28?
That is really bad for the Lemmy instances.
Data is here https://fedidb.org/software/lemmy/versions
0.18.4 sorry
In the past, there have been some pretty unpleasant regressions.
My own home instance, lemmy.today, had some time where it was more-or-less unusable, because every release for a while had some new regression. The lemmy.world guys were a lot more conservative, just backported some critical fixes and waited for a while after each new release to wait and see if problems showed up. They didn’t crash into the regressions.
Granted, some of this could probably be picked up by better automated testing. But to some extent, I think that for at least big instances, it’s good to hold off, wait, and see if a new release has a bunch of issues.
Also, my understanding is that at least for some (all?) past updates, there’s no downgrade path. Once you upgrade, you’re committed.
Maybe you can back up the instances and restore them, but I suspect that that may break state across instances, since you’d get instances with conflicting views of what’s on an instance.
