Closed Bug 659721 Opened 13 years ago Closed 13 years ago

Serve partial updates for rapid releases of Firefox

Categories

(Release Engineering :: General, enhancement, P5)

Product:
Release Engineering
Component:
General
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 663894

People

(Reporter: benjamin, Unassigned)

Details

(Whiteboard: [updates]) 

Currently for Firefox 4 -> 5 update the plan is to serve everyone a full update MAR. This is safe, but it's a lot of bandwidth to spend every 6 weeks if we don't have to. I think we should test and ship minor updates from Firefox 5 to Firefox 6.
(In reply to comment #0)
> Currently for Firefox 4 -> 5 update the plan is to serve everyone a full
> update MAR. This is safe, but it's a lot of bandwidth to spend every 6 weeks
> if we don't have to. I think we should test and ship minor updates from
> Firefox 5 to Firefox 6.

s/minor/patch/ I believe
In releng terms, "partial MAR".
Marking this as an enhancement as we will still ship with the base case / no partial mar offered
Severity: normal → enhancement
OS: Linux → All
Hardware: x86_64 → All
If you're talking about the release channel, where we nominally only have one 5.0 and one 6.0 build, I agree it's crazy to have the vast majority of our users pulling a large file. We can set up partial updates for this case easily. Come 7 our normal processes would give us a complete from 5, and a partial from 6.

Did you mean something more than that ?
No, just that. Previously our policy has been to use a full MAR for major version number changes, but with the rapid release cycle I think we should change that policy.
Priority: -- → P5
Whiteboard: [updates]
Based on how I'm setting up the release automation, we should get these for free. Duping to that tracking bug.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Let's dupe to the right bug...
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.