Solved Inconsistent update warnings

[jdaviescoates]

With the last two Nextcloud updates I've noticed some inconsistencies about the warnings sometimes shown about the package being unstable.

I just updated 3 instances of Nextcloud, all on the same version, all updating to the same version. Only one of them gave this warning.

The same thing happened with the last update too (but I think it was a different Nextcloud that gave the warning that time).

What's all that about?

How can the exact same update be a pre-release sometimes and not at other times?!?

Bizarre and confusing.

[nebulon]

This has to do with the way we roll out updates. For some apps like nextcloud we deliver updates over the course of a few days for automatic updates. Manual updates are immediately available though. This means for a Cloudron which is not yet part of the autoupdate batch for the app, it will show this warning.

[jdaviescoates]

@nebulon I thought I'd seen this on Nextcloud on the very same Cloudron, but I guess I must've dreamt this (especially as that isn't what happen just now)

I think you've previously mentioned you roll things out alphabetically though, which aligns with what I'm seeing: the two Cloudron where I didn't get the warning just now are my.b.... and my.d.... but the one where I did see the warning is my.u....

So, thanks. Makes sense now, if still a little confusing.

[girish]

@jdaviescoates right, we roll out alphabetically as you noticed