366740 - Allow updates to be offered incrementally

Status: RESOLVED WORKSFORME

(AUS Graveyard :: General, enhancement)

Description

[Marcia Knous [:marcia]]

Discussed with seth and asa, and seth suggested filing a bug on this.

Situation: When offering folks a jump to a major update, instead of pushing out all updates at once, it would be great to offer them first to a certain percentage of users or to roll them out incrementally. This would allow us to roll the updates out slowly and identify problems, in case that there is a problem of some sort that wasn't detected during testing.

In the case of the jump from 1.5->2, this could be quite useful.

Comment 1

[Daniel Veditz [:dveditz]]

This seems like an important feature for regular minor updates, too. If you look at the download spike, with the peak getting higher linearly each release, we're really hammering the mirrors all at once. Would be very nice to be able to say "10% of the time say 'no update available'" or whatever adjustable percentage is appropriate.

But we'd want users who explicitly "Check for new Updates" after they heard of the release to go ahead and get the update, otherwise they get miffed. We'll probably need to change the client to send slightly different query parameters for an explicit check vs. a timer-based update.

Comment 2

[Marcia Knous [:marcia]]

It would great if morgamic could comment as to how much work this would be, or whether this is even feasible.

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

This is very similar to bug 358025. Dupe ?

Comment 4

[Nick Thomas [:nthomas] (UTC+12)]

We have global and per version throttling these days.