Closed Bug 601660 Opened 15 years ago Closed 15 years ago

generate custom updater-only update for 10.5 users

Categories

(Release Engineering :: General, defect)

All
macOS
defect
Not set
critical

Tracking

(blocking2.0 beta7+)

RESOLVED WONTFIX
Tracking Status
blocking2.0 --- beta7+

People

(Reporter: Gavin, Unassigned)

Details

(Keywords: relnote)

Nightly updates for 10.5 users are currently disabled due to fallout from bug 571367 (see bug 600289). Given the nature of the problem (we needed to make changes to the updater itself to avoid it failing to relaunch the updated build, bug 600362), we need to update users in two steps: first get them a build with an updated updater, and then get them to a build with the changes from bug 571367 (universal i386/x86_64). I propose we do this first for nightlies as a test run, and then again on the beta channel prior to the beta 7 release.
blocking2.0: --- → beta7+
So I can be clear: what's the effect if we don't do this? The "burp" (where after an update the user sees a startup crash, but then after that it works fine?) or an all out "user can't update, can't run Firefox".
If we don't do this, the b6->b7 experience (or nightly update experience once we re-enable those) for 10.5 users will be: 1) update downloads, we restart to apply 2) updater applies update 3) updater fails to launch newly updated build: http://grab.by/6H7H 4) re-launching manually then works fine If we're OK with that experience, we don't need to do this at all...
As long as we can verify that comment 2 is what happens, then yeah, I'm fine with it for the 6,000 or so people who will be affected.
I've gone through the update manually and verified that that's what happens.
Sucks, but ultimately I don't think it's worth the effort.
Status: NEW → RESOLVED
Closed: 15 years ago
Keywords: relnote
Resolution: --- → WONTFIX
Note that this will also affect someone on 10.5 who manually downloaded a Mac nightly between 2010-09-26 (when config change in bug 571367 was made) and 2010-10-02 (when bug 600777 landed) - their updates will be completely broken.
(In reply to comment #2) > If we don't do this, the b6->b7 experience (or nightly update experience once > we re-enable those) for 10.5 users will be: > > 1) update downloads, we restart to apply > 2) updater applies update > 3) updater fails to launch newly updated build: http://grab.by/6H7H > 4) re-launching manually then works fine > > If we're OK with that experience, we don't need to do this at all... I have verified on staging that this is exactly what happens for 10.5 users from beta6 to beta7. From comment 3 I assume we are fine in here.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.