this post was submitted on 27 Nov 2023
431 points (96.3% liked)

Announcements

23287 readers
4 users here now

Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.

You can also find major news on join-lemmy.org

founded 5 years ago
MODERATORS
dessalines@lemmy.ml
nutomic@lemmy.ml
431
Lemmy.ml v0.19 upgrade issues and downtime. (lemmy.ml)
submitted 11 months ago by dessalines@lemmy.ml to c/announcements@lemmy.ml
190 comments fedilink hide all child comments
 

In anticipation of Lemmy's upcoming 0.19 release, and to work out any final issues, we're going to deploy a test release on lemmy.ml within the next few days.

We're doing this testing on lemmy.ml only, so that we can encounter any issues before the release, and to make sure the upgrade process is smooth for other production servers.

Some of the following will happen during the process:

  • Apps will likely break (only for lemmy.ml)
  • Lemmy.ml may experience some downtime for the upgrade to complete (ideally no more than an hour).
  • If anything goes wrong, we may have to restore from a database backup, meaning content made in between backups may be lost.

If all goes well, we'll have an official announcement for the release after this testing period.

I apologize for the difficulties this might cause. At most this will be a week of hair-pulling, but its vital that we catch any issues before telling other servers to upgrade.

you are viewing a single comment's thread
view the rest of the comments
[–] UnverifiedAPK@lemmy.ml 7 points 11 months ago (1 children)

I can sign in with a web browser, but this broke Jerboa for me

[–] dessalines@lemmy.ml 2 points 11 months ago (1 children)

That's expected. Jerboa has an open PR for v0.19 support, and it'll be deployed with the official release.

[–] oh_gosh_its_osh@lemmy.ml 3 points 11 months ago

Same issue here.

I think it would be good practice, that verifying app support should take a front seat in the future before upgrading. The way it is currently handled, is not a good practice to retain users, but rather drive them away.