I’m thinking this might be a good thing, since Lemmy v0.19.2 has introduced a new round of bugs and brought back some old ones. Is this why Beehaw is still running the older version? I’m just curious.
Beehaw is still on 0.18.5 for a few reasons:
-
It’s working as expected for functionality, same cannot be said for any 0.19.x release
-
Database changes for 0.19.x release, when upgrading from 0.18.5 will cause extensive down time _(based on reports of other instances). Need to plan that out and ideally TEST IT before doing so on prod. Admin team haven’t had time to do that yet; life happens.
-
Pict-rs updates and changes aren’t compatible with the current version used for pictrs or Lemmy. IE, once we attempt to go up to a 0.19 release it either works, or we’re in a broken state with only recourse to roll back the entire system to a prior backup. Yes, we have those, yes we can do that but really don’t want to.
-
Yes, Beehaw admins are still planning a move to other software. See above about the admin team time constraints.
Beehaw admins are still planning a move to other software
Oh I thought it was still only under consideration, not a plan. That’s unfortunate.
I’d like confirmation on this as well, if there’s confirmation to be had.
Yes, Beehaw admins are still planning a move to other software.
Looking forward to this.
Discuit recently went open source, but it’s still missing some features that other platforms have.
Definitely a good accomplishment, but fits more with the Mastodon style than the Beehaw/forum style.
-
I’ve been wondering this as well. I’ve been wanting some of the 0.19 features, particularly the instance blocking, but with the bugs that have been cropping up I kind of just figured that the mods are waiting and seeing.
0.19.2 seems stable now. But more compelling reasons to upgrade are to fix security holes. I just read another similar post in regards to another instance that mentions this CVE https://github.com/LemmyNet/lemmy/security/advisories/GHSA-r64r-5h43-26qv
0.19.2 seems stable now.
Still getting AbortError: Aborted when I log out with other instances that are running it.
(one of several new bugs)
My instance is working well on 0.19.2 finally with the caveat that it (still) need a daily reboot (docker).
So yes I think it’s wise to wait a bit more.
I’m not having those issues with 0.19.2. I did need to do a one time reset of the instance table, but touch wood has been great. If you are having issues, the official matrix chat is helpful. The general consensus is you shouldn’t need the restart anymore so worth asking for help there.
Well, the ‘official’ devs/mod matrix chat kicked me out and banned my user due to refusing to do free work for them. 🤷♂️ . So not going to be getting any help there.
Don’t know if this is a factor, but my preferred Android client, Liftoff, doesn’t yet support 0.19.x; maybe other clients are in the same boat.
thunder work
Isn’t Beehaw going to leave lemmy? I thought it’s a wasted effort to upgrade if we’re gonna go away?
Why bother haha let’s just chill until we move