Comments on: Fun and Games with Major Updates (more followup) http://oduinn.com/blog/2009/03/14/fun-and-games-with-major-updates-more-followup/ Wed, 16 May 2012 01:47:52 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: AndersH http://oduinn.com/blog/2009/03/14/fun-and-games-with-major-updates-more-followup/#comment-23925 AndersH Mon, 16 Mar 2009 23:54:49 +0000 http://oduinn.com/2009/03/14/fun-and-games-with-major-updates-more-followup/#comment-23925 My point was, that if the update UI was changed so only a single dialog was shown to the user, it would look like a single update even if it in reality was four updates running and migrating data. This means that you could get all the benefits you list, without doing new QA work on the old code (which no developers are dogfooding anymore). My point was, that if the update UI was changed so only a single dialog was shown to the user, it would look like a single update even if it in reality was four updates running and migrating data. This means that you could get all the benefits you list, without doing new QA work on the old code (which no developers are dogfooding anymore).

]]> By: Robert Kaiser http://oduinn.com/blog/2009/03/14/fun-and-games-with-major-updates-more-followup/#comment-23766 Robert Kaiser Sun, 15 Mar 2009 15:21:22 +0000 http://oduinn.com/2009/03/14/fun-and-games-with-major-updates-more-followup/#comment-23766 I fully agree with Callek that we should even go as far as to offer direct updates to at least a supported version right away, even for FF 1.0 and 1.5, as offering people a major upgrade that just goes to another unsupported product like FF 2.0 is probably still bad. I fully agree with Callek that we should even go as far as to offer direct updates to at least a supported version right away, even for FF 1.0 and 1.5, as offering people a major upgrade that just goes to another unsupported product like FF 2.0 is probably still bad.

]]> By: Justin Wood (Callek) http://oduinn.com/blog/2009/03/14/fun-and-games-with-major-updates-more-followup/#comment-23736 Justin Wood (Callek) Sun, 15 Mar 2009 02:56:32 +0000 http://oduinn.com/2009/03/14/fun-and-games-with-major-updates-more-followup/#comment-23736 Though I know it might be a QA Headache, might be worth seeing if we can support FF1.0.x -> FF3.0.x directly. I know in-app-migrations may be hectic, but the potential still exists per users downloading 3.0.x (or 3.5.x) directly and upgrading anyway. My thought is if we can institute a general rule that "A user should be able to skip at least 1 major update line entirely and still have a useable profile in the end" we'd be much better off. Of course we only need to primarily care about what QA can support/test, and may need some actual infra app-side (and server-side) to support the people who may not want to SKIP a line. In theory of course, we already have that upgrade path for much of Gecko (SeaMonkey, Thunderbird for example skipping 1.9.0 and going straight to 1.9.1 from 1.8.1 -- requiring toolkit, etc. to properly migrate things) Come to think on it, my comment may be better expressed in a separate blog post, or an entirely new thread on .planning, but here will suffice for now. Though I know it might be a QA Headache, might be worth seeing if we can support FF1.0.x -> FF3.0.x directly. I know in-app-migrations may be hectic, but the potential still exists per users downloading 3.0.x (or 3.5.x) directly and upgrading anyway.

My thought is if we can institute a general rule that “A user should be able to skip at least 1 major update line entirely and still have a useable profile in the end” we’d be much better off. Of course we only need to primarily care about what QA can support/test, and may need some actual infra app-side (and server-side) to support the people who may not want to SKIP a line.

In theory of course, we already have that upgrade path for much of Gecko (SeaMonkey, Thunderbird for example skipping 1.9.0 and going straight to 1.9.1 from 1.8.1 — requiring toolkit, etc. to properly migrate things)

Come to think on it, my comment may be better expressed in a separate blog post, or an entirely new thread on .planning, but here will suffice for now.

]]> By: Nick Thomas http://oduinn.com/blog/2009/03/14/fun-and-games-with-major-updates-more-followup/#comment-23731 Nick Thomas Sun, 15 Mar 2009 00:26:31 +0000 http://oduinn.com/2009/03/14/fun-and-games-with-major-updates-more-followup/#comment-23731 It's currently FF1.5.0.12 -> FF2.0.0.6 -> FF2.0.0.20 ..., not 2.0.0.4. "Later" prompts you about a day later, rather than refusing the update. "Never" means don't prompt again for this update, but the updater will prompt for the next major update. It’s currently FF1.5.0.12 -> FF2.0.0.6 -> FF2.0.0.20 …, not 2.0.0.4.

“Later” prompts you about a day later, rather than refusing the update. “Never” means don’t prompt again for this update, but the updater will prompt for the next major update.

]]> By: Bradley Baetz http://oduinn.com/blog/2009/03/14/fun-and-games-with-major-updates-more-followup/#comment-23729 Bradley Baetz Sat, 14 Mar 2009 23:56:15 +0000 http://oduinn.com/2009/03/14/fun-and-games-with-major-updates-more-followup/#comment-23729 Having been through the four-stage upgrade process on a friend's laptop recently, why not just offer the full file if we can't get from the installed version to the latest version (or at least the latest train) in one step? Even after you go "FF1.5.0.12 -> FF2.0.0.20 -> FF3.0.7", its still two steps, and eventually it'll be 1.5.x->2.0.0.x->3.0.x->3.5.x->3.6.x and so on. Having been through the four-stage upgrade process on a friend’s laptop recently, why not just offer the full file if we can’t get from the installed version to the latest version (or at least the latest train) in one step? Even after you go “FF1.5.0.12 -> FF2.0.0.20 -> FF3.0.7″, its still two steps, and eventually it’ll be 1.5.x->2.0.0.x->3.0.x->3.5.x->3.6.x and so on.

]]>