[Bug]: updater always proposes to update to new major release immediately, dispite stable channel about server

[vasyugan]

all my other instances always skip 0.0 releases and offer upgrades to a new major release only at the first maintenance release, which, I assume, is the expected behaviour for the stable channel.

No. In general:

* 30% of instances on the stable channel are offered x.y.0 - e.g. [28.0.0 nextcloud-releases/updater_server#964](https://github.com/nextcloud-releases/updater_server/pull/964)

* Then when x.y.1 is published, 30% are offered that - e.g. [28.0.1 nextcloud-releases/updater_server#971](https://github.com/nextcloud-releases/updater_server/pull/971)

* Within a couple weeks 70% are offered it - e.g. [Bump staged rollout of 28 to 70% nextcloud-releases/updater_server#973](https://github.com/nextcloud-releases/updater_server/pull/973)

* Then when x.y.2 is published, 100% are offered it - e.g. [28.0.2 nextcloud-releases/updater_server#989](https://github.com/nextcloud-releases/updater_server/pull/989)

It varies a bit IIRC, but that's the convention and based how v28 was rolled out.

The point is not that the upgrade to a particular version is offered at a different point in time, but that all my other instances always skip 0.0 releases

Because of the way the staging probability works currently, it'll always be the same instances offered the update in the early part of the release cycle of any new major.

Thanks for clearing that up. This is, I have to admit, unexpected, given that updating Nextcloud as soon as a new major release is out is, in my experience, asking for trouble. I've done it way too often in the past and more than once I paid quite a hefty price for doing so.

[joshtrichards]

Update should follow the same pattern as on my other NC instances.

Major releases are published via staged roll-outs (https://docs.nextcloud.com/server/latest/admin_manual/release_schedule.html#release-channels). Not all instances will be offered the update at the same time.

Also, one of the biggest factors is instance installation time so the same instances tend to get early offers in the current implementation:

https://github.com/nextcloud-releases/updater_server/blob/3a4a05140dff427487651598aaabd47ea689b732/src/Response.php#L71-L103

[vasyugan]

Update should follow the same pattern as on my other NC instances.

Major releases are published via staged roll-outs (https://docs.nextcloud.com/server/latest/admin_manual/release_schedule.html#release-channels). Not all instances will be offered the update at the same time.

That's not the issue here. The point is not that the upgrade to a particular version is offered at a different point in time, but that all my other instances always skip 0.0 releases and offer upgrades to a new major release only at the first maintenance release, which, I assume, is the expected behaviour for the stable channel.

[joshtrichards]

all my other instances always skip 0.0 releases and offer upgrades to a new major release only at the first maintenance release, which, I assume, is the expected behaviour for the stable channel.

No. In general:

• 30% of instances on the stable channel are offered x.y.0 - e.g. nextcloud-releases/updater_server#964
• Then when x.y.1 is published, 30% are offered that - e.g. nextcloud-releases/updater_server#971
• Within a couple weeks 70% are offered it - e.g. nextcloud-releases/updater_server#973
• Then when x.y.2 is published, 100% are offered it - e.g. nextcloud-releases/updater_server#989

It varies a bit IIRC, but that's the convention and based how v28 was rolled out.

The point is not that the upgrade to a particular version is offered at a different point in time, but that all my other instances always skip 0.0 releases

Because of the way the staging probability works currently, it'll always be the same instances offered the update in the early part of the release cycle of any new major.