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.
deleted by creator
They used to test on dedicated testing instances. They probably have for this already.
In the case of lemmy.ml, the users here are probably a bit old hat and dedicated to the cause and so relatively happy to help the project out while the dev team and resources are small. Meanwhile there’s undoubtedly great value in testing on a live and substantial server rather than merely a mock.
As for each new version getting worse, that’s not my impression at all.
That’s the point of the Fediverse.
Yes, that’s not a good idea, regardless of how large an instance is.´or how many users it has. Testing in production is always bad (but most times the only way to get reliable test results).
GitHub in general is problematic since it’s a non-free, for-profit, corporate-hosted service.
What issues are you talking about? This would be important context so I can decide whether I care or not.