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.
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.