Upcoming 1.3.0 Release (Lemmy v0.19)

[ticoombs]

Tasks

• [x] Confirm with Lemmy Devs regarding upgrade processes
  • [x] Update README.md with migration / deployment steps
  • [x] Update VERSION
  • [x] Add new section with Options (Moving forward if we have multiple options we need better documentation regarding what each option does)
• [x] Double check that pictrs_safety_env_vars isn't enabled by default
• [x] Double check using old pictrs version 0.4.4 and not 0.5.x-beta
  • There was a PR on Lemmy that introduced 0.5 (https://github.com/LemmyNet/lemmy/pull/4194)
  • If we do need to move to 0.5 there will be a migration plan created (or notify the admins about the change?). Ref: (https://git.asonix.dog/asonix/pict-rs#user-content-0-4-to-0-5-migration-guide)
• [x] ? Think up more tasks?

[codyro]

I'll snag a few of these over the next few days--feel free to separate any into tasks and assign them to me as well.

Add new section with Options (Moving forward if we have multiple options we need better documentation regarding what each option does)

What Options are you referring to here?

If we do need to move to 0.5 there will be a migration plan created

We should consider this sooner rather than later, regardless of whether we need it for this release.

[ticoombs]

What Options are you referring to here?

pictrs_safety specifically now. But in the future when we choices such as multiple frontends where to do pictrs DB etc

[dessalines]

@asonix is working on a 0.4 -> 0.5 migration script iirc, but I don't know how we'll be able to integrate it into this upgrade.

[kroese]

This migration is only necessary when you want to switch from the sled backend to the postgresql database backend. So maybe its an option to switch to 0.5 first without any changes and do the switch to postgresql at a later point (with the release of Lemmy 0.20 for example).

[codyro]

@asonix is working on a 0.4 -> 0.5 migration script iirc, but I don't know how we'll be able to integrate it into this upgrade.

Does the newest version of Lemmy require 0.5, or can we keep having it use 0.4 until we iron out an upgrade path?

[kroese]

AFAIK Lemmy 0.19 will also work with 0.4 (but I upgraded to 0.5 long ago, so I cannot tell that from experience).

Also with migration, I assumed it was about moving the ansible from sled db to postgresql db. But there is also another kind of migration in 0.5, that fetches the metadata for all objects.

This is automaticly executed and was finished within seconds in my case. But for users who ever had 0.3 or older installed, this process can take a long time because their objects do not have this metadata.

I see that version 0.4.6 is just released which contains a few improvements to prepare for this migration, so the first step would be updating the ansible to that version.

The upgrade from pict-rs 0.4 to 0.5 might take some time. Any uploads that have not had their metadata extracted will be processed during this migration. In order to reduce the time required the migration, pict-rs version 0.4.6 can be run first, and the /internal/prepare_upgrade endpoint can be hit. This will tell pict-rs to extract the required metadata for the 0.5 upgrade in the background while 0.4 is still running, enabling the upgrade to 0.5 to proceed much faster after it completes.

[ticoombs]

@dessalines @Nutomic Do you have any documented upgrade instructions from 0.18.x to 0.19.0 ? As we end up linking here for the upgrade instructions, we probably should write them.

Any gotchas or specific things of note? Or is it the standard change to new tag, run?

---

I see that version 0.4.6 is just released which contains a few improvements to prepare for this migration, so the first step would be updating the ansible to that version.

Yep, we'll bump to 0.4.6 for the next 2 weeks, instead of 0.5, and then go to 0.5 to ensure people have a smooth upgrade.

[dessalines]

No gotchas, this one only requires upping the versions in the docker-compose.yml .