234
edits
Software Update:Major Update Use Cases: Difference between revisions
Software Update:Major Update Use Cases (view source)
Revision as of 17:30, 24 October 2006
, 24 October 2006no edit summary
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
a) -1 from current minor version (i.e. I have 1.5.0.7 and 1.5.0.8 is published) | a) -1 from current minor version (i.e. I have 1.5.0.7 and 1.5.0.8 is published) | ||
Result: User should get the minor update. No offer of Major will be made | Result: User should get the minor update. No offer of Major will be made | ||
b) -x from current minor version (i.e. I have 1.5.0.3 and 1.5.0.8 is published) | b) -x from current minor version (i.e. I have 1.5.0.3 and 1.5.0.8 is published) | ||
Result: User should get the minor update. No offer of Major will be made | Result: User should get the minor update. No offer of Major will be made | ||
c) at current minor version (I have 1.5.0.8 and the only newer version is 2.0.0.0) | c) at current minor version (I have 1.5.0.8 and the only newer version is 2.0.0.0) | ||
Result: User should get the offer for major | Result: User should get the offer for major | ||
d) at current minor version (I have 1.5.0.8 and the only newer version is 2.0.0.0) and have clicked "never" to previous major update offer | d) at current minor version (I have 1.5.0.8 and the only newer version is 2.0.0.0) and have clicked "never" to previous major update offer | ||
Result: User should get no update. | Result: User should get no update. | ||
e) at current minor version (I have 1.5.0.8 and the only newer version is 2.0.0.0) and have clicked "never" to previous major update offer - however we've offered a new major version (i.e. 2.1) | e) at current minor version (I have 1.5.0.8 and the only newer version is 2.0.0.0) and have clicked "never" to previous major update offer - however we've offered a new major version (i.e. 2.1) | ||
Result: User should get major update offer | Result: User should get major update offer | ||
'''Summary''' | '''Summary''' | ||
| Line 23: | Line 23: | ||
a) There is no minor update for me (I'm at the latest point release) | a) There is no minor update for me (I'm at the latest point release) | ||
AND | |||
AND | |||
b) I've not clicked never for this major update version OR I've done a manual "Check for Updates..." | b) I've not clicked never for this major update version OR I've done a manual "Check for Updates..." | ||
| Line 32: | Line 34: | ||
* A never decision does not affect minor updates, only major updates. (See https://bugzilla.mozilla.org/show_bug.cgi?id=350636 for why this matters.) | * A never decision does not affect minor updates, only major updates. (See https://bugzilla.mozilla.org/show_bug.cgi?id=350636 for why this matters.) | ||
* If the server side accidentally offered a major update to Fx 1.5.0.7 (and below), it would be bad because the user would get the major update without having agreed to the EULA. There is nothing in 1.5.0.7 (and below) on the client side to prevent this, so we need a safeguard on the server side. | * If the server side accidentally offered a major update to Fx 1.5.0.7 (and below), it would be bad because the user would get the major update without having agreed to the EULA. There is nothing in 1.5.0.7 (and below) on the client side to prevent this, so we need a safeguard on the server side. | ||
* At some point (Firefox 3, according to bug | * At some point (Firefox 3, according to bug https://bugzilla.mozilla.org/show_bug.cgi?id=341190), we plan to stop supporting Windows 98/ME. Unlike Fx 1.5.x, Fx 2.0+ sends the OS version as part of the update url when it pings the AUS server. Again, this is something the server side will take care of, by not presenting incompatible major updates to clients running on unsupported OSes. See https://bugzilla.mozilla.org/show_bug.cgi?id=341190 for details | ||
'''Example Table''' | '''Example Table''' | ||