Lemmy.World Announcements

29044 readers

3 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news 🐘

Outages 🔥

https://status.lemmy.world

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to info@lemmy.world e-mail.

Report contact

DM https://lemmy.world/u/lwreport
Email report@lemmy.world (PGP Supported)

Donations 💗

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Join the team

founded 1 year ago

MODERATORS

ruud@lemmy.world

lwadmin@lemmy.world

lwCET@lemmy.world

jelloeater85@lemmy.world

Serinus@lemmy.world

lw_mod_notification@lemmy.world

340

[Done] New try at upgrading to 0.18.1 July 1st 20:00 CET (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by ruud@lemmy.world to c/lemmyworld@lemmy.world

253 comments fedilink hide all child comments

We'll give the upgrade new try tomorrow. I've had some good input from admins of other instances, which are also gonna help troubleshoot during/after the upgrade.

Also there are newer RC versions with fixed issues.

Be aware that might we need to rollback again, posts posted between the upgrade and the rollback will be lost.

We see a huge rise in new user signups (duh.. it's July 1st) which also stresses the server. Let's hope the improvements in 0.18.1 will also help with that.

you are viewing a single comment's thread
view the rest of the comments

[–] New_account@lemmy.world 1 points 1 year ago

That's why it has to be done today. At the moment, Jerboa instantly crashes when trying to access Lemmy, which will definitely scare away new users. My understanding is that this is because Lemmy.World is on version 17, but Jerboa requires instances to be on version 18 or higher. If successful, I believe this would fix the instant crash issue, so we'll at least have an Android app working again.

Hopefully, these are just growing pains symptomatic of a site trying to deal with rapid growth and rapid improvements.